Nevermind. It's always a bit difficult to explain this as I can't see your screen. But in the end we got it fixed and improved voukoder a little bit more.
Beiträge von Vouk
-
-
Yes, I can confirm I found that one.
I just need to find a clever way to fix it.Edit: Fixed in the next release.
-
nikossnyder Are you talking about parallel or sequential encoding with Media Encoder to multiple files with multiple resolutions?
Edit: I guess I've found the issue.
-
Voukoder does not use the Sequence resolution. It uses the resolution from the export dialog. It should work if the sequence resolution matches the export resolution.
-
I am not really sure what you are trying to do.
Voukoder never automatically added crop filters. It takes the video from premiere as seen in the preview with the dimensions in the video tab of the export dialog. If you are adding video filters manually changing the width/height this new value will be taken instead.
-
Please add a logfile first, so i can see the full export process.
-
Dahingehend habe ich nichts implementiert.
-
Die Sidedata Werte sind meines Wissens nach nur reine Informationen bzgl. der Wiedergabe. Sie haben keine Auswirkung auf die Kodierung.
-
-
Not (yet) part of this project.
-
-
-
This is fixed in Connector 1.1.1
-
Done. It will try to autodetect the latest installed Elements version IF Pro is not installed.
Available in Premiere Connector 1.1.1
-
Alright. I'll take a look at it tomorrow.
-
I could also extend the auto detection for the plugin path. But I don't know the registry key where Elements plugin path is stored.
-
It has been added already (Just as 48 and 72 fps). Just use the latest connector for premiere.
-
But why don't you just select the Elements plugin directory in the installer?
-
Das sollte mit VirtualDub2-x64-2020-01-26_00.zip jetzt behoben sein.
-
Benutzt du die aktuelle Version des VEGAS Connectors?