Beiträge von Vouk

Can you explain this a bit more? What are the steps to reproduce this issue?

Released 2.3beta5

Attention:

This is not compatible with the previous 2.3beta4 Voukoder and connectors. Please uninstall these packages first and then install the 2.3beta5 version.

Fixes:

• Fixed and improved handling with color ranges and color spaces
• Fixed lots of small issues

Changes:

• (h264_nvenc/hevc_nvenc) Added qmin and qmax encoder options

It might also be required to delete all presets / templates from a previous version for it to work properly.

I guessed i'll have that fixed in 2.3beta5 and connector 0.4.0.

Thanks.

CustomAction GetVegasPath returned actual error code 1157

It seems the installer was unable to determine the VEGAS installation directory from the registry.

Please open regedit.exe and take a look if you find entries like these:

ArnoldK Danke für die Info. Ich schaue mal ob ich dahingehend etwas finde.

kevinl203 Can you try these steps with the installer please?

Can you open a command prompt (cmd.exe) and execute the installer like this? (uninstall first)

msiexec /i vegas-connector-0.3.0.msi /L*V install.log

Then please append that install.log file.

Zitat von ArnoldK

weil irgend was mit der DLL nicht stimmt.

Das ist genau das Problem. Ich habe keinerlei Anhaltspunkte das zu untersuchen. "Irgendeine DLL verursacht irgendeinen Fehler". Ich bin auf die Hilfe von Usern (genau: von denen die den Fehler haben) angewiesen mir dort weitere Informationen zu liefern. Mit o.g. Befehl würde mir z.b. der Name der DLL angezeigt werden oder eine Meldung was genau schief läuft damit ich den Fehler beheben kann. Letztendlich möchte ich ja das es für Alle funktioniert.

--

That's exactly the problem. I have no evidence to investigate that. "Some DLL is causing some kind of error". I am dependent on the help of users (exactly: those who have the error) to give me more information there. With the above command I would get the name of the DLL or a message what exactly is wrong so I can fix the error. Finally I want it to work for everyone.

I am in contact with Magix quite frequently and they're very interested in the voukoder plugin. So i'll keep my fingers crossed.

ArnoldK

If it is about being easy and complicated you should wait for the final 2.3 release. A "beta" or a "release candidate" build highly depends on user feedback so I am able to find and fix issues like this one. I am personally not able to test these releases on thousands of different computer configurations by myself.

Can you open a command prompt and execute the installer like this? (uninstall first)

msiexec /i "C:\MyPackage\Example.msi" /L*V "C:\log\example.log"

Then please append that logfile.

It's not a plugin issue. Unfortunately it's a VEGAS issue. Normally they support only one encoder / container per plugin. Voukoder is differently in this point. I hope VEGAS will support changing the file extension by some time.

Done! Added qmin and qmax to h264_nvenc and hevc_nvenc!

Fixed in 2.3beta5

Okay, seems there is another issue with zscale.

It delays the export by 1.4 seconds per frame. That's not really usable.

Yes, its a less obvious for advanced uhd/bt2020 users but also less confusion for yuv 420 hd/rec709. It depends on the use case. I think most users won't ever use colorspace conversion (and if the need it they can use that filter) so in my opinion it is the right way.

Zitat von morphinapg

Might also be a good idea to bring back the x265 settings in this case too.

They will be back! Added them to the config already.

I am thinking about removing these dropdown boxes again and just extend the regular zscale filter (Configure > Filters > Add filter (zscale) ) to support all the color space options. It'd be more consistent, I guess.

That'd mean that there is also no need for the conversion checkbox, nor any mapping of option values. You can just add that filter if you need it.

I'll switch to zscale before any doing any release. As these settings are saved together with a project I'd like to prevent any conflicts like "bt709" vs "709".

Please confirm zscale has all the options you need.

I investivated this with different encoders:

This happens with AAC, AC-3 and DTS. The others work fine.

I am on it.

P.S.: The different offset does not matter! When playing video and audio in a media player it will sync this correctly using the display timestamp (DTS).

P.P.S.: VEGAS and Premiere are not affected.

Theoretically yes, but it does not use FFmpegs standard values i.e. "709" instead of "bt709". Makes it complicated again to map all of these. I'll think about this later.

Fixed taking this value from the project settings.

Fixed in 2.3beta5.