Best quality render - GPU on or off?

pilsburypie wrote on 11/28/2014, 2:42 PM
I'm running Vegas 11pro which for me is pretty stable in general. GPU acceleration works fine with my 570 graphics card. On my mp4 renders, I do however see the very occasional thin (1 pixel wide) white line flash for a single frame every 5 or so minutes. Only my critical eye would notice this.

I was wondering if this is a GPU thing..... I think I may have read somewhere that for the very best renders, GPU should be off. Is this correct?

Comments

john_dennis wrote on 11/28/2014, 3:06 PM
"[I] I think I may have read somewhere that for the very best renders, GPU should be off. Is this correct?[/I]"

"Best" implies a qualitative answer. I've looked at the quality difference and admitted that I usually couldn't see the difference in the output even when I could put two renders back on the timeline and detect that there was actually a difference.

I would say that you would get "more consistent" results with fewer hassles if you use CPU only. Many code issues have surfaced since GPU rendering was implemented and they're likely to keep coming.

Here is an example that came up recently.
Mindmatter wrote on 11/28/2014, 3:19 PM
I've had a couple of black frames twice in recent renders, once with mxf and the last one wth mp4.
On recommendations from forum members here, I totally switched off GPU, not only in the render but altogether, before rendering, and the black frames were gone in the render.

AMD Ryzen 9 5900X, 12x 3.7 GHz
32 GB DDR4-3200 MHz (2x16GB), Dual-Channel
NVIDIA GeForce RTX 3070, 8GB GDDR6, HDMI, DP, studio drivers
ASUS PRIME B550M-K, AMD B550, AM4, mATX
7.1 (8-chanel) Surround-Sound, Digital Audio, onboard
Samsung 970 EVO Plus 250GB, NVMe M.2 PCIe x4 SSD
be quiet! System Power 9 700W CM, 80+ Bronze, modular
2x WD red 6TB
2x Samsung 2TB SSD

pilsburypie wrote on 11/28/2014, 4:06 PM
I shall try CPU only to see if those little lines disappear. I posted to see if there was a difinitive answer as I suspected the difference would not be visible to the naked eye! Cheers for the replies
johnmeyer wrote on 11/28/2014, 4:41 PM
Forget that Vegas has a GPU feature. Just turn it off, everywhere you can. It apparently does work for a few lucky people, although I secretly suspect that they may also be having problems that they simply haven't spotted yet. Random blank frames are sometimes difficult to discover. I actually wrote software that would scan my renders to look for single black frames, and after I kept finding them, I gave up on GPU, never to go back.

You might still want to use GPU for playback, but only if you get a substantial improvement. Just remember to turn it all off before you render.
OldSmoke wrote on 11/28/2014, 5:35 PM
It apparently does work for a few lucky people, although I secretly suspect that they may also be having problems that they simply haven't spotted yet.

It works for those that have the right hardware; it's as simple as that.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

BruceUSA wrote on 11/28/2014, 5:55 PM
"It apparently does work for a few lucky people, although I secretly suspect that they may also be having problems that they simply haven't spotted yet.

It works for those that have right hardware; it's as simple as that."




A++++ 1000% correct :) no other way to put it.



CPU:  i9 Core Ultra 285K OCed @5.6Ghz  
MBO: MSI Z890 MEG ACE Gaming Wifi 7 10G Super Lan, thunderbolt 4
RAM: 48GB RGB DDR5 8200mhz
GPU: NVidia RTX 5080 16GB Triple fan OCed 3100mhz, Bandwidth 1152 GB/s     
NVMe: 2TB T705 Gen5 OS, 4TB Gen4 storage
MSI PSU 1250W. OS: Windows 11 Pro. Custom built hard tube watercooling

 

                                   

                 

               

 

NickHope wrote on 11/29/2014, 1:14 AM
I recommend putting the original footage, a CPU-rendered file, and a GPU-rendered file lined up on 3 separate video tracks, then compare them on the Waveform and RGB Parade (in the video scopes window) by soloing each track. This is a great way to pick up differences. I expect in many cases you'll see the GPU-rendered file differ more from the original than the CPU-rendered file, but it depends on many factors, and the difference may well be tolerable.
farss wrote on 11/29/2014, 2:51 AM
[I]" It works for those that have the right hardware; it's as simple as that."[/I]

And that would be?
Where is that information published by SCS?

Bob.
OldSmoke wrote on 11/29/2014, 8:37 AM
There was information available since VP11 if you knew how to read it and nothing has changed ever since.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

johnmeyer wrote on 11/29/2014, 10:35 AM
There was information available since VP11 if you knew how to read it and nothing has changed ever since.Can you please refrain from these snarky remarks? Bob is a really good guy and has contributed more to this forum than almost anyone I can think of. He doesn't deserve to be "spoken to" like this.

What Nick and Bob and I are trying to say is that the GPU rendering is fraught with problems for many people -- most of whom have tried really hard to find the right hardware to use but, absent any guidelines from SCS, have often failed to get a system which reliably works. In addition, speaking for myself (although Nick echoed this sentiment), I strongly suspect that the GPU and CPU renders are not identical, and that other problems may lurk in the GPU renders. I base this on having read most of the posts in this forum for the past fourteen years, including the large number of posts in the past four years concerning GPU rendering problems.

John Meyer
Grazie wrote on 11/29/2014, 11:01 AM
I agree with OldSmoke. I found it very difficult to read. Actually I could read it, but it went over my head!

We're all Stars here.

Grazie

larry-peter wrote on 11/29/2014, 11:16 AM
@nickhope,
Would using the difference compositing mode on a GPU rendered track above a CPU rendered track be a good way to compare? Or do the compression schemes have enough randomness introduced to make this test meaningless?

When I first installed 11, I noticed color fringing around thin text on a GPU render that wasn't on a CPU render. I then started noticing subtle differences in the renders whenever any compositing was involved, even crossfades. Couldn't see any difference when compositing wasn't involved. After that I just always went with CPU renders even though I get good timeline acceleration with GPU on. 560ti on one system, QuadroFX 1800 on another. Saw same results on both.
OldSmoke wrote on 11/29/2014, 1:17 PM
@johnmeyer

Provided the information in your system spec is still up to date, there is a very good reason why it doesn't work for you.
There is also a reason why I and others here are always asking for system specs when they complain about GPU acceleration.
Could Vegas be better, certainly but we first should always look at our systems before we blame the software.
As for the topic, yes there are differences in rendering with and without GPU and they are most apparent at low bitrates, 7K and lower on my system, and mostly only with the MC AVC encoders which where specifically written for certain GPUs by Mainconcept.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

farss wrote on 11/29/2014, 2:58 PM
[I]"There was information available since VP11 if you knew how to read it and nothing has changed ever since."[/I]

On behalf of the many forum members who are having issues and who you implied are at fault because they're using the wrong hardware I asked you where they could find the information. The best you can come up with is a document that:

a) Is labelled "Internal use only."
b) Is benchmark tests.
c) at least one of the cards used in the benchmark tests is no longer in production.
d) is years old.

It's neither published nor a list a recommended video cards.

If that's the best you can manage then I'd suggest you owe the forum members that you were taking a cheap shot at when you said:
"It works for those that have the right hardware; it's as simple as that. "
an apology.

Aside from that, there is one piece of information in that document that could be relevant:

"A clean uninstall of the previous driver was CRITICAL."

That's a statement backed up by multiple posts on several Windows support fora. Doing a complete uninstall of video card drivers does seem to be problematic, even if you use Windows own driver uninstallation tools it might not get rid of everything and it does seem that might lead to issues.

One tool that is recommended for getting this task done is Display Driver Uninstaller. I have not tried this, as with any such software be careful as the page includes download links to things you probably don't want on your computer. Hopefully it's an easier road to go down than what several users have had to resort to, a bare metal re-install of Windows.


Bob.
OldSmoke wrote on 11/29/2014, 4:37 PM
Oh no, that is not the only information and by the way, it was publicly available for a long time. Here is some more information.
Again, read it carefully and you will still find that it says FERMI architecture when it comes to Nvidia.
There have been numerous threads about GPU acceleration and what works and what doesn't. Members of this forum have taken their time to even test their hardware properly and publish the results here. This has been going on since VP11 was introduced and I still stand to it: if you have issues with GPU acceleration you have to check your hardware.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

NickHope wrote on 11/29/2014, 11:57 PM
@nickhope,

Possibly, especially if you're used to working that way, but I tried your suggestion on the Photoshop layers issue that John Dennis referred to above and those pale edges reveal themselves as only very dark grey on black in terms of differences. Difficult to see. I also tried it with very similar videos that were of significantly different luminance and no differences showed up at all. Personally I think it's just easier to compare by looking at the normal preview and the scopes, and not necessarily just the waveform and RGB parade. For example with that Photoshop layers problem there is a big and very obvious jump in the histogram.

One thing I did just discover is that that Photoshop layers problem actually appears to be only a preview issue. I can't get it to render out in Sony AVC or MC AVC with GPU rendering on. Which is a very good thing that gives me more confidence to leave GPU acceleration on in the video preferences. However I did get an incorrect green top border in the Sony AVC GPU render, which is a very bad thing.

Personally I don't think I'll ever do GPU-accelerated rendering, but I'm lucky that I almost never use those GPU-accelerated codecs anyway. Even if I did I think I'd let CPU-only do its thing and go put my feet up for longer. If you're churning out a lot of videos on a tight timescale then it's a different story.