Recherche avancée

Sur d’autres sites (14164)

• FFMPEG Increment filename past 1000 and reset from 1

  15 avril 2019, par Eric Gao

  From the documentation :

  ffmpeg -i video.webm image-%03d.png

  This will extract 25 images per second from the file video.webm and save them as image-000.png, image-001.png, image-002.png up to image-999.png. If there are more than 1000 frames then the last image will be overwritten with the remaining frames leaving only the last frame.

  Is there any way to increment this number past 1000, and can I also have this restart from 1 so that we’re not just overwriting the last frame ?

  I have a script that analyzes these images as they come in so I use locally stored images as a buffer/queue. It’s also useful for me to have more images stored so I can go back and debug anything, so being able to do the above would be quite helpful for me.

• http: Do not try to make a new request when seeking past the end of the file

  20 février 2019, par Justin Ruggles

  http: Do not try to make a new request when seeking past the end of the file
  This avoids making invalid HTTP Range requests for a byte range past the
  
  known end of the file during a seek. Those requests generally return a HTTP
  
  response of 416 Range Not Satisfiable, which causes an error response.
  Reference : https://tools.ietf.org/html/rfc7233
  Signed-off-by : Vittorio Giovara <vittorio.giovara@gmail.com>
  

  • [DH] libavformat/http.c

• 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.