• Adobe Premiere Pro

  official standpoint on multithreading / multicore?

  Posted by Philipp Hahn on December 25, 2019 at 1:50 pm

  TL;DR premiere / after effects / media encoder only leverage a single thread / core and reencoding movs therefore takes about 11x times as long as it should.

  i originally contacted adobe support over this – they asked me to file a bug report in their official forum, but as i do not get an answer there…:
  https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/39221437-what-is-the-official-standpoint-on-multithreading

  the issue: i convert an h264 to a cropped png sequence, no effects applied (except the cropping).
  if i do this in premiere, ae or media encoder, it takes at least 2 hours and only utilises a fraction of my cpu. if i do the very same operation via ffmpeg (cli), it’s done in 11 minutes. i verified this behaviour on three different machines, results are the same. bottom line is, media encoder simply does not seem capable of using more than one thread on a single core (for screenshots and details, see referenced thread).

  is this expected behaviour (because cc simply does not work on more then one core/thread) or a bug (and something can be done about it)?

  Pat Horridge replied 6 years, 4 months ago 2 Members · 1 Reply
• 1 Reply

• 

  Pat Horridge

  December 26, 2019 at 9:22 am

  Writing multicore/thread code isn’t easy.
  Typically for video it’s often done by processing multiple frames in parallel but with long GOP content that’s not easy to do as following frames are based on current ones.
  It is possible but not easy and Adobe have decided its not worth the effort.
  You will find with frame based media it works much better but that’s because it’s easier to code.

  Pat Horridge
  Broadcast & Post Consultant, Trainer, Avid Certified Instructor
  Free online Tutorials at VET digital media academy online https://vimeo.com/channels/752951
  pat@vet.co.uk

Reply to this Discussion! Login or Sign Up