Recherche avancée

Sur d’autres sites (8920)

• FFmpeg - Past Duration Too Large

  14 avril 2018, par Nimble

  I’m having an issue with the warning "Past Duration Too Large" being spammed in my console. There has been quite a bit of discussion about this "warning" online but I have yet to find an actual solution to get rid of it.

  Many just say silence your console, but then I can’t see my segments and other things like warnings, it’s really not a good solution. Another suggests using the fps filter but I have found it creates stutter in the end files...

  Very strangely for reasons completely unknown to me if I double the input framerate and then specify the actual framerate for the output file the warning disappears. Example :

  ffmpeg - y -thread_queue_size 9999 -indexmem 9999 -guess_layout_max 0 -f dshow -video_size 3440x1440 -rtbufsize 2147.48M ^
  
  -framerate 200 -pixel_format nv12 -i video="Video (00 Pro Capture HDMI 4K+)":audio="SPDIF/ADAT (1+2) (RME Fireface UC)" ^
  
  -map 0:0,0:1 -map 0:1 -flags +cgop -force_key_frames expr:gte(t,n_forced*2) -c:v h264_nvenc -preset: llhp -pix_fmt nv12 ^
  
  -b:v 250M -minrate 250M -maxrate 250M -bufsize 250M -c:a aac -ar 44100 -b:a 384k -ac 2 -r 100 ^
  
  -af "atrim=0.038, asetpts=PTS-STARTPTS, aresample=async=250" -vsync 1 -ss 00:00:01.096 -max_muxing_queue_size 9999 ^
  
  -f segment -segment_time 600 -segment_wrap 9 -reset_timestamps 1 C:\Users\djcim\Videos\PC\PC\PC%02d.ts

  As you can see I have -framerate on the input at 200 and -r on the output at 100, believe it or not this gets rid of the warning completely and the resulting file has no issues. However... this is not something you can pull off with any capture card, the only reason I can do this with the Magewell is because under certain resolutions it can record 200fps. Therefore FFmpeg allows me to set it, even though it is double what the card actually allows at the resolution I’m recording. So when I record my camera with a card from Elgato I can’t pull that off :

  ffmpeg -y -thread_queue_size 9999 -indexmem 9999 -guess_layout_max 0 -f dshow -video_size 1920x1080 -rtbufsize 2147.48M ^
  
  -framerate 60 -pixel_format yuyv422 -i video="Game Capture HD60 Pro (Video) (#01)":audio="ADAT (5+6) (RME Fireface UC)" ^
  
  -map 3:0,3:1 -map 3:1 -flags +cgop -r 60 -force_key_frames expr:gte(t,n_forced*2) -c:v h264_nvenc -preset: llhp ^
  
  -pix_fmt yuv420p -b:v 40M -minrate 40M -maxrate 40M -bufsize 40M -c:a aac -ar 44100 -b:a 384k -ac 2 ^
  
  -af "pan=mono|c0=c0, adelay=112|112, aresample=async=250" -vsync 1 -max_muxing_queue_size 9999 -f segment ^
  
  -segment_time 600 -segment_wrap 9 -reset_timestamps 1 C:\Users\djcim\Videos\PC\Camera\CPC%02d.ts 

  When I try to set the -framerate to 120 is just throws an error and wont start recording. Also, while I really wish I could just double the framerate and be done with it, it is pretty clear that that is not a conventional or "actual" solution. That really shouldn’t get rid of the message... The only solution I have come up with besides buying another Magewell is to modify the if statement in the code and compile FFmpeg myself.

  Also I’d like to mention that at times the message is spammed so much that it actually crashes the console, so it’s a real issue not just a warning...

  Any help would be appreciated.

• FFmpeg macos install Reason : image not found

  26 avril 2019, par Joycon

  I’m trying to install FFmpeg on my mac.
  When I do

  brew install ffmpeg --with-chromaprint --with-fdk-aac
  
  --with-fontconfig --with-freetype --with-frei0r --with-game-music-emu --with-libass --with-libbluray --with-libbs2b --with-libcaca --with-libgsm --with-libmodplug --with-librsvg --with-libsoxr --with-libssh --with-libvidstab --with-libvorbis --with-libvpx --with-opencore-amr --with-openh264 --with-openjpeg --with-openssl --with-opus --with-rtmpdump --with-rubberband --with-sdl2 --with-snappy --with-speex --with-tesseract --with-theora --with-tools --with-two-lame --with-wavpack --with-webp --with-x265 --with-xz --with-zeromq --with-zimg

  This happens when I try to use FFmpeg

  dyld: Library not loaded: /usr/local/opt/rubberband/lib/librubberband.2.dylib  
  
  Referenced from: /usr/local/bin/ffmpeg  
  
  Reason: image not found  
  
  Abort trap: 6

• Evolution #3964 : mise en forme minimum des formulaires

  6 juin 2018, par nico d_

  C’est l’avis de tetue mais pas le mien :)

  Dans cette logique, pour être cohérent jusqu’au bout il faudrait aussi déplacer les h3.legend, .editer, .choix .saisie_* etc, qui sont explicitement liés à spip, dans spip.css
  Et déplacer ce qui reste de margin, font-weight et tous les Elements de notifications des boites succes, info, notice, alerte dans theme.css

  Bref, vider forms.css quoi :)

  Tel que je le conçois, form.css devrait contenir tout le style de base des formulaires spip ainsi que boutons réponses et erreurs.
  Tout dans ce fichier, pour pouvoir facilement le surcharger intégralement.

  Et dans theme.css, les ajustements de marges, couleurs, pour la dist, comme actuellement.