Intel i7 6850K and RTX 2080 Ti but no CUDA accelleration on warp stabilizer

Forum|Forum|6 years ago
August 5, 2019
4 replies
2178 views

GPU-usage stays as low as 1% whereas the CPU is doing the job. Mercury Playback is activated, newest Nvidea Studio Driver 431.70 installed (with 431.60 wasn´t better). Brandnew RTX 2080 Ti doing nothing. Same result I had on my old GTX 970 though... Using Mainboard AII X99 from Asus, 32GB RAM, SSD etc.

This topic has been closed for replies.

MyerPj

Community Expert

Yeah, what R Neil Haugen said!

It's just something to try to see if your 2080 is being used. There's also a PP benchmark from Bill Gehrke, but unfortunately he hasn't been around for awhile. His benchmark if you can find it, really fired up you graphics card also. So in lieu of that, try creating the proxies with a scaling and you can see if PP is using your card where it can.

Adobe Premiere Pro Help | Ingest and Proxy Workflow in Adobe Premiere Pro

https://www.google.com/search?q=premiere+pro+proxy+editing

R Neil Haugen

Legend

I've got a BlackMagic PCC4k now ... and I love the files from that camera. Especially, I love the BRAW format. But even the higher quality ProRes has a very wide dynamic range, a very "thick" 10-bit file.

My poor machine here ... even on 1/8th res in playback ... stutters horribly with both the BRAW (using the Autokroma plugin) and the higher-Mbps ProRes files. It's only a 6-core I7-6800k at 3.4Ghz with 32GB of RAM. All "working" drives either M.2 or regular SSD. Spinners used for mass storage but not working projects or their media.

So ... I'm looking over the Puget Systems and Safeharbor Computing systems again. My builder done left the state, so ... I'll be just buying one from them. Sometime twixt now and October 1 I figure I'll pop the cork on it.

And ... gonna have it preloaded and tested by them (as they do!) for Premiere, AfterEffects, and Resolve.

Gonna take a chunk of change but ... I gotta get the work out, you know? Sigh. Neither Premiere, AfterEffects, nor Resolve work particularly spiffy on this "small" a rig. Not with that media, nor some of the RED I occasionally get now also.

Neil

Everyone's mileage always varies ...

J

JofikahnAuthor

Participating Frequently

Yeah, Neil - cheers!
It looks as if we´ll never get enough "operation power", though (especially concerning our budgets). After reading the newest tests from Puget Sys (and comparing the CPU benchmarks) I recon we´ll have to wait for some kind of "chinese wonder" e.g. quantum computer. I just read they recently patented an incredible amount of new inventions on this field...

MyerPj

Community Expert

You might want to try making some proxies just to see things work. I have the same processor as you with an gtx-1070. Here's some screenshots making 4K -> 720p proxies and 1080p -> 1080p.

With the former, both gpu and cpu are at 100% (considering the scaling of the proxies). In the later, the gpu is only at 17% when no scaling is involved.

PP 2019 - Making Proxies - Runs Well wTask Manager | Adobe Community

J

JofikahnAuthor

Participating Frequently

Thanks MyerPj
Sounds interesting and the grafics you´re providing are impressive. But I´m afraid I can´t follow you. Just stopping unnecessary system tasks doesn´t make a proxi, right? How or maybe where do I make a proxi "from ...."? And why should "making a proxi" force or allow the GPU to run at 100%?

R Neil Haugen

Legend

The example used demonstrates how the GPU is used. As MyerPJ notes, when doing scaling from 4k->720, the GPU is used heavily because it is being used some for the general process and a ton for the scaling.

For creating proxies with same-size as original media, so no scaling, the GPU use drops dramatically. As the process of basic encoding is mainly a CPU task.

And he has a number of links on the background processes one can eliminate in the OS Task Manager that reduce the load on the system/CPU so that Premiere can run faster. And of course, one of the reasons he gets the performance he does from the CPU is that 4.39Mhz CPU speed ... awesome!

Neil

Everyone's mileage always varies ...