Beiträge von rsmith02

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.

Don't worry about us, thanks for the update and we'll be here when you're ready to do more.

That's great!

Well, with Vegas you can also filter by frame rate so I'd suggest 24p, 25p, 30p, 50, 60. You won't overwhelm users as if they apply a filter they'll only see a framerate matching their settings. (I would say this for resolution too but that's set in project properties, right)?

For HDR, currently the choices are AVC or HEVC, HDR10 or HLG. No 24p for some reason. They have NVENC templates for HEVC HDR10 or P3 only. So for HDR at least options comparable to the Vegas presets would be nice.

That's good news. Glad they are working with you on this. Magix own HDR templates don't support GPUs so perhaps Voukoder will be an option for GPU-assisted rendering to HDR.

Is there anything we can help test?

Zitat von Steve Rhoden (Hentys)

rsmith02, Everyone is aware of the new Pixel format (8-bit full range) feature in Vegas Pro 18 when it was released (a highly welcomed option)..... So this topic is no longer an issue for Vegas Pro users nor for Voukoder.

Hi Steve, you should tag fifonik not me as I am replying to a post from Friday.

Vegas shows the file as it is, so the preview is correct.

Vegas Pro 18 added a new 8-bit full range default where jpegs, full range and limited range video are all mapped to full range using metadata for video files. If a file isn't displayed properly you can manually change it from limited to full range. Vegas also has limited and full render settings upon export.

I think Vouk is aware of this and the software modified to reflect changes in VP 18.

kanilingus , see Chris's screenshot. Right above x.264 is H.264 NVIDIA NVENC, so highlight that and hit "apply."

If it still doesn't work, see Vouk's post about updating your NVIDIA drivers to the latest studio version (which you need to do anyway in Vegas- they make it easy- go to the help menu and select driver update in Vegas.)

In the Vegas render dialog, you clicked on Voukoder. Then in Voukoder you selected custom template show voukoder dialog, and then codec h.264. DO you see a preset there for NVIDIA NVENC? If so, click on it and hit apply. You can then change options if you want to further tweak the settings.

The other main option is h.264 x264 which is higher quality but CPU driven.

Thank you for explaining. Yes, those tradeoffs are understandable.

I have to read up on x264 settings as I've never dealt with this complexity before. Is there a preset for good quality, somewhat fast if greater file size? I'd use that.

I think in the past I had rendered with just the defaults as I didn't notice the "apply" button for presets and just selected it.

Here is the same project with look ahead to 24 instead of 180. link Still a good pause at the end but less than before?
Here's the fast preset: link It definitely seemed faster at the end.

One feature request would be a way to save your own presets- it's hard to remember what all these settings do and good values for them.

Here's a test with just the x.264 default settings and no presets selected. It didn't have a big pause at the end.

Is this an issue with Vegas or my system, or are the "recommended" settings not really recommended if you want reasonable speed? I'm not clear on what settings are slowing things down.

I noticed the presets from video don't seem to affect audio and there aren't audio presets. The default audio bitrate of 96kbit/s seems low. Is that and low-complexity what you're recommend?

Hi Vouk,
Here's a test using the same project as before.

NVENC
CPU x.264

The CPU one slowed down and used the CPU a lot starting at about 55%. Then it paused again on 99.4% for a while. NVENC had no pauses and finished quickly.

Thanks for looking at this- I'm glad the log file was of use. Something does seem wrong with the footer in CPU mode.

Here's the log file I got from Voukoder 6 in NVENC mode. It just flew along:

https://www.dropbox.com/s/yhvzvxjncp61…NVIDIA.log?dl=0

This render is 100% identical to the past one with the CPU. I left the selected region the same in Vegas and only changed the Voukoder render settings.

It seems like the log file is an option I have to check. Here's one of a CPU render that was faster than Vegas for the first half (15fps vs 12) but then slowed to a crawl and spiked CPU usage and sat for a while at the end:
https://www.dropbox.com/s/5f1bqru3qzfj…0power.log?dl=0

No, I left the settings under output as is. I did these tests with "general purpose recommended" for x264 and used the only default for NVENC (good quality).

6rc with Lanczos also cuts through the same render with no delays or issues, so it seems equivalent to 5 from what I can tell.

I did a regular CPU VBR render with Magix AVC. CPU usage climbs towards the end, but the pause at the end of the render was only a few seconds.

I uninstalled 6 and reinstalled Voukoder 5. You seem right about it, I'm having the same slamming of the CPU from 58% and it's sitting at 99.7% for a while again for some reason. There's nothing going on at the end of the clips to render (no fadeout or transition or anything).

I tried again with 5 and NVENC with the output filter (Lanczos) and it flew through the whole thing- no pauses, stops and no hitch at the end.

Where is the Voukoder log? It's not in the Voukoder program folder.

I think the presets need to be renamed to correct the English and put them in a consistent naming format.