Hi, community. There are dozens of posts here about Media Encoder being horribly slow and Premiere Pro doing the rendering about 10 times faster. I came accross this problem myself when I'd sent a finished project into Me and after 10 hours of work on another project found Me hadn't done even half of the job.
I'd like to share my thoughts about it. The culprit is Microsoft. Dah
With the introduction of the mixed-core technology in 12-14th gen Intel processors, where there are P-cores and E-cores that are much less powerfull but at the same time are more power efficient, Microsoft introduced new updates in their operating systems - Win10 and Win11 - where the tasks that your CPU deals with were queued in such a way that if your current programme had an active window - that is you are currently working in it - the P-cores were involved, and if you minimized the program's window or just started another program and made its window active - the small e-cores started working with the program in the background and the big P-cores switched to the new one. The most interesting thing about it is that it does not matter whether the current program demands such power as the P-cores suggest or not. You may open a notepad and start typing text and all those GHzs of P-cores will compute it instead of a more powerhungry 3D-rendering running in the background.
This happens with Media Encoder and Premiere Pro as well. Normally when you start rendering in Premiere Pro you cannot minimize it's window so the program remains active till the rendering is over. But when you send a project to Me it normally runs in the background. Surely you can maximize its window and watch it do the job but frankly no one does it otherwise what's the point in using Media Encoder instead of Premiere Pro. And at the same time you may start rendering in Premiere Pro and open Youtube to watch a video - Premiere Pro will also switch to the small cores but as a matter of fact their impact on Premiere Pro is not as big as on Me.
The only way to fix Media Encoder AND Premiere Pro switching to the small e-cores and this reduce the render times (that is make them normal as they should be) is to force Windows 10\11 to always use the big P-cores for those products in the Task Manager. You have to switch off ALL the e-cores if you want this fix to work.
Share your thoughts, people.
1
Reply
And another thing to note. If you don't want to look at Premiere Pro\Me during the whole process of rendering in order to keep them work on P-cores, you can open some youtube video or a movie player, make Pr\Me window active and then hover your mouse pointer over the preview window on the windows task bar thus making your video player\youtube fullscreen in preview. This will still keep Pr\Me window active but you will be able to watch a movie
AdChoices