My mistake. It does not expand it, it just displays it.
What I meant: the preview just displays what is in the framebuffer.
If you load a limited frame into it where 0x10 is supposed to be black it will display it as dark grey. The preview simply ignores any color range setting.
In the projects "Pixel format" setting dropdown box there should be actually:
8 bit (Full)
8 bit (Limited)
@MajorBubble
Right, most YUV 8 bit content is supposed to be limited. The internal preview expands it to full (black = 0x101010, white = 0xebebeb) and that's what it makes look brighter.
People apply a brightness correction to make it look like the original again, render it and the external player shows it darker - Which is correct.
And I even know the technical reason for this issue: The preview is a direct pointer to the uncompressed framebuffer. (I once vertically flipped the framebuffer and the preview flipped too).
Still this is a very, very bad design as most 8 bit video is actually limited.
I tend to agree. But to me it looks like the preview is actually too bright.
If i compare the source video and the exported file brightness/contrast/gamma look identical to me. But the preview just looks to bright.
Is this related to the selected color range (i.e. bt601, bt709, ...?)
Currently the voukoder connector only works with bt709.
If it is not related to that i could add a brightness/contrast/gamma filter from FFmpeg to it to correct this.
Ich habe das eben ausprobiert. Bei mir treten keine solche Phänomene auf. Insbesondere ist es seltsam das bei einer fertig gerenderten Datei mal Ton kommt und mal nicht. Bisland hat sich auch noch niemand mit einem ähnlichen problem gemeldet.
Da ich es selber nicht reproduzieren ist es schwer nach einer Ursache für dein Problem zu suchen.
Hänge bitte mal die zugehörige Voukoder Log Datei hier an.
Nutzt du beta2 oder beta3? Funktionierts mit dem jeweils anderen?
Released 2.3beta3
Fixes:
It depends entirely on your setting (which you didn't tell us). Please provide the voukoder log file.
I compared the project files and made them almost identical. But that did not fix it.
In theory we do not need to think about v2 here. The first goal is to make VRPT as fast as v1.1.3 (or find out was has changed).
Wird alles in der nächsten Betaversion behoben sein.
Wird auch recht zeitnah kommen (ich schätze Sonntag).
That'd mean that both versions have a different vRender value (That's what I assume). And the big question is: Why?
A bug ：First open dialog it will show "ui.encoderconfig.true" rather than "Yes".
This is fixed in the next version.
There are many users reporting this. But I never found out why it is like that.
When i use my test project (2048x1152 / h264_nvenc / default) version 2.3b2 is even faster than 1.1.3.
All I know it has to do with the time premiere needs to render the raw frame (vRender). Did you try the VRPT tool on the project? Does that finish faster or slower than 1.1.3?
It also depends on your encoder. What encoder are you using? Not all encoders can encode interlaced.
Vegas says "filename.mp4", but voukoder will still output a "filename.mkv" file. Unfortunately Vegas can currently only handle one file extension per plugin.
Vorbis issues are fixed too.
It is using the project settings so far. It should work if you change the projects settings.
1. FLAC issue is fixed in the next version of voukoder core.
2.1. Can't reproduce this, works fine for me. Please tell me detailed steps on how to reproduce it.
2.2. Can reproduce this with vorbis.
Click in the File menu the entry Render as:
Voukoder should appear in the list of output formats:
You can configure the Voukoder settings by clicking on Customize Template ... and then click on on Open Voukoder dialog ...
You can store the this settings as a new template of course.
