Beiträge von Vouk

Zitat von dream

The problem with that, is when you upload that video to youtube, the video will also look "dark" if a user enables the full range in his browser/device or in the nvidia control panel.

That's not the point at this moment. Let's do a systematic approach and investigate this step by step. Currently we are investigate what goes into VEGAS and what comes out of it. What YouTube is doing with it is a different story (and investigation).

At this point the video levels of the input ("Reference") source and the Output have been always identical. Show me video files where this is not the case and prove me wrong.

Do the steps I did in my previous post, make screenshots and compare them to eachother.

I created two AVI clips with BandiCAM & MagicYUV 2.2:

	Reference	Preview	Export
Limited
Full

It's a bit strange that the "Full" color range now looks strange in the preview but the result looks okay in both cases.

dream I will try to reproduce your exact scenario tommorrow. I still recommend using the "Limited" color range when using YUV. The footroom and headroom is used by some cameras for super-black / super-white. I've read this was a reserve in the good old analogue TV times.

Zitat von Steve Rhoden (Hentys)

That is not the effective solution to what we are trying to resolve here!

Actually we're discussing any possible solution here. I want to fully understand this issue.

Input

I opened "bars.mp4" in MPC-HC, took a still image ("Reference") and here it is:

Preview

I imported it to VEGAS Pro 17, dragged it to the timeline, saved a still image ("Preview") from VEGAS and pasted it here:

What we all notice:

• White is not as bright as the white in the Reference
• Black is not as black as in the Reference
• Gray is brighter than in the Reference

As the Preview is not equal to the Reference I consider it as ...

• ... the colors of the Preview are brighter than the Reference
• ... the VEGAS preview is broken as it does not show the source video correctly

Output

I will now render it with Magix' very own encoder by clicking "File" > "Render as" and selecting format "MAGIX AVC/AAC MP4" and preset "Internet HD 1080p 59,94 fps". I get a new mp4 file, open it with MPC-HC and save a still image ("Output") from it:

Exporting it with Voukoder looks like this:

Conclusions

• Reference is not equal to the Preview => Preview is not okay!
• Output is equal to the Reference => No issue with rendering / exporting!

Whats left is that the preview is not okay:

• ... which has been confirmed by MAGIX
• ... SeMW tools have been developed to fix this

I don't see any other issues. If I did something wrong or miss anything please tell me. Do your own tests with the bars.mp4 file attached to this post and help me to understand this (if I didn't).

But please, from now on: Let's discuss this with facts and measurements only!

P.S.: This has been done entirely in 8-bit mode.

Please try vegas-connector-0.4.2.msi. Fixed a bug in it.

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:

FAQ - Frequently Asked Questions

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.