MP 7,1 Premiere Pro Export Only 20% CPU usage? and Hardware Encoding Unavailable.

zhpenn

macrumors regular
Original poster
Aug 27, 2014
188
74
Mac Pro 2019, 28 Cores + Radeon VII +580X to export a VR camera footage super slow.


In the setting, I can ONLY see there are Metal and OpenCL selection.
Is there a place to select use VII or 580x?

When exporting, under Encoding Setting, when select Hardware Encoding, it shows Unavailable.

Then I select software Encoding, but when exporting I have a look at the CPU usage, it only uses 20% of the power, is this normal?

I'm sorry because I'm a Photo Guy, not very familiar with Videos, is there any other setting I need to do?


Thanks a lot

Screen Shot 2020-02-14 at 2.47.36 am.png




Screen Shot 2020-02-14 at 1.56.07 am.png


Screen Shot 2020-02-14 at 1.54.03 am.png



Screen Shot 2020-02-14 at 1.41.58 am.png
 
Last edited:

jasonmvp

macrumors demi-god
Jun 15, 2015
222
171
Northern VA
Mac Pro 2019, 28 Cores + Radeon VII +580X to export a VR camera footage super slow.

Is there a place to select use VII or 580x?
In the setting, I can see there are Metal and OpenCL selection.
Premiere is very picky about what it'll allow for hardware encoding, and you might be pushing it too far with your 5K resolution. It'll do 4K/VBR @ 60FPS if I remember correctly (I'm not at my Pro at the moment). It'll also do smaller resolutions like 1080p/60, etc.

Make sure you're doing Variable Bit Rate first, and then see if it allows hardware. If not, then start playing with your output resolution. Just understand it's not going to make a huge difference because the hardware encoders on your GPUs are ... slow.
 

chfilm

macrumors 68030
Nov 15, 2012
2,775
1,524
Berlin
Premiere is very picky about what it'll allow for hardware encoding, and you might be pushing it too far with your 5K resolution. It'll do 4K/VBR @ 60FPS if I remember correctly (I'm not at my Pro at the moment). It'll also do smaller resolutions like 1080p/60, etc.

Make sure you're doing Variable Bit Rate first, and then see if it allows hardware. If not, then start playing with your output resolution. Just understand it's not going to make a huge difference because the hardware encoders on your GPUs are ... slow.
I also had this frustrating experience with the hardware encoder at first, but it does Work with certain settings. Definitely make sure you have set it to one pass only.

About the CPU usage... well WELCOME to ADOBE LAND! Where Software runs on years old, dusty engines, with stuttery UIs, laggy, sluggish scrolling On HiDPI Displays and and EXTREMELY underwhelming core utilization during work and render (not to mention the lack of GPU usage).

It‘s time to learn Resolve for editing and to educate our clients to switch systems. Premiere‘s star is sinking if they dont do something about this soon! At least that‘s what I hope, it‘s unbearable.
 

zhpenn

macrumors regular
Original poster
Aug 27, 2014
188
74
I also had this frustrating experience with the hardware encoder at first, but it does Work with certain settings. Definitely make sure you have set it to one pass only.

About the CPU usage... well WELCOME to ADOBE LAND! Where Software runs on years old, dusty engines, with stuttery UIs, laggy, sluggish scrolling On HiDPI Displays and and EXTREMELY underwhelming core utilization during work and render (not to mention the lack of GPU usage).

It‘s time to learn Resolve for editing and to educate our clients to switch systems. Premiere‘s star is sinking if they dont do something about this soon! At least that‘s what I hope, it‘s unbearable.
so, the 20% usage is normal?wtf....
thanks a lot for the info, and btw, how is fina cut pro goes compare to Resolve and premiere
 
  • Like
Reactions: chfilm

Neeco

macrumors newbie
Feb 13, 2020
2
0
so, the 20% usage is normal?wtf....
thanks a lot for the info, and btw, how is fina cut pro goes compare to Resolve and premiere
Premiere will use 100% of CPU and GPU when using more advanced raw codecs.
 

zhpenn

macrumors regular
Original poster
Aug 27, 2014
188
74
Premiere will use 100% of CPU and GPU when using more advanced raw codecs.
if i want up upload good quality VR 360 to you tube, use less space will be great, which codes should i use? im using h264
 

jasonmvp

macrumors demi-god
Jun 15, 2015
222
171
Northern VA
Premiere will use 100% of CPU and GPU when using more advanced raw codecs.
That's an over-simplification and not really accurate. You can get Premiere to pin the CPU on some systems depending on the CODECs you're using and what you're trying to do. Premiere uses the GPU for very few things, however; mostly accelerated effects. So if you have a pile of accelerated effects on the time line, you might see the GPU warm up a bit. But it'll probably never hit 100%. At least not a modern day one.
 

zhpenn

macrumors regular
Original poster
Aug 27, 2014
188
74
I found that when using PR editing it will use a lot VII GPU, even when I only plug the monitor in 580x, it will still use VII for computing, I can see GPU usage in Activity monitor very high in VII. only export will be slow
 

bsbeamer

macrumors 68040
Sep 19, 2012
3,476
1,766
Hardware encode is VERY dependent on codec/format and almost always 1-PASS VBR style is the most compatible.

There are added restrictions based on XEON CPU vs. Core i5/i7/i9 CPU and XEON is not compatible with several of the hardware encode options. That is a CPU limitation, nothing that can be unlocked unless the hardware acceleration "tricks" for MP5,1 can be implemented in MP7,1. Take a look at VideoProc and search this forum for more info on the testing.

If you're running into lack of GPU usage, or multiple GPUs with lack of usage would suggest attempting with headless adapters. It's a workaround that has solved more than one issue in Catalina previously and helps in nearly all testing across products, including eGPU so far.
 

Neeco

macrumors newbie
Feb 13, 2020
2
0
That's an over-simplification and not really accurate. You can get Premiere to pin the CPU on some systems depending on the CODECs you're using and what you're trying to do. Premiere uses the GPU for very few things, however; mostly accelerated effects. So if you have a pile of accelerated effects on the time line, you might see the GPU warm up a bit. But it'll probably never hit 100%. At least not a modern day one.
Apparently my Activity Monitor and export times are lying then?
 

zhpenn

macrumors regular
Original poster
Aug 27, 2014
188
74
To make full use of the GPU, I export one task using Media Encoder, the other task exporting in PR
2 tasks at the same time
CPU still 20% usage, but GPU usage from 50% jump to 90%.
is H264 Really make very limit use of CPU?
 

h9826790

macrumors G5
Apr 3, 2014
13,484
6,185
Hong Kong
VCE only support up to 4K DCI. Your preset has 5120x2560 resolution, which explain why you can't use HWAccel.

For low CPU usage. I don't know the actual reason. However, I don't expect ME can use all 28 cores. My understanding, even video encoding can is a multi thread process. There is still a main thread. All other threads can just assist this main thread.

So, let's say this software's main thread can only handle up to 12 threads on your setup, then you will see about 21% CPU usage overall. But not any higher.
 

h9826790

macrumors G5
Apr 3, 2014
13,484
6,185
Hong Kong
btw is the navi base 5700 will have a lot better H264 export speed?
I doubt.

The new hardware usually has better driver support in Windows. And it seems the VCN on 5700 is just at the same performance level at RX580 when doing screen recording, and it's very slow in FFMpeg transcoding.


Also, it seems VCN also max at 4K only. So, in your case, you still can't do hardware encoding with that preset.
 
  • Wow
  • Like
Reactions: chfilm and zhpenn

chfilm

macrumors 68030
Nov 15, 2012
2,775
1,524
Berlin
I doubt.

The new hardware usually has better driver support in Windows. And it seems the VCN on 5700 is just at the same performance level at RX580 when doing screen recording, and it's very slow in FFMpeg transcoding.


Also, it seems VCN also max at 4K only. So, in your case, you still can't do hardware encoding with that preset.
Wow this looks like a major bummer for the folks holding out for the 5700 precisely for this hardware encoder..
 

deconstruct60

macrumors G3
Mar 10, 2009
8,555
1,508
Wow this looks like a major bummer for the folks holding out for the 5700 precisely for this hardware encoder..
Hardware isn't the primary issue. If go to around timestamp 10:20-11:00 in the video can see that AMD hasn't put much work (or progress) into the H.264 encoder here for years. The 5700 (Navi ) switches to a new encode engine (VCN) from (VCE) so this small bump likely is just to get back to same status quo they had.

The true core issue here is whether the 'closed source' macOS drivers will have real effort put into them or just as equally commitment to the status quo ( or less relative to where the open source library has some support) .

If no one does any work on the software drivers, it won't make any difference if there is better hardware down below. If folks are hoping that can brute force unoptimized software with brute force through better hardware .... that usually isn't a good match to ASIC circuits.
 
  • Like
Reactions: chfilm

deconstruct60

macrumors G3
Mar 10, 2009
8,555
1,508
....
The new hardware usually has better driver support in Windows. And it seems the VCN on 5700 is just at the same performance level at RX580 when doing screen recording, and it's very slow in FFMpeg transcoding.


Also, it seems VCN also max at 4K only. So, in your case, you still can't do hardware encoding with that preset.
It looks as though the VMF he was probably using was "older" . The video is dated July 9th. Here is the release dates for the VMF.

https://github.com/GPUOpen-LibrariesAndSDKs/AMF/releases


Unless grabbing some other development fork 1.4.9 was 'current' around July 8th ( presuming did work before uploaded video ). 1.4.9 dates from Sept 2018 (long before 5700 would have been even in tape out stage). What probably have is software that thinks it is feeding at 480/580 and get the same results. That should be a big surprise. Perhaps had some beta 1.4.14 for the new hardware ( which is in the "3 newer tags" ). 1.4.16.1 is pretty bleeding edge (this month).
 
  • Like
Reactions: OkiRun and h9826790