The shell script is an interesting workaround. He's using uncompressed, so every frame is a keyframe in this case.
How are you finding the frame number? If you are scanning the video to find you could use the showframe/showtime options as shown in my image above. I do not have the articles url at the moment until i get on the computer. I don't know if it would help but there have been several post recently that describe how to list the key frames or all frames and their times. anything like that exist? Couldn't find it in the docs. It'd be nice if there was a filter like exitif(condition) - then I could say: I guess I could write a babysitting script that determines when the file being generated stops growing and then SIGINT's ffmpeg. I know I can SIGINT the process and it will cleanly close the file - that can work, but I'd like to batch this up and run it overnight, rather than babysitting it. If there was a fancy way to put all of this into one giant filter chain and output 12 different files at different frame rates, I would only have to churn through the file once. What's the smarter way to do this? I have 12 or so consecutive sections of the file that are at different frame rates. That is, ffmpeg doesn't cleverly parse the "select" filter to realize that it can stop encoding after 100 frames and just close out the file - instead, it churns through all the remaining frames. The issue I'm having is that the "select" filter seems to work, but (understandably) ffmpeg correctly stops encoding at 100 frames and then needs to read every remaining frame just to check the "select" filter, which takes ~30m for this file (if my estimate is correct). Ffmpeg -r 24 -i input.avi -vf 'select=gte(n\,0)*lt(n\,100),setpts=PTS-STARTPTS' -c:v libx264 -b:v 40000k -preset veryslow -profile:v high444 output.mp4
0 kommentar(er)
