Skip to main content
Participant
April 19, 2023
Question

Media Transcode poorly optimized?

  • April 19, 2023
  • 1 reply
  • 562 views

Hi there,

 

I am a Multimedia Production Student and have been using Premiere Pro and Media Encoder for 6 years now. As I am preparing to move to freelance I am finding myself regularly having to transcode large amounts of footage, for example from H.265 to Prores. I am growing more and more frustrated with how little CPU and GPU capacity is used when transcoding. Currently I am looking at a max. utilization of 44% on CPU and around 25% on GPU, no matter what I do. It's definitely not storage speed related, everything is running off of internal PCIE SSDS or external drives with over 400MB/s transfer speeds. What's most frustrating is that transcoding in Resolve 18 Maxes out my system resources in similar transcodes. Am I doing something wrong or is Media Encoder still this poorly optimized?

 

Thank you for your inputs and experiences.

This topic has been closed for replies.

1 reply

Participating Frequently
April 20, 2023

Hi @Dom R. ,

 

Sorry for the problem. Please provide some details to help us investigate this on our end:-

  • System/OS details
  • Premiere Pro version

 

Please share your project & associated media file also, if possible. You can use https://helpx.adobe.com/creative-cloud/help/share.html . We will check it on our end and update it here.

 

Thanks,
Mayjain

Dom R.Author
Participant
April 20, 2023

Hi @mayjain7130546 

 

Thanks for your reply. 

I'm currently running PR V23.3 and ME 23.3 also (I've had poor utilization with previous versions as well however), doing direct transcodes via ME atm. OS is Windows 10 22H2 (fresh install) on Ryzen 7 3700X, 64GB of RAM and a GTX 1080ti.

 

I'm transcoding  Panasonic GH6 Footage (5760x4320, 4:3, 25fps, 200Mbps, 10bit long-GOP, H.265) to Prores 422 HQ with 16bpc enabled and audio set to 48000/24bit. 

I have just sent you an example base file in a private message. 

 

Cheers,

Dom

Participating Frequently
April 25, 2023

Thanks, @Dom R. for sharing the details. We will look into this. 
Mayjain