@[email protected] to [email protected]English • 7 months agoFFmpeg Lands CLI Multi-Threading As Its "Most Complex Refactoring" In Decadeswww.phoronix.comexternal-linkmessage-square8fedilinkarrow-up1189arrow-down10 cross-posted to: ffmpeg[email protected][email protected]
arrow-up1189arrow-down1external-linkFFmpeg Lands CLI Multi-Threading As Its "Most Complex Refactoring" In Decadeswww.phoronix.com@[email protected] to [email protected]English • 7 months agomessage-square8fedilink cross-posted to: ffmpeg[email protected][email protected]
minus-square@Juujianlink25•7 months 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-squareSupercriticallink65•7 months agoMaybe this? Every instance of every such component was already running in a separate thread, but now they can actually run in parallel.
minus-square@echo64link31•7 months 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
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?