Tag Info

Hot answers tagged

2

From the options in your question, I would use Method 1, as it's the most robust. You should simply set the keyint and min-keyint to the same value and disable scene detection. If you don't disable scene detection, the "counter" will indeed be reset, and your keyframes end up at irregular intervals. Note that I am not assuming variable framerate sequences ...


1

The answer therefore seems to be: Method 1 is verified to work, but is libx264-specific, and comes at the cost of eliminating the very useful scenecut option in libx264. Method 3 works as of the FFMPEG version of April 2015, but you should verify your results with with the script included at the bottom of this post, as the FFMPEG documentation is unclear ...


1

In your setup Server A will consume the most bandwidth due to the icecast server, taking into account you have more people listening with the player. Server B will not consume any bandwidth of those connected directly to Server A's icecast server. Now if you have most of your listeners or viewers using the web front end on Server B then Server B will use ...


1

Try specifying -ss 00:03:00 before your input file. I haven't tried this with screen capture/livestreaming, but I know that this works with standard ffmpeg transcoding syntax. For example, the following command will input a file, transcode the entire file to h264, and then only save the output starting at the 3 minute mark. ffmpeg -i [INPUT] -ss 00:03:00 ...



Only top voted, non community-wiki answers of a minimum length are eligible