Beiträge von Joe24

Did some testing here, and there does seem to be an issue with Vegas Pro 12 (and possibly 13, judging by other recent threads). I only have Vegas Pro 12, 15, and 20 installed.

Vegas Pro versions 15 and 20 seem to work fine.

When Voukoder connector is installed in Vegas Pro 12 (I tried connector versions back to 0.7.2 from 2020, along with Voukoder versions back to 5.0), hitting the Render As button in Vegas brings up the Render As menu, which displays a "Loading Templates . . . " message for a few seconds, and then Vegas crashes to Windows desktop.

Changing Voukoder versions makes no difference, and changing connector versions makes no difference. If any Voukoder connector is installed to Vegas Pro 12, Vegas crashes when clicking Render As. If you uninstall the connector, Vegas then functions normally (don't need to uninstall Voukoder itself).

I don't really want to wipe all my settings and cache from Vegas, if I can avoid it. If somebody else wants to try on their system, hold Ctrl+Shift while double-clicking the Vegas icon on your Windows desktop.

Not sure which log file to pull. There seem to be several of them. The only file in the %localappdata%\Sony\Vegas Pro 12.0\ folder containing the phrase "voukoder" is the file FFCache_x64_1033.ini , which isn't super helpful:

[voukoderplug]
Path=C:\Program Files\Sony\Vegas Pro 12.0\FileIO Plug-Ins\voukoderplug\voukoderplug.dll
ModTime=88756417
Surrogate=-1
{8266BE96-B2DC-4BF8-96AE-E7C7A337D598}=Voukoder for VEGAS
[voukoderplug.{8266BE96-B2DC-4BF8-96AE-E7C7A337D598}]
Access=32
Flags=1
StreamType=3
[{8266BE96-B2DC-4BF8-96AE-E7C7A337D598}]
DialogName=Voukoder
LangID=1033
ModTime=88756417
Renderer={93CBE59C-BEB7-40EA-A5BD-775AB67087B7}
ExtRenderer=*.mp4



(the file ends here)

In the upper right corner of your Project Properties window, change the Field Order option to "Progressive". This will render your output video as progressive, instead of interlaced.

VoPro now auto-detects which NLEs are installed. Awesome.

Make sure you turn off the "Show Favorites Only" filter in your "Render As" list.

Zitat von HuzamaAhmad

It sounds like you're facing a codec compatibility issue with Windows 10 and the Adobe suite......

Nope. Voukoder 13.1 had a bug causing the playback issues. Fixed in Voukoder 13.3.

This was detailed in the forum I linked above.

Interlacing has nothing to do with resolution or vertical/horizontal mode. You must have accidentally enabled interlace when you changed resolution.

You can disable this in your Vegas Project Settings (File -> Properties). For the Field Order option, select "None (progressive scan)."

Technically, a 1-sec GOP would be encoder Level 4.1, but changing encoder levels didn't make a difference to the results above.

I've never had great luck with TMPGEnc Authoring Works accepting video which uses encoder Level 4.1. They say it's Blu-ray compatible, but I never found how to make it work. AW always flags the 4.1 tracks as incompatible with Blu-ray, by reason of encoder level. So I just use encoder Level 4.0, which works fine. TMPGEnc Authoring Works accepts either 1-sec or 2-sec GOPs with Level 4.0 (which should be 2-sec GOP only, according to spec).

Lol, and as mentioned . . . TECHNICALLY, 1080p29.97 is non-compliant with Blu-ray anyway.

In any case, all test files above were rendered using Voukoder, and therefore FFmpeg. And they all used NVENC on an Ampere card. None of my tests yielded a file with an extra leading I-frame, so this is quite clearly neither an FFmpeg issue, nor an NVENC issue.

Zitat von avwtp

can be produced directly using FFMEG

If you are getting this problem even while using command-line FFmpeg, then we can also rule out Voukoder and its connector as the cause.

If the error occurs in command-line FFmpeg across multiple framerates and encoders (you've mentioned both NVENC and x264), then there must be a problem with your encoding settings, or maybe even with your source file's encoding from Premiere.

Out of curiosity, what are your Voukoder encode settings? And what exact command-line are you using for your FFmpeg encode?

Zitat von avwtp

1) create BluRay complaint 1080p stream, with "1 sec" GOP (30 frame) for std 29.97 video.

2) bring up SmartRender, add the clip, then in the "Format" panel click "Start Analysis". Notice it wants to render the first 2 sec. Now output the file and it creates a 61 frame GOP out of the original 3 GOPs (1, 30, 30).

3) This re-rendered file is now not BluRay compliant.

[...]

if you bring up a Vouk or FFMpeg NVENC clip in SmartRender, enable "show frame status", you'll see the solitary I frame followed by the regular GOPs ... and a blank audio frame.

I don't observe any frame-order problems with video files rendered by Vegas 20 using Voukoder/VoPro. Following the steps quoted above (except using GOP 60, which is actually the Blu-ray max for 29.97p video, and my preferred setting), the first few frames of the video are as follows, starting with frame 0: IBPBP.

Switching to your setting of GOP 30, Smart Renderer now wants to re-encode most of the video file for whatever reason (see screenshot). But the frames still remain in the correct order (IBPBP), with no extra I-frame. I assume you have a reason for rendering as GOP 30, so I'm not going to address that.

Tested some 1080p23.976 GOP 48 renders, and they cause no problems either.

I suspect, as stated before, that your problem may lie with Premiere or your settings therein. AFAIK, FFmpeg just encodes whatever frames it's fed.

See screenshots below. TMPGEnc Smart Renderer 6 doesn't complain about the video stream at all using GOP 60.

These files were encoded using Vegas Pro 20 build 411, Voukoder 13.3, connector 1.7.1, NVENC h.264. I modified a preset I normally use for Blu-ray encoding, just changing frame rate and GOP size. Normally I run 1080p23.976 GOP 48 which is fully Blu-ray-compatible.

GOP 60:

GOP 30:

Zitat von Joe24

AAC has a limit of 96 kHz.

Zitat von rsmith02

I don't understand AMF- what does that mean?

AMD's version of NVENC.

What I'm getting at is: is Smart Render "correcting" part of your video file, which is confusing something further down the workflow? Do you have the same problem with 24p files?

Did you select Vegas 21 in the VoukoderPro installer options? You have to manually select your NLE from the list.

Also, make sure you have the "Show Favorites Only" filter turned off in the "Render As..." list in Vegas.

Not sure if this has any bearing on the issue, but the 1080p29.97 h.264 format itself is not Blu-ray compliant.

1080i29.97, 1080p24, and 1080p23.976 are Blu-ray compliant in h.264.

You can also do 1080p29.97 HEVC on UltraHD Blu-ray.

List of Blu-ray compatible formats (see the Data Format Standards subheading):

Blu-ray - Wikipedia

en.m.wikipedia.org

I've done plenty of TMPGEnc disc work with NVENC renders from Vegas/Voukoder/VoukoderPro/FFmpeg, and have never seen this. If FFmpeg itself was introducing errors, you'd think I'd have had this problem too... Which makes me wonder whether your issue might be with Premiere or the settings there-in? Or maybe even your I/B-frame settings in Voukoder/FFmpeg? Just my 2 cents.

Zitat von Lan-Na

I hope Vouk will not always pursue the latest Nvidia SDK.

Or maybe you could just use older drivers and Voukoder versions if you need to, rather than demanding that everybody change to suit you?

Zitat von georgeschris

Is a Nvenc VP9 version a possibility?

Sure... if and when Nvidia builds a GPU that includes a VP9 encoding engine! So far they haven't done that.

NVENC is hardware (a special module in your GPU), and not a software program. You can only use NVENC to encode the formats that the physical chip was designed for. So you can't retroactively add NVENC VP9 support to an existing GPU.

Currently, NVENC supports formats: h.264, h.265, and AV1 (on 40-series GPUs).

Nvidia NVENC - Wikipedia

Zitat von Lan-Na

I heard from my friend that the newer NV driver has a lot of bugs. So I haven't installed the newer NV driver. If you ask me which bug, I really can't say it.

But I believe that many users choose a stable driver instead of a newer one.

Sounds like some high-quality information there. 🤣🤣🤣

The minimum NVIDIA driver for Voukoder 13.2/13.3 is v531.61, which came out in April 2023. Hardly the "newest" driver (current one as of writing is v545.92, issued Oct 26, 2023).

Install an older driver from NVIDIA's website if you're in a panic about it. Between 531.61 and 545.92, there are around 20 different driver versions to choose from.

I don't see a problem here.

VoukoderPro is currently a beta version, so it has an expiry date, after which it will not work. This expiry date is extended from time to time as newer beta versions come out. I believe the final product will be a paid version.

Voukoder classic is free.

Voukoder 13.2beta4 works here. All good.

• All NVENC-encoded files play normally, and audio is in sync.
• Tested using the same h.264 and h.265 NVENC presets as before.
• Tested Vegas 20 build 411 (connector 1.7.1) and Vegas 15.0 build 416 (connector 1.5.0).
• Tested VLC v3.0.19 64-bit. Also downgraded to the same VLC v3.0.18 64-bit which I was using before, and still no problems observed.

Zitat von Steve Rhoden (Hentys)

Using the latest version of Vegas Pro 21... Tried every configuration possible.

According to your log file, what pixel format is being provided to FFmpeg?