Please try vegas-connector-0.4.2.msi. Fixed a bug in it.
Beiträge von Vouk
-
-
I did not want to add anything to this discussion anymore but It's itching me pretty hard right now:
This is the original document I once sent to Magix explaining them the preview is broken (in most cases). This behaviour has been confirmend by Magix.
-
I guess, if you start vegas-connector-0.4.1.msi again and click "Repair" everything is working?
-
And what if you also install voukoder-2.3beta5_fixed.msi ?
-
The was an issue with the installers that they did not necessarily overwrite existing and older files. These installers have been updated now. You might download the new version if you experienced issues.
-
Please try connector 0.4.1. I guess i fixed a nasty issue with the installer.
-
Did you uninstall any older Voukoder and/or Connector first?
-
Please set the options just like in the FAQ with the exact same values.
(Don't set a level at all)
-
Please retest with Connector 0.4 and Voukoder 2.3beta5.
-
You should set a proper encoding strategy.
Take a look at section 1 here:
-
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.
-
-
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.
-
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.
-
-
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.
-