[FFmpeg-devel] Change bitrate on-the-fly

Bodecs Bela bodecsb at vivanet.hu
Mon Aug 1 21:30:53 EEST 2016

2016.08.01. 19:46 keltezéssel, Aman Gupta írta:
> I would find your patch useful and am looking forward to reviewing
> it. Using a socket isn't a bad way to do it IMHO- it's portable and allows
> easy integration from any language.
> Another option would be to extend the existing ffmpeg interactive mode to
> handle your new command. Currently ffmpeg allows sending commands to
> filters, but tbh it's pretty confusing to use and not well documented.
> I'd love to see a generic control interface for ffmpeg that was easy to use
> programatically, and could handle simple commands like "pause", "resume",
> "seek <ss>", etc.
> Aman
> On Sun, Jul 31, 2016 at 9:32 AM, Llorx <dallorx at gmail.com> wrote:
>> Hi,
>> About 1 or 2 years ago I had written an addition for ffmpeg to change the
>> video bitrate while ffmpeg is running. The way I've done it is by listening
>> to a UDP socket for an int32, and each time a 4 byte packet enters, changes
>> the bitrate, taking effect instantly. Works like a charm, and the UDP way
>> fits my needings without problems. I needed it because currently I have a
>> business that requires streaming video in some difficult and
>> bandwith-changing environments, so I have a thrid party program than
>> launchs ffmpeg and analyzes the packets sent to detect bandwidth
>> alterations, changing the bitrate accordingly.
>> Now I would like to share it with the community, as I had some messages
>> from some users telling me to release it (As I posted a question about this
>> on Stack Overflow).
>> I know that the UDP thing is a bit hackish, so I would like to ask you,
>> ffmpeg masters, how do you consider that this can be applied in a more
>> "professional" way. I thought that instead of listening to a UDP socket
>> (configurable at launch time with a parameter), I can use named pipes,
>> memory mapped files or simply process signaling. The last method is only
>> available on Unix with SA_SIGINFO. Windows can't handle such signal
>> behaviour.
>> What do you think is the best option?
>> _______________________________________________
>> ffmpeg-devel mailing list
>> ffmpeg-devel at ffmpeg.org
>> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

for filters there is zmq. It works well. Quite few filters support it 
via commands. Would not zmq be good for this purpose, also?



More information about the ffmpeg-devel mailing list