4k editing without proxies lagging premiere using cpu instead of gpu

I know this thread is old but I felt compelled to jump in here. As mentioned, creating proxies is absolutely necessary. I'm not sure even a threadripper could cut through 4k, HEVC, Long-GOP footage without stuttering.

As far as I remember, leaving IGPU enabled is crucial for taking full advantage of Intel's QSV. Unless you use 2-pass encoding for export, leave IGPU enabled and your exports will be pretty quick.

Lastly, I remember reading the RTX 2070 was the sweet spot for PP somewhere. It might have been a Puget Systems article. I believe PP leverages dedicated GPU's for several more tasks now that this thread was created. As mentioned, the Adobe developers/engineers are adding more and more features as time goes on. I do speculate that there is a deal between Intel and Adobe though that will ultimately always leverage the full architeture Intel chips have.

In the end, just use proxies (it's what the pro's after all) and enjoy your dedicated GPU by playing some graphically intense PC games!

Not sure if mentioning other brands is OK here, but I've switched to davincy resolve 16.. Taking full advantage of my GPU now and editing h265 4K without proxies or transcoding

https://www.youtube.com/watch?v=C5nJ4RMy8mU

What will you be using?

I have switched to another program that actually can use the NVDEC and NVENC out of the box. I can now edit 4K without transcoding or creating proxies. Finally the decoder of my GPU is used, jeej!

100% CPU and 52% GPU, great, you've done well. PP only use one graphics card so you need to disable the onboard GPU, it's a weakling compared to your Nvidia. The high-end CPUs typically don't have onboard video as they know users of those CPUs will want to add a good card like your 2080.

Did you create proxies of a different size as your footage, ie: 1080p or even 720p. Your video card is used for the scaling. Also, make 5 or 10 proxy files, and time them, then switch your graphics card on and time it there, and let us know the numbers.

The engineers over time add in more capabilities from and for various hardware so perhaps they will add the hardware decoding from those cards.

CPUs often make use of the onboard graphics chip for certain things, but that is something about the way that motherboard and CPUxare designed to work, separate from the coding of any app. Sometimes it is useful to have the onboard graphics enabled and sometimes the CPU will nearly ignore a discrete GPU if the onboard is enabled.

Neil

Some screenshots when creating proxies. 

shot 1 and 2: here I have my onboard intell graphics card enabled. As you can see it's used for decoding. The specific NVDEC chip on my RTX is not used at all. The GPU is used indeed, but not for decoding! CPU not being used here.

shot 3: I disabled the onboard graphics card trying to fore media encoder. No luck at all, it now starts using the processor instead and CPU is spiking to 100%. 

Since NVENC and NVDEC is specifically meant to do hardware encoding and decoding of h264 and HEVC I hope PP and/or Media encoder will support it soon and then I doubt if I still need proxies in my workflow.. 

Thanks @R_Neil_Haugen ; Till your message I was not familiar or awar of what kind of workflow professionals are using. I guess I have to resign then and start using proxies again of transcode. But it still makes no sens to me that PP is not leveraging NVENC en NCDEC (https://developer.nvidia.com/nvidia-video-codec-sdk

I now have a video card which has specific hardware to encode and devoce from h264 and hevc but it's not used at all. 

@myerPJ; my hardware specs was a copy paste from dell order form. The first part is to be ignored indeed, it's Dells article code :). I dont really want to sell the card although it's a 1200 USD card, I just want it to be used. It now seems that PP is using CPU and my internal intel GPU, so not quite sure why I even need a dedicated graphics card at this point.

My media is constante framerate, gopro 7 and dji mavic 2 pro 4k footage. I will test out how Media encoder will use the video card while making proxies, but as far as I have read from other threads and officiel Adobe communication it will not use my specific NVENC en NVDEC processing units, whith is pity.. 

Yes, go ahead and sell it, you seem to want to do that.

A 2070 would suffice.

Your hardware specs are incredibly hard to read,.. I thought it was me, but then I did a google search for "486-33818 D00AWR811 1 SR" and google found exactly 1 page... this one! 🙂

Is your media constant frame rate or variable. That would be the kicker for me to transcode or use proxies.

As Neil mentioned people think "I shouldn't need to stoop to this ... " using proxies, etc... your's is a decent machine, with not quite enough memory to balance it, but that's not what's holding you back. h.264 and 5 source footage is going to need some help going forward. Might as well develop a workflow now.

If you want to see your cpu and gpu really performing, make some proxies (720p or 1080p). Here's a picture of Task Manager running while I'm doing so...

https://community.adobe.com/t5/Premiere-Pro/PP-2019-Making-Proxies-Runs-Well-wTask-Manager/td-p/10418307

Post a similar screen shot of your Task Manager while doing something interesting in PP. We'll take a look at your running tasks... it should be insteresting with a machine from Dell.

I'm puzzled by people who for some reason have issues with standard pro editing practices whether it's proxies, transcodes, finishing AfterEffects comps and replacing the comp on a sequence with finished media, smart rendering, all that sort of thing.

I deal with colorists that have rigs with 6 or more GPUs in them running various post processing apps who still use transcode or proxy media. It's the idea that seems like "I shouldn't need to stoop to this ... " to me. Those techniques are a large and continuing part of the entire post processing business. You don't think major movies don't use transcoding, proxies, digital intermediates, all that?

Personally I figure that if people with $20,000 plus in the computer and $30,000 in monitors do it, I'll probably be  wise to follow along. And I know people with rigs well above those costs. NOT mine thankfully. I can't justify that kind of expense.

And I've colorist friends who work 6k Red r3d files no problem but immediately transcode all long-GOP.

Another and important part of the business is knowing which app you're going to use, and getting hardware suited for the app.  Studying the documents tfat both Puget Systems and Safeharbor Computing publish on their sites is very useful for that, as they build for machines specifically for Premiere, or AfterEffects, or Resolve,  or Filmlight, whatever you're using.

Neil