Beiträge von Joe24

A few issues noticed while experimenting with Vegas Pro 20.0 and VoukoderPro v0.7.1.4:

• NVENC VBR target video bitrate is not being observed, although the max bitrate seems to be working. This affects both HEVC and h.264. Didn't try AV1. Tried to set a target video bitrate of anywhere from 2500-512000 kbps etc., but actual output is 200-400 kbps. If 2-pass is enabled, things get even worse (< 200 kbps).
• AAC encoding setting of 96 kb/s CBR gives 128 kb/s. Other bitrate settings seem correct. This could possibly be an issue with the MediaInfo app.
• If Vegas' output file name and VoukoderPro's output file name are not in the same folder/drive, the render hangs.
• If you are creating multiple output files without specifying a unique name for each file, VoukoderPro will write both streams to the same file, resulting in a corrupt file.

Zitat von Vouk

Maybe you need to uninstall the VoukoderPro completely first.

Correct, v0.7.1.3 was still installed. Uninstalled both versions, reinstalled v0.7.1.4.

v0.7.1.4 is confirmed working here, alongside Voukoder connector v1.6.0.

Thanks!

Still broken here. But there's a workaround now.

Zitat von Vouk

So there is a conflict with both plugins installed?

Seems that way. Vegas Pro 20.0 won't load VoukoderPro if the Voukoder connector (v1.6.0) is installed. Haven't tried other connector versions. See my previous post for log file.

No it does not. Here's fileio_x64.log with both Voukoder and VoukoderPro installed:

fileio_x64.log.txt

In any case, uninstalling the Voukoder connector fixes things, and reinstalling it breaks everything again.

The string "VoukoderPro" does not appear in the log file.

vegas_script_x64.log.txt

EDIT: FIGURED IT OUT! Uninstalling the Voukoder connector v1.6.0 fixes the problem. Looks like you can have either Voukoder or VoukoderPro installed in Vegas Pro 20, but not both.

No.

voukoderproplug.dll appears in Vegas' Component list. Cleared cache and preferences using Ctrl+Shift. No change.

File size of voukoderproplug.dll is 175 KB, is this the expected size and version (0.1.0.0)?

Is there a way to log what's (not) going on?

Yes, voukoderproplug.dll is listed in Components (see screenshot).

Uninstalled and reinstalled Vegas. Flushed the plugin cache with Ctrl+Shift, deleted all preference data.

Still nothing showing in Render As menus.

No joy. No files left in the root folders this time though.

The file size on my voukoderproplug.dll is only 174 KB, while yours is 624 KB.

Zitat von Vouk

Regarding the installer: Can you test if this fixes the issue?

• VoukoderPro is still not available in the Vegas 20 render list. Tried uninstalling, reinstalling, rebooting, etc. Tried with the default installation settings, and also tried the options to install everything.
• VoukoderPro.aex no longer appears in the root folder.
• VoukoderPro.prm still appears in the root folder of a bulk storage drive (drive I:) which has no role in my operating system. There are multiple bulk drives available in the system, but it prefers Drive I:. If I remove drive I: from the system, VoukoderPro.prm instead appears in the root folder of my boot drive C:.

Zitat von Vouk

I've added first VEGAS Pro 20.0 support to 0.7.

Hmmm . . . Voukoder Pro isn't shown in the renderer list (see screenshot). I'm using Vegas Pro 20.0 build 411.

Uninstalled, reinstalled. No change.

Also found VoukoderPro.aex and VoukoderPro.prm files in the root folder of one of my bulk storage drives (I:) which was odd. They were placed there today when I installed VoukoderPro v0.7, judging from the timestamps.

And all audio and video streams in the output test files from Scene Designer are flagged as Swedish. Even when you manually enable the language flag for each stream and set it to English etc.

Test function reports success with this layout. Will see how that translates to the real world when the time comes.

Video and audio streams in output files are by default flagged as.... Swedish??? Even after manually enabling language metadata in each stream node and setting all 4 streams to English.

Not really a bug, more of a question . . . Am I just missing something here?

I've been playing around with the Scene Designer a bit, while waiting for Vegas Pro functionality to arrive. Love the interface. From downloading to having more-or-less what I wanted on the screen took less than 15 minutes. Of course I'm not able to actually test the results yet . . .

One thing I notice is that the scale_cuda video filter doesn't appear in the list of available filters. (scale_cuda is the hardware scaler function on Nvidia graphics cards.) This would be fairly important for my use-case, as I'm trying to have the GPU accept a single video stream, split this into two streams, scale one of them down to 720p resolution, then use NVENC to encode them to different formats (h.264 and h.265).

If this chain has to send a video stream back to the CPU for software scaling, and then back to the card, there will be a huge performance penalty.

You can see my desired scenario below, except the Scale video filter would use scale_cuda and thereby keep all the computation on the graphics card.

PS, wildcard file naming would be helpful, especially in a case like this where both output files will be MP4 file formats with the same name from the NLE. It would be nice to be able to add a suffix to the name from the NLE, for instance "* - Blu-ray version.mp4" and "* - download version.mp4".

Zitat von Jorge Luis

I hate supscription base model

I figured. Stevie says he only uses Vegas, so he probably doesn't know that CS6 was the last non-sub version of Premiere.

Zitat von Steve Rhoden (Hentys)

I am an expert....

Not in other people's affairs, you're not.

Zitat von Steve Rhoden (Hentys)

Trolling, constantly looking for an argument and a fight by jumping into other user's posts that does not concern you.....

Here we have the OP thanking the author for his work. A conversation which in no way involved you. You inserted yourself and your views on how the OP is doing everything wrong.

So, yeah... trolling. Which is what you've been doing to multiple people in multiple forums, such as this one...

If you don't understand why people are doing things a certain way, the intelligent approach would be to learn more about their specific use-case before opening your mouth. If they even want your help, which is unlikely.

If you've got a workflow that works for you, that's great! So does everybody else.

Zitat von Steve Rhoden (Hentys)

"what you should have initially done"

Suddenly you're an expert in everybody else's affairs?

Zitat von Steve Rhoden (Hentys)

What does my response to someone else have to do with you Joe24 ?

I was not talking to you!

I was addressing Jorge Luis on using old software, which of course will ultimately lead to errors and limitations when used in conjunction with newer technology and modern coding.

If he wants to use old software, "ultimately" that's none of your business. I also use Vegas 12 for some things, despite owning 15 and 20. Newer is not necessarily better, and 20 is actually a real PITA for some things. Neither of us owe you an explanation of our rationale for using "old" software. Nor do the other people whom you've attempted to 'convert' in the other forums. Mind your own business.

Zitat von Steve Rhoden (Hentys)

Why on earth are you still using those exceedingly old tools...?

Why would it matter to you what he does with his own property?

Zitat von Jorge Luis

Will it work on after effects cs6? And also premier cs6? How about vegas pro 12?

Somebody hasn't read the thread...

Zitat von Vouk

Joe24 Do you have that error message in the log file again?

No, the error message is not present in the 13.2beta3 logs.

Would a byte-compare of the files rendered by working/non-working versions of Voukoder be useful? The problem might be something at the very beginning of the file, because the clip posted above has zero video-motion throughout. Something breaks immediately at the start of playback, and stays broken.

I've attached 2 files and their logs below. Absolutely nothing is different between the 2 files except the Voukoder version. The 13.0.2 file plays normally, the 13.2beta3 file gives a still picture and plays audio only.

test files.zip

I also tried the 32-bit version of VLC, and a beta version v4.0. No change.