Thank you, I did. There are numerous other issues affecting VSTs but this is the only one I found that causes issues with Voukoder so I thought I'd mention it here, too.
Beiträge von rsmith02
-
-
Great question. I only used this plugin as there is a bug with the VST engine and the Fx I normally use!
Anyway, just loaded VP 19.643 and applied the same TDR NOVA Fx to the same file. The Voukoder render completed without issue.
-
I am not sure this is a Voukoder issue rather than a Vegas one but with VP 20 my 64-bit VST 2 TDR Nova Fx works fine until you go to render. I am using 11.3.2 with a manually pasted connector.
It crashes with an x264 or NVENC preset with Voukoder instantly. It works fine with MagixAVC (Mainconcept or NVENC) in Vegas.
Voukoder otherwise worse as expected in Vegas.
-
VP 20 has only been out for a day so it's not so late.
-
For % of the GPU used, just looking at one figure is almost useless. Click on the GPU and see decoding, 3D, CUDA and encoding and watch what it does during a NVENC render.
-
What do you mean by doesn't support? Try the current Studio Driver. Other 3080s work, I'd be surprised if the Ti version doesn't.
Here's a render benchmark sheet comparing different GPUs. Bunch of 30XX cards on the list. -
-
I see YouTube recommends
ZitatHigh Profile 2 consecutive B frames Closed GOP. GOP of half the frame rate. -
In VP 19, media rendered with Voukoder x.264 is now flagged with a warning that it is not an efficient format for editing. I contacted Vegas staff about why this is happening and they reviewed the output and determined it was the very long GOPs. This warning was intended for highly compressed Zoom files.
For editing they recommended GOP length no greater than 1-2 seconds of footage (so GOP of say 30) whereas general purpose recommended, maximum useful cost possible, etc. are setting it to maximum lengths of 300, 480, etc.
I suggest reducing the GOP length of presets for x264 renders to facilitate further editing as some of us are using the output again in future projects.
Also, CRF for the general purpose recommended is also maybe higher than necessary? Default is 23 but it's at 17 which might better suit a high-quality preset.
-
Strange. It clearly sees your GPU. I did it with the exact same settings on my 1050 and it worked.
In case media is an issue (Vegas is failing to send frames to Voukoder), could you try with just generated media or a picture or a benchmark project?
-
Thanks for clarifying that!
-
What other project settings? Voukoder ignores Vegas project settings.
Just set the render settings you want (I made a generic one with the encoder/quality I want and then a second that adds a filter to downscale to HD for when I want to do that in Voukoder).
-
You are using Vegas? Can't you save it as a custom template with your desired settings?
-
Hi Fedosiki, that doesn't sound like you used QSV (1:3 is slow). What settings did you use?
Your processor appears to have Intel® Iris® Xe Graphics which I'm not really familiar with. https://ark.intel.com/content/www/us…o-4-20-ghz.html
-
Audio is working here with 9.2 and X-AVC media with x.264 export.
-
It seems to depend on driver version or type.
I haven't had a QSV option in 1+ years in Vegas Pro for MagixAVC or with Voukoder. I'm using i7-7700HQ processor in a Dell XPS 15 with Intel DCP latest driver.
Oddly it seems to work with MagixHEVC. -
Thanks for following up on this. Makes sense!
-
Is it possible to add the Lanczos-4 resizer as a filter for zscale? I read it is quite high quality.
-
Try the NVIDIA Studio Drivers, but yes, rendering might be CPU-limited on this machine.
-
This is user error. You are trying to apply methods from old versions of Vegas to VP 18.
Stay in 8-bit full range. Don't do anything special to adjust levels. Don't change anything with the preview window settings. Output a x264 file with Voukoder and it will work as expected on your TV, YouTube, Media Player, etc. It all expects video levels (but may work with full). Just to make sure this is correct I did just this and brought back into Vegas in 8-bit legacy mode to check the levels. It's video levels.
Also, QSV needs a really high bit rate to not look terrible. Try x264 if you're not in a big hurry.