Comments

xberk wrote on 1/8/2019, 8:48 PM

Yes. No harm expecting.

Kinvermark wrote on 1/8/2019, 8:53 PM

No. It already uses GPU processing extensively. You could improve your GPU by spending more money, however. :)

espen-braathen wrote on 1/9/2019, 8:22 AM

There is no GPU decoding activity at all when I play back the timeline or in the trimmer window. :-p

If I apply like lens correction from NewBlue FX there is 3D and COPY activity on the GPU.

 

If I playback the finished render directly from my SSD or watch a YouTube video its full GPU video decoding.

 

With NVENC I can encode the 4K render and watch a 4K YouTube clip at the same time no problem.

 

Clearly there is substantial benefits from using the GPU for decoding the playback during editing in the trimmer and timeline?

espen-braathen wrote on 1/9/2019, 8:24 AM

No. It already uses GPU processing extensively. You could improve your GPU by spending more money, however. :)

LOL. My GPU is only running like 50 per cent max with Vegas doing a 4K encode with NVENC.

espen-braathen wrote on 1/9/2019, 8:28 AM

4K render with lens correction and simultaneous 4K playback.

 

klt wrote on 1/9/2019, 8:57 AM

I saw other graphs too. Compute0, Compute1.

And if memory bandwith is maxed out between CPU / GPU then the GPU has to wait more to get the data to process. So those Windows 10 graphs are just indicative only.

 

Kinvermark wrote on 1/9/2019, 9:00 AM

That's right. you cannot judge what's going on in Vegas by the simple windows component traces. Typically, media decode is done by the CPU and effects, etc by the GPU. This is true of other NLE's too.

espen-braathen wrote on 1/12/2019, 12:12 PM

Vegas clearly only uses CPU for video decoding so a rewrite of this section of the software into GPU compatible code could improve performance tremendeously.

bob-h wrote on 1/12/2019, 5:14 PM

There is no GPU decoding activity at all when I play back the timeline or in the trimmer window. :-p

Clearly there is substantial benefits from using the GPU for decoding the playback during editing in the trimmer and timeline?

davinci resolve timeline playback has a cpu & gpu signature like a media player, it does the GPU decoding & it's really impressive. It means I can edit 4k30p footage on my slow i7 & get timeline playback of 30fps using only 35% cpu and under 20% gpu. Same file with vegas 1fps 100% cpu & it's not usable.

With all the problems of v16 & yet to date only 3 revisions, it would seem unlikely they have the ability to improve efficiency

Kinvermark wrote on 1/12/2019, 7:11 PM

@espen-braathen

An NLE is a lot more than a media player. Maybe give the developers some credit for having insight into the best way to make a balanced system - it is what they do for a living after all!

@bob-h

Can you upload (dropbox?) a sample of the media type that only gets 1 fps in Vegas and gets full playback in Resolve?

 

 

espen-braathen wrote on 1/12/2019, 7:46 PM

@Kinvermark

Well, the developers of Vegas have no advanced knowledge of GPU use it seems. 100% CPU is not a balanced system.

@bob-h

Unfortunately full GPU use is only in the pro version at 300 USD and it can't even be validated in any way as far as I know without entering a license key. So, yes I have heard that Resolve is the most GPU friendly software at the moment.

Kinvermark wrote on 1/12/2019, 7:57 PM

1) It is not 100% cpu. It is CPU for media decode, and gpu for timeline processing (FX etc.) Try for yourself. Compare cpu/gpu usage during playback with no fx to payback with many fx. Try a few different ones as not all are gpu accelerated and some use it more than others (e.g. neat video).

2) DR does use the gpu in the free version, just not multiple gpu's. Again, a simple test will prove this (turn on/off in master settings and test a timeline loaded with fx.)

bob-h wrote on 1/12/2019, 8:37 PM

 

@bob-h

Can you upload (dropbox?) a sample of the media type that only gets 1 fps in Vegas and gets full playback in Resolve?

 

 

I used losslessCut to edit out a piece for you to test but surprisingly I can playback the 30second clip just fine in vegas15 no dropped frames 60%cpu 12% gpu, but the full video is unplayable in vegas.

Actually I started a new project with the same original video file & timeline without any plugins. It is working just fine (60%cpu) yet unusable last time I tried. I falsely maligned the good name of vegas!

Kinvermark wrote on 1/12/2019, 8:53 PM

Thanks for your honesty. Sounds like you may have some issues to work out with your setup. :)

FWIW, my 8 year old system (specs in signature ) gives me a decent editing experience (not great, but workable) with UHD footage in Vegas (14 or 16), but is unworkable for editing in Resolve. The Windows 10 CPU/GPU usage signature for simple payback is quite similar for Vegas / Resolve / Premiere (something like 20% CPU, 10% GPU) with the only major difference being that Resolve is very aggressive about grabbing Video RAM (grabs all 4GB right away) whereas Vegas sometimes grabs very little VRAM or ramps up slowly.