starman@programming.dev to Programming@programming.devEnglish · 1 year agoFFmpeg Lands CLI Multi-Threading As Its "Most Complex Refactoring" In Decadeswww.phoronix.comexternal-linkmessage-square8fedilinkarrow-up1196arrow-down10
arrow-up1196arrow-down1external-linkFFmpeg Lands CLI Multi-Threading As Its "Most Complex Refactoring" In Decadeswww.phoronix.comstarman@programming.dev to Programming@programming.devEnglish · 1 year agomessage-square8fedilink
minus-squareJuujian@lemmy.worldlinkfedilinkarrow-up24·1 year agoI’m not sure I understand. I’ve already been running ffmpeg from the command line and it’s been using multiple cores but default. What’s the difference, what’s the new behavior?
minus-squareSupercritical@lemmy.worldlinkfedilinkarrow-up63·1 year agoMaybe this? Every instance of every such component was already running in a separate thread, but now they can actually run in parallel.
minus-squaregravitas_deficiency@sh.itjust.workslinkfedilinkEnglisharrow-up22arrow-down5·1 year agoGood old RTFM lol
minus-squareecho64@lemmy.worldlinkfedilinkarrow-up31·1 year agobefore you could tell an encoder to run multiple threads, but everything outside of the encoder would run effectively single threaded. now you (should) be able to have all the ffmpeg components, decoder, encoder, filters, audio, video, everything all run parallel
minus-squareOwlBoy@lemmy.worldlinkfedilinkarrow-up9·1 year agoOooo. Will it be automatic? Or do you need to pass a flag?
I’m not sure I understand. I’ve already been running ffmpeg from the command line and it’s been using multiple cores but default. What’s the difference, what’s the new behavior?
Maybe this?
Good old RTFM lol
before you could tell an encoder to run multiple threads, but everything outside of the encoder would run effectively single threaded.
now you (should) be able to have all the ffmpeg components, decoder, encoder, filters, audio, video, everything all run parallel
Oooo. Will it be automatic? Or do you need to pass a flag?