Beiträge von Noki

Hi,

I noticed that the scene list order in the Vegas preset dialogue differs from the scene list order of the Designer Open Scene dialogue. This seems to be the cause of this issue.

An example:
if index #0 in the preset dialogue is "Test1", "Test1" is stored as the selected scene, but when you re-open the dialogue, it does not show "Test1". It shows "Test2", because index #0 in the Designer Open scene dialogue is "Test2".

So, in my tests the selected/stored and recalled scene names only match in the plugin preset dialogue, if for a specific index number both list entry names also match.

I attached a scenes.json file with this problem. Maybe you can reproduce this effect?

Thanks,
Nils

Hi,

I tried the Vegas cache flush and complete settings reset but to no avail.

What's interesting: The .SFT2 plugin-preset file itself seems to be written correctly. If I open it in a text editor, it shows the correct scene name, although the settings windows in Vegas/Voukoder gives the wrong name.

Any further ideas? Thanks!

Nils

EDIT: Not only the .SFT2 file is written correcly, Voukoder also actually uses the right scene file for rendering. So, it looks like a dialog display issue.

A workaround might me to integrate the scene name into the plugin preset name to be aware of which scene is in use.

Hi,

I cannot get the right scene stored with a Voukoder Pro (2.0.14) render preset (see also screen recording attached):

1. I select a predefined preset like "YUV 4:2:0, 8 bit"
2. select the scene I want to use from the scene list
3. rename "YUV 4:2:0, 8 bit" to something different and save the render preset
4. when I reopen this preset, a different scene is selected for this preset
5. when I correct the scene and save again, the scene does not change

Is there something I''m doing wrong?

Additionally, after adding scenes by using the Voukoder Pro Designer, even already existing presets change their scenes. I'm using Vegas Pro V22 B250 (german), but there's the same behaviour in earlier versions of Vegas and Voukoder Pro. I also noticed the same problem on a second system (both Win11 24H2 geman).

Running Vegas with elevated privileges also makes no difference.

So, I'm really puzzled what's going on here

Thanks for some help!

Nils

The frameserver seems to work, as rendering starts even with activated PCM audio. Though, the button "Vorlage anpassen" (edit preset) cannot be clicked (Normal state for this plugin?). In opposite to Voukoder now there is a "Project Default" preset like in Voukoder in Vegas Pro.

Thanks,

Nils

If it helps I could give you my P3 activation code, so you can temporarily use it to get Voukoder up and running in Movie Studio

Nils

You can download a preset from here:

https://www.dropbox.com/s/gmc6bd8d5kn4vyn/default.sft2?dl=1

It's a binary file (.sft2), so hard to see what's actually stored in it.

Nils

This is what it looks like when I try to save a preset with audio activated:

Without "include audio" activated a preset is stored and rendering starts.

BTW, as you can see, there is no default "(Use project settings)" preset in the list like in Vegas Pro.

Thanks,

Nils

It obviously has something to do with audio:

Render with "include audio" activated in Voukoder:

Rendering does not start and a new preset is automatically deactivated by Movie Studio (...preset is not valid...)

Render with "include audio" DEactivated in Voukoder

Renderering works and a new preset can be stored

Any Ideas?

Thanks,

Nils

Also tried connector 0.6.1 with Voukoder 3 now, but it does not start to render either. Also no log file created.

Vegas Pro 15 does work in any case.

Anybody successfully running Voucoder under Movie Studio 16?

Thanks

Nils

I noticed that for Movie Studio with connector 0.70 Voukoder only shows up in the list if there is a valid preset stored under "C:\Users\%username%\AppData\Roaming\VEGAS\Render Templates\voukoder\" already. No preset, no voukoder.

Nils

Hi,

when I select Voukoder for rendering (basic preset) and click render nothing happens (mouse pointer is the busy ring). Clicking on cancel stops the busy ring and closes the render window.

This happens on two different systems with Voukoder 4.1, one with connector 0.70 (Vegas Pro 15 is working well with Voukoder here), and one with connector 0.61 (Voukoder does not show up in the list with connector 0.70).

Any Ideas?

Thanks,

Nils

I had right the same problem today on one system with Movie Studio 16 P. With connector 0.70 no way, but 0.61 made voukoder visible in the render target list. It did not render though, but this seems to be a Movie Studio specific issue as Vegas Pro ist working.

Maybe you should give 0.61 a try?

Nils