FFmpeg lands CLI multi-threading as its "most complex refactoring" in decades
1–10 of 186 posts
Re: FFmpeg lands CLI multi-threading as its "most complex refactoring" in decades
#2Is there a recording of this talk from VDD@Dublin? Can't easily find it on the author's site or here https://www.videolan.org/videolan/events/vdd23/
Update: Found here! https://www.youtube.com/watch?v=Z4DS3jiZhfo&t=1221s
Re: FFmpeg lands CLI multi-threading as its "most complex refactoring" in decades
#3It’s nuts to think that in the near future LLM will be able to do that refactoring in seconds. All we need is enough context window.
Re: FFmpeg lands CLI multi-threading as its "most complex refactoring" in decades
#4the pdf with a presentation requires a password
Re: FFmpeg lands CLI multi-threading as its "most complex refactoring" in decades
#5If I'm operating a cloud service like Netflix, then I'm already running thousands of ffmpeg processes on each machine. In other words, it's already a multi-core job.
Re: FFmpeg lands CLI multi-threading as its "most complex refactoring" in decades
#6It’s nuts to think that in the near future LLM will be able to do that refactoring in seconds. All we need is enough context window.
Why would you think this is possible?
Re: FFmpeg lands CLI multi-threading as its "most complex refactoring" in decades
#7If I'm operating a cloud service like Netflix, then I'm already running thousands of ffmpeg processes on each machine. In other words, it's already a multi-core job.
As multi-core as Python and Ruby then.
Re: FFmpeg lands CLI multi-threading as its "most complex refactoring" in decades
#8Meanwhile, I've been enjoying threaded filter processing in VapourSynth for nearly a decade.
Not that this isn't great. Its fantastic. But TBH its not really going to change my workflow of VapourSynth preprocessing + av1an encoding for "quality" video encodes.
Re: FFmpeg lands CLI multi-threading as its "most complex refactoring" in decades
#9It’s nuts to think that in the near future LLM will be able to do that refactoring in seconds. All we need is enough context window.
Yeah, it's nuts to think that.
Re: FFmpeg lands CLI multi-threading as its "most complex refactoring" in decades
#10If I'm operating a cloud service like Netflix, then I'm already running thousands of ffmpeg processes on each machine. In other words, it's already a multi-core job.
As multi-core as Python and Ruby then.
Yes. The kernel multiplies your efforts for you. It works great for web services.