Beiträge von Joe24

Zitat von EMDave

For some reason DVD Architect want to recompress it again

DVD Architect is stupid like that... and will never tell you why it doesn't like something. I didn't find a way to make DVDA work with any non-Vegas MP2 DVD renders, and got tired of fighting with old buggy (and abandoned!) software.

I switched to TMPGEnc Authoring Works and never looked back. Quality code, uses your GPU for MP2 encoding, and if there's a problem with your files it'll tell you what it doesn't like about them.

If you're making Blu-rays, TMPGEnc will take Voukoder-encoded MP4 files with no recoding (as long as your files meet the Blu-ray specifications). If you're making DVDs, TMPGEnc will port your Blu-ray project to DVD, and has GPU-accelerated MPEG-2 transcoding built-in.

There's a trial period if you just want to download and try TMPGEnc.

Zitat von Vouk

Voukoder Classic and VoukoderPro - both Apps will be free and Open Source.

Holy..... Really? I've been sitting here waiting for the paid version of VoPro since forever. As have other people.

Not complaining, I guess, but I hate to see all your care and effort go unrewarded.

Usually means the video/audio that you're sending to Voukoder isn't in an acceptable format. Post your log file.

Zitat von Jorge Luis

I don't know why but I like vegas 12 more then 20.

Not unusual to dislike 20. I prefer 15 myself.

Right, thanks for that. Here's what's happening in Vegas Pro 12, as discussed above:

Full quality screen capture: crash.zip

Vouk Any chance of getting the forum upload function fixed?

Zitat von Jaro

sorry, I dont understand.

Relax. I'm just agreeing with you, and providing a video showing the crash happening. Yes, Voukoder connectors cause Vegas Pro 12 to crash.

I wonder if it's a glitch in how templates are being reported to Vegas by Voukoder.... because this issue happens while Vegas is trying to populate the Render As list.

(This forum is currently refusing to upload files, which is a separate issue.)

I'm using 8-bit.

This forum won't allow me to upload a screen capture of the crash. Tried uploading in GIF format (3.4 MB) and ZIP format (4.7 MB). Neither works, although the stated upload limit is 20 MB, and both file formats are listed as supported. Hmm . . .

(Webpage error: The file size exceeds the PHP limit "upload_max_filesize" and/or "post_max_size".)

EDIT: see screen capture posted below in Post #15.

I haven't used my copy of Vegas 12 for about a year and a half (July 2022), judging by the log files. It got to be a hassle changing the connector back and forth (uninstall/reinstall) between 12 and 15 every time.

But I know it did work with Voukoder at one point, and I'm pretty sure it was working last time I used it a year and a half ago. Tried the Voukoder/connector versions from that time period, though, and no joy.

Maybe something changed with Windows folder permissions etc? It's odd that no connector versions seem to work with Vegas Pro 12.

In "About Vegas Pro" -> "Components", voukoderplug.dll is listed. So the connector appears to be properly installed.

I did do a fresh install on a different computer, and behavior is identical.

Possibly the same issue as:

Thema

Sny Vegas Pro 12 - Voukoder not working problem

Hello,

I am new here.

I use rather old version Sony Vegas Pro 12.
I have downloaded the latest version Voukoder and connector VEGAS Pro (Version 12-17.
Installation was ok but when I try to render there are no templates, empty.
I had to uninstall Voukoder.

So, will Voukoder work with Sony Vegas Pro 12 ?

Jaro

12. Januar 2024 um 21:09

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.