Beiträge von Vouk

In theory this should be possible. I'll think about it and put it on my todo list.

That'd be great and I'd put it in the documentation.

Voukoder 4.1 is not supported anymore, but ...

[19:13:25] Interlaced:      Top first

This is not supported with the NVIDIA GeForce GTX 1650 GPU.

Check your logfile. The ZIP file is empty.

I'm currently on a business trip and will investigate this when I'm back at home on the weekend .

Yes. Please see the latest news.

VEGAS Pro 23 will be supported with the Voukoder Pro 3 version.

I will drop a beta version most likely at October 1st.

Note: It is important to check the "Show all formats" checkbox to see the Voukoder Pro plugin.

Thanks for your investigation. I'll look into it.

Maybe you can try to flush the plugin cache on a test-machine (Hold CTRL+Shift on VEGAS Pro startup)? Does that help?

I don't think the issue is normal as many Voukoder Pro users are using VEGAS Pro.

Okay, I just found out this isn't mentioned anywhere, but these variables are available ...

$(FilePath)
$(FileName)
$(FileExtension)
$(FileFullname)

So this should work:

youtubeuploader -filename $(FileFullname)

Putting it on my list ...

Zitat von deco

The full/full-shared builds contain everything possible; I didn't really look at the essentials builds, because I want everything :)

What do you mean with full/full-shared and essentials builds?

Zitat von deco

I'm sure you have lots of concerns about licensing (and patents), so something like this moves that to a 3rd party. But, I'm not a programmer :)

I actually have no concerns about licensing issues anymore as FFmpeg is not included in GPL in Voukoder Pro anymore, but yes, building FFmpeg takes hours and can be VERY complicated if you want to embed all libraries and features. That's why I already switched to the BtbN builds. But scoop makes it even easier.

I just wish to make Voukoder Pro and FFmpeg even more user friendly for the user, like maybe install it via the Designer app. Maybe I can work on this in 2026 and check the legal aspects first.

Zitat von deco

I also really like the system of "zero"-installs, where everything is contained in one directory, Windows is not involved, and it just makes shims as necessary. Delete that directory if you don't like it, and it's gone!

Same. In theory I don't even need the path variable anymore. But the shims are currently working for EXE files only, not for DLLs.

It's really interesting VEGAS Pro is one of the few tools where older version are still in use by many people. But we can try to support as many older versions that are supported by the oldest VEGAS Pro SDK I have access to.

I'm just busy with Voukoder Pro 3 at the moment. I'll put it on my todo list.

Voukoder never included a download link for VEGAS Pro. My first version of VEGAS Pro was 17 which SDK should be compatible down to VEGAS Pro 12, but i was never able to test it.

Voukoder Pro supports VEGAS Pro 18-23 now.

I've looked into this, and yes, it looks very promising! In fact this finally makes installing ffmpeg easy (like homebrew on MacOS).

I need to look deeper into it and check what's bundled into this ffmpeg version.

Edit:

So yes, scoop is indeed a good option, you can install FFmpeg really easy with it, like:

1. Install scoop itself:
   Open a powershell.exe console and enter:
   Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
   Invoke-RestMethod -Uri https://get.scoop.sh | Invoke-Expression
   
2. Install ffmpeg (for Voukoder Pro 3.0)
   1. scoop install main/ffmpeg-shared@8.0
      
3. Add the directory with the installed ffmpeg dlls to the PATH variable
   

Apparently no single log is created.

• Please open the Designer App on your Desktop.
• Open the scene you want to use in After Effects
• Run the Scene Test with like 10 iterations.
• Copy the generated log file here.

Reproduce this steps, please:

1. Reproduce the issue
2. Open "%LOCALAPPDATA%VoukoderPro\logs" in the windows explorer
3. Copy & paste the latest logfile here

Yes, if you want to get a certain video size it's a good reason. I'll put it on my list.

Technically it's possible, but i didn't implement it yet as it slows down the overall encoding process and there are much better rate control algorithms available (i.e. CFR). What do you need it for?

The scene graph looks weird when recreating your settings. I'll investigate this ...

Can you perform a scene test and share the log output here?