Beiträge von Vouk

Can you post a voukoder log file? Then we can take a look at it.

What "bitrate=0" does is that it actually says "bitrate can be unlimited", which is what you want. This basically simulates a dynamic quantizer like CRF with x264.

So, yes i'll change it to allow bitrate=0.

Can't confirm.

If i run this ...

ffmpeg -i "z:\overvouk\2016-11-02-Dead by Daylight #001.mp4" -vcodec h264_nvenc -preset hp -profile:v main -rc:v vbr -qmin 0 -qmax 50 Out.mkv

... the quantizer value is frequently changing. Maybe the range between qmin and qmax in your case is just too small.

Gefunden und behoben. Benötigt allerdings für einen vollständigen Fix ein Update beider Komponenten.

• VEGAS Connector 0.4.5
  Erkennt nun den ausgewählten / gewechselten Preset und lädt diesen auch.
• Voukoder 2.3beta6
  Behebt einen Fehler das Optionen teilweise vom vorherigen ausgewähltem Preset übernommen werden.

can you start regedit.exe and make a screenshot of this key with all its entries first, please?

HKEY_LocalMachine\Software\Adobe\Premiere Pro\

Really strange. I have the impression that it is somehow related to your specific windows configuration.

Is it possible your user is a special restricted user? Maybe limited by various rules defined by a domain policy? Or in a citrix environment or similar?

I will add filters on demand. Please name the filters you need.

1. The connector should let you choose the installation directory. The default value will be taken from the registry:

C:\Program Files\Adobe\Common\Plug-ins\7.0\MediaCore

2. Please make sure you have at least NVIDIA driver 418.81 installed

3. What happens if you use x264 with default options?

Das ist derzeit noch Baustelle die mir noch Kopfschmerzen bereitet. Ich fordere aktuell einen I420 Framebuffer an, bekomme aber keinerlei informationen über Farbraum und Pegel.

Der Workaround geht von Begrenzt/709 aus und das führt natürlich zu Problemen wenn es anderes ist.

Die Farbraum Filter konvertiert meines Wissens nach immer (spreizt/komprimiert). Sollte ich die Informationen von VEGAS korrekt bekommen müsstest du meinem Verständnis nach auch keinen Filter nutzen.

Der bekannte Frameserver macht es sich da einfacher. Er holt sich alles als RGB und rechnet es sich es dann in YUV ... um so wie er es gerade braucht. Diese Konvertierung will ich mir aber eigentlich sparen.

Well, the questions we're discussing here is:

Is VEGAS showing a wrong preview only or does it change the video levels on rendering?

I don't think any NVIDIA settings is interfering with the calculations VEGAS is doing during rendering, does it?

btw. I don't have the NVIDIA control panel installed and I never use that switch. So if you leave it on the default setting, would you have any issues at all?

And please leave out all encoding and post processing. This is just about vegas.

Do you use the "color space" filter? There is a known issue that you have to set all options of one group (i.e. output), not just a single one.

Unfortunately the installer is currently not capable of doing that.

But there is a manual workaround. Copy these file / folders from VEGAS 17 to their VEGAS 15 and 16 equivalent:

• VEGAS Pro 17.0\Voukoder-x64.fio2007-config
• VEGAS Pro 17.0\FileIO Plug-Ins\voukoderplug\voukoderplug.dll

I created a new set of installers that should include this package now. It should be automatically installed now.

OldSpice Really? You get pissed already when not getting an instant answer to a question that is completely offtopic here while I am already working on something else?

Great! Now i just need to include this in each installer somehow.

Alright, it's getting clearer now.

Does installing the runtime libs help?

https://aka.ms/vs/16/release/vc_redist.x64.exe

(with the original 0.4.2 file)

@MajorBubble If 0.4.2 is installed and you replace voukoderplug.dll with the one from this zip file, does that work?

1. Uninstall the Voukoder connector for VEGAS
   1. These files / directories should not be present anymore
      1. C:\Program Files\VEGAS\VEGAS Pro 17.0\FileIO Plug-Ins\voukoderplug\voukoderplug.dll
      2. C:\Program Files\VEGAS\VEGAS Pro 17.0\Voukoder-x64.fio2007-config
2. Uninstall the Voukoder (Core) component
   1. There shouldn't be a C:\Program Files\Voukoder directory anymore
   2. Open regedit.exe and confirm this entry is not present anymore
      1. Computer\HKEY_CLASSES_ROOT\CLSID\{E9661BFA-4B8E-4217-BCD8-24074D75000B}
3. Reboot your machine (Just to be sure)
4. Install VEGAS Connector 0.4.2
   1. Confirm it is installed in "Apps & Features":
      
   2. These files / directories should now be present
      1. C:\Program Files\VEGAS\VEGAS Pro 17.0\FileIO Plug-Ins\voukoderplug\voukoderplug.dll
      2. C:\Program Files\VEGAS\VEGAS Pro 17.0\Voukoder-x64.fio2007-config
      3. Confirm the version number is indeed 0.4.2.0
         
5. Don't install voukoder core, just start VEGAS
   1. You should see this error:
      
   2. Click OK three times
   3. Voukoder should be listed in the About dialog:
      

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.