Since the topic is over 1 year old and i was reminded about it because the new OBS beta version has
udated to FFMPEG 4.4.1.
I wanted to ask carefully if their are any news about this feature for Voukoder 
Posts by dream
-
-
Ahh okay.
Are there any plans to bring it back in the future?
-
Hello Vouk,
in the current ffmpeg build (i think it's 4.3.1) we have new presets for "hevc_nvenc" and i think some old ones got renamed.
Some of those presets give you even better quality than slow like the new "p7" preset (but of course they're slower).
Would be nice if you could add them, when you do the next ffmpeg update for voukoder.
ffmpeg -h encoder=hevc_nvenc:
-
Sehr gut! Mit 0.5.1 funktioniert es.
Vielen Dank!
-
Mit der neuen Version, besteht das Problem bei mir nach wie vor.
Code
Display MoreFormat : Matroska Format version : Version 4 File size : 285 MiB Duration : 1 min 0 s Overall bit rate mode : Variable Overall bit rate : 39.6 Mb/s Writing application : Voukoder (VEGAS) Writing library : Lavf58.35.101 ErrorDetectionType : Per level 1 Video ID : 1 Format : AVC Format/Info : Advanced Video Codec Format profile : Baseline@L4.2 Format settings : 1 Ref Frames Format settings, CABAC : No Format settings, Reference frames : 1 frame Codec ID : V_MPEG4/ISO/AVC Duration : 1 min 0 s Width : 1 920 pixels Height : 1 080 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 60.000 FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 8 bits Scan type : Progressive Writing library : x264 core 157 r2981 b5bc5d6 Encoding settings : cabac=0 / ref=1 / deblock=0:0:0 / analyse=0:0 / me=dia / subme=0 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=0 / me_range=16 / chroma_me=1 / trellis=0 / 8x8dct=0 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=0 / threads=24 / lookahead_threads=4 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=0 / weightp=0 / keyint=250 / keyint_min=25 / scenecut=0 / intra_refresh=0 / rc=crf / mbtree=0 / crf=23.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / aq=0 Default : Yes Forced : No Audio ID : 2 Format : FLAC Format/Info : Free Lossless Audio Codec Codec ID : A_FLAC Duration : 1 min 0 s Bit rate mode : Variable Channel(s) : 2 channels Channel layout : L R Sampling rate : 44.1 kHz Bit depth : 16 bits Compression mode : Lossless Default : Yes Forced : No -
Moin,
hast du hier schon mehr untersuchen können.
-
Thank you!
With Voukoder 2.3 my lossless avi files get the correct colors, because i can use this code from ffmpeg in voukoder:
ffmpeg -i "G:\test.mkv" -vf "scale=in_range=pc:out_range=tv" -pix_fmt yuv420p -c:v libx264 -preset ultrafast -crf 21 Output.mkv
Now i get the correct colors in the output with
- .mp4 videos that i record with nvenc (There were always correct, so no need to use a filter)
- Lossless .avi (magicyuv, utvideo) files recored with dxtory, obs etc. when i use the Voukoder filter colorspace.
colorspace filter setting for lossless .avi files recored in limited range:
Output
- Range: Limited
- Matrix: BT.709
- Primaries: BT.709
- Transfer: BT.709
Input:
- Range: Full (The important one)
- Matrix: BT.709
- Prismaries: BT.709
- Transfer: BT.709
Thank you for your excellent work and fast responses.
-
2.3rc1 is working. Thank you!
-
Anbei der Log.
-
Still the same problem in the 2.3beta7
-
Thank you, its working!
-
When using the Scale (Z-Lib) filter the problem still exists, with 2.3beta6 and vegas-connector-0.4.5
-
Ohh can you please try that with lower values like:
-qmin 0 -qmax 16?
-
Instead of adding -b:v 0 a simpler "fix" would be to allow these values to be set to 0, what give me the correct result, when i'm testing in FFMPEG:
FFMPEG Example:
-
Sorry to bother you again, but in order to use qmax and qmin without bitrate limitations, you need the parameter: -b:v 0
You can test that in ffmpeg with the following code:
ffmpeg -i "yourinput" -vcodec h264_nvenc -preset hp -profile:v main -rc:v vbr -b:v 0 -qmin 10 -qmax 16 Out.mkv
If you remove -b:v 0, ffmpeg will always use a constant qc value, but with -b:v 0 set ffmpeg/nvenc can use a lower value (qmin) for scenes that are more complex (more quality).
In ffmpeg you can see the current used value while encoding:
-
Same thing for the Scale (Z-Lib) filter, when i use:
Width
Height
Filter
-
Bei der 2.3b4 werden jetzt zwar die erweiterten Einstellungen bei x264/265 korrekt angezeigt, aber nur die vom letzten Aufruf des Codecdialogs! Wenn man ein zuvor abgespeichertes Preset (bzw. eine "Voreinstellung") lädt, stehen die alten Einstellungen noch im Fenster drin und nicht die des Presets. Das Problem besteht jetzt übrigens auch beim nV-Encoder.
Daß das Laden der Voreinstellungen endlich mal richtig klappt, wäre schon 'ne richtig gute Sache!
Same thing for Vegas Pro 15 with 2.3b5
-
Is VEGAS showing a wrong preview only or does it change the video levels on rendering?
I think my knowledge is way to limited to answer that.
I just wanted to make the point, that every other software i listed handles it like i described, so i thought that should be the norm.
-
This time i recorded with Dxtory but it shouldn't matter, because i used UtVideo YUV420 BT.709 VCM.
Mediainfo from reference (Source):
In the table view i try to demonstrate the problem with Vegas and lossless .avi files (i don't know if something else is also affected)
Notice: These are the NVIDIA Control Panel settings i normally use, for this test i switched between limited and full and show the results in the table:
Reference (.avi UTVideo 4:2:0 BT 709) Software x264 Output
Limited (16-235)
(NVIDIA Control Panel)x264 Output
Full (0-255)
(NVIDIA Control Panel)
Vegas Pro 15 FFMPEG Vegas Pro 15 output
As you can see the output from Vegas Pro 15 is "much" darker when full range is enabled in the NVIDIA Control Panel.
This can be fixed by applying the Vegas Pro 15 filter "levles" > computer RGB to studio RGB.
Then the Image would be bright on limited output, but would look like the source on full.
Vegas Pro settings:
Project settings and Voukoder settings are the same like in my comment about MSI Afterburner.
Voukoder output mediainfo:
FFMPEG and other software
FFMPEG, MeGUI and x264vfw (Each software is able to encode with x264) handles videos like the images show above next to FFMPEG.
On limited range the image is brighter and on full range its like the reference source, when you have a .avi source recorded in bt 709, limited range (like i said i don't know if something else is also affected)
FFMPEG settings:
ffmpeg -i "input" -pix_fmt yuv420p -c:v libx264 -preset medium -crf 21 Output.mkv
FFMPEG mediainfo:
Somehow x264vfw with Vegas can output the video correct, but the process is a bit more complicated to write down, why i choose ffmpeg as an example above...
And again its not a Voukoder problem, but a Vegas Pro problem
-
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.
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.
Like other people said, its a Vegas problem and the only solution at the moment, is to use the Vegas Pro level filter > Computer RGB to Studio RGB.
Thanks for testing all that!
