Really??? This HAS to have been mentioned before - surely? ("And stop calling me Shirley!")
Having selected my expensive GPU card in Accel. I really "believed" that was it - yeah? However, this is what I had in I/O:
And NOW i've switched to my NVIDIA Card and NOT my CPU procesor, INTEL QSV?:
Just picked this up from FaceBook. Kudos Dean Farrell.
Again, have y'll been doing this all the time?
Must be a browser issue. I see them (from the Options/Preferences/IO menu).
Which detailed selection down menu?
All I meant is j-v actually mentioned that I/O GPU switch before. In that topic I linked he recommended switching from Intel QSV to NVIDIA NVDEC, just like to be seen on your screenshots.
He posted screen recordings, not screen grabs.
Ah, got it!
Omg thanks for this, I had no idea I had to make that change! Yeah mine was on Intel QSV setting as well, which is odd because I have an AMD Ryzen 1700 cpu. Made the switch to NVIDIA on that setting and presto, *much* faster decode and pans. Thank you!
Omg thanks for this, I had no idea I had to make that change! ........Made the switch to NVIDIA on that setting and presto, *much* faster decode and pans. Thank you!
@RealityStudio - You’re welcome. If I hadn’t had seen that myself on Facebook the thread that @Marco. kindly linked to, wasn’t obvious to me, at all.
I just Rendered a 1mins Media with a non-rendered NeatVideo + Mercalli treatment in 3mins. Wow... I could see the GPU being used in Task Manager and the CPU being left alone to get on with what it should.
OK, the knowledge about this has got to be made more visible. The MAGIX technicians have done right for me. Hopefully now more will be made of it.
@Grazie you should have read my post a few days ago on the same subject!
https://www.vegascreativesoftware.info/us/forum/vp17-hevc-decoding-read-this--116538/#ca724818
No, it was not always there, but still I have no answer why the program makes with that option available still the wrong setting by itself.😬
No, it was not always there, but still I have no answer why the program makes with that option available still the wrong setting by itself.😬
@j-v - Actually, I was rather referring to the ancient DNA of the Vegas philosophy. Something has changed, something has. I supposed it started when, cough, cough, we got to liberate our GPU for Acceleration.
@j-v - Actually, I was rather referring to the ancient DNA of the Vegas philosophy. Something has changed, something has. I supposed it started when, cough, cough, we got to liberate our GPU for Acceleration.
It has nothing to do with Acceleration meant in Hardware Acceleration.
It is a setting in Preferences/File I/0
Yess I see, forgive me as Dutchman to have no knowing about English humor and so.
@j-v Actually, on this occasion, I was not attempting to be humorous, but rather making, I think, a valuable point regarding how the Engineers have released/loosened their grip on the code a little. This has meant them needing to work closely with, in my setup, with NVIDIA. In turn this has meant they are trusting us to make our decisions on how the NLE works. This will give them more options for us to make our own decisions.
Give Users the freedom to make this type of decision-making can only be good for all of us.
Give Users the freedom to make this type of decision-making can only be good for all of us.
I think we have that freedom because we are able to change settings, but I don't think that its good the developpers make the software as it installs now with the wrong settings, without to give at the start of the program the posibilities to make such a proper decision.
It has nothing to do with Acceleration meant in Hardware Acceleration.
It is a setting in Preferences/File I/0
@j-v - I know that, I really do. I was rather referring to the change in philosophy. Read my comment again. 😉
There are actually 2 settings in VP17 regarding enabling QSV encoding and decoding... one in file i/o and the other in general settings. The general settings one is also there in VP16. I didn't test all different combos but turned them on and off together when rendering in VP17... I imagine they'll remove the checkbox in general settings in the next VP17 update. Unchecking the box in file i/o adds about 10% to render times on my system (Asus motherboard with Intel iGpu) if source files are AVC encoded and output encoder is Mainconcept.
Wow, aren't more people mad about this? I'm really not understanding why I just found out? So for years I haven't been using my expensive NVIDIA card in Vegas because your system weirdly defaulted to Intel QSV?
I'm not techie so I don't understand what all of this means but it certainly looks like your program has a major bug that remains in 18. If I change from Auto QSV to NVDEC does that mean things should work better now and I'm getting my money's worth out of my card?
Wow, aren't more people mad about this? I'm really not understanding why I just found out? So for years I haven't been using my expensive NVIDIA card in Vegas because your system weirdly defaulted to Intel QSV?
I'm not techie so I don't understand what all of this means but it certainly looks like your program has a major bug that remains in 18. If I change from Auto QSV to NVDEC does that mean things should work better now and I'm getting my money's worth out of my card?
The auto setting utilizes the GPU decoder that is capable of decoding the most formats, which is intel QSV. So, when working properly (it isn't in your case, since you have an AMD CPU) it isn't really a bug, though it can result in users not getting optimal performance in some cases. However, in your case, it most definitely is a bug.
Wow, aren't more people mad about this? I'm really not understanding why I just found out? So for years I haven't been using my expensive NVIDIA card in Vegas because your system weirdly defaulted to Intel QSV?
I'm not techie so I don't understand what all of this means but it certainly looks like your program has a major bug that remains in 18. If I change from Auto QSV to NVDEC does that mean things should work better now and I'm getting my money's worth out of my card?
There's nothing to be mad about as this auto detection feature is new to Vegas Pro 18. We've only had hardware decoding since VP 17 I believe.
Now, I actually was mad about Version 17, where decoding also defaulted to Intel QSV. After a while I noticed this in the prefs and changed it to NVENC, thinking I'd be better of using my nice graphics card. But then for half a year I had huge stability issues and hangs until a recent driver update this spring fixed it. I had no idea that this was the reason for it and didn't get why Vegas had suddenly gotten worse.
So the lesson learned is that Intel QSV is the most compatible and stable, but not necessarily the best performance. What did I end up doing in VP 18? Well I left it on Intel QSV and all is working fine.