When using the Scale (Z-Lib) filter the problem still exists, with 2.3beta6 and vegas-connector-0.4.5
Beiträge von dream
-
-
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:
Spoiler anzeigen
ffmpeg -i "<INPUT>" -vcodec h264_nvenc -preset hp -profile:v main -rc:v vbr -b 0 -maxrate 0 -bufsize 0 -qmin 10 -qmax 16 Out.mkv -
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):
Spoiler anzeigen
Code
Alles anzeigenGeneral Complete name : G:\csgo 2019-11-22 14-39-44-832.avi Format : AVI Format/Info : Audio Video Interleave File size : 381 MiB Duration : 4 s 433 ms Overall bit rate : 721 Mb/s Original source form/Distributed by : Video:UtVideo YUV420 BT.709 VCM Writing application : DxtoryCore ver2.0.0.142 Video ID : 0 Format : YUV Codec ID : ULH0 Codec ID/Info : Ut Video Lossless Codec Codec ID/Hint : Ut Video Duration : 4 s 433 ms Bit rate : 721 Mb/s Width : 1 920 pixels Height : 1 080 pixels Display aspect ratio : 16:9 Frame rate : 60.000 FPS Color space : YUV Chroma subsampling : 4:2:0 Compression mode : Lossless Bits/(Pixel*Frame) : 5.797 Stream size : 381 MiB (100%)
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:
Spoiler anzeigen
Code
Alles anzeigenGeneral Complete name : H:\vegas.mkv Format : Matroska Format version : Version 4 File size : 1.89 MiB Duration : 4 s 455 ms Overall bit rate : 3 554 kb/s Writing application : Voukoder (VEGAS) Writing library : Lavf58.35.100 ErrorDetectionType : Per level 1 Video ID : 1 Format : AVC Format/Info : Advanced Video Codec Format profile : High@L4.2 Format settings : CABAC / 4 Ref Frames Format settings, CABAC : Yes Format settings, Reference frames : 4 frames Codec ID : V_MPEG4/ISO/AVC Duration : 4 s 455 ms 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 Encoding settings : cabac=1 / ref=3 / deblock=1:0:0 / analyse=0x3:0x113 / me=hex / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=24 / lookahead_threads=4 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=crf / mbtree=1 / crf=20.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00 Default : Yes Forced : No Audio ID : 2 Format : AAC LC Format/Info : Advanced Audio Codec Low Complexity Codec ID : A_AAC-2 Duration : 4 s 437 ms Channel(s) : 2 channels Channel layout : L R Sampling rate : 48.0 kHz Frame rate : 46.875 FPS (1024 SPF) Compression mode : Lossy Default : Yes Forced : No
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:
Spoiler anzeigen
Code
Alles anzeigenGeneral Complete name : H:\ffmpeg.mkv Format : Matroska Format version : Version 4 File size : 1.52 MiB Duration : 4 s 434 ms Overall bit rate : 2 875 kb/s Writing application : Lavf58.29.100 Writing library : Lavf58.29.100 ISRC : Video:UtVideo YUV420 BT.709 VCM ErrorDetectionType : Per level 1 Video ID : 1 Format : AVC Format/Info : Advanced Video Codec Format profile : High@L4.2 Format settings : CABAC / 4 Ref Frames Format settings, CABAC : Yes Format settings, Reference frames : 4 frames Codec ID : V_MPEG4/ISO/AVC Duration : 4 s 434 ms Bit rate : 2 818 kb/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 Bits/(Pixel*Frame) : 0.023 Stream size : 1.49 MiB (98%) Writing library : x264 core 158 r2984 3759fcb Encoding settings : cabac=1 / ref=3 / deblock=1:0:0 / analyse=0x3:0x113 / me=hex / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=24 / lookahead_threads=4 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=crf / mbtree=1 / crf=21.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00 Default : Yes Forced : No
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!
-
Okay with the bars.mp4 i get the correct output.
When the source is from UTVideo or MagicYUV (.avi lossless formats) i get the dark output.
I tried to record with Dxtory, MSI Afterburner and OBS Studio (OBS uses the FFMPEG Version of UTVideo).
Steps to reproduce with MSI Afterburner:
Software
Install utvideo-20.3.0 (Newer Versions have problems with dxtory, vegas and afterburner)
Install MSI Afterburner with Rivatuner Statistic Server
Afterburner
Open MSI Afterburner Settings > Video Recording (Videoaufnahme)
Screenshot with the settings: https://i.imgur.com/tnMpFPC.png
I also tried different colors for UTVideo like: 4:2:0, 4:2:2 and RGB
Rivatuner
In Rivatuner Statistic Server i make sure, that the
- Global Profile Application detection level is set to low
- On-Screen Display support: On
- On-Screen Display coordinate space: Framebuffer
Setup/Settings in Rivatuner:
Use dedicated encoder service > 64 Bit
Record a random Game
Vegas Pro:
...Import the video
Project settings
I use Vegas Pro 15 with these project settings: https://i.imgur.com/zvPzk3f.png
Render as
For example Voukoder with H.264 (x264):
crf=20.0 preset=medium profile=high rc=crf
EDIT:
Also make sure to use the full dynamic range for videos in the NVIDIA control panel video tab > Adjust video color settings > With the NVIDIA settings > Advanced > Dynamic range : Full (0-255)
-
So i tested some thing with FFMPEG and with this parameter i get the correct colors:
Codeffmpeg -i "G:\test.mkv" -vf "scale=in_range=pc:out_range=tv" -pix_fmt yuv420p -c:v libx264 -preset ultrafast -crf 21 Output.mkv
But this is only for a already encoded video with Vegas, because Vegas somehow set the pc range flag?
So the solution is to tell the encoder that the input is in pc range if i understand the filter correct:
-vf "scale=in_range=pc:out_range=tv"
When i try to encode directly from the source file (No encoded Video from Vegas) i need to the the filter to:
-vf "scale=in_range=tv:out_range=tv" (It depends on the source file).
I don't know if this is possible to implement and if this is even the correct fix for this problem.
-
Exactly but its also the output/encoded video.
-
-
Ok the output is still dark like the screenshots above, when using the new color space filter with:
--range tv --colorprim bt709 --transfer bt709 --colormatrix bt709
It seems like its a vegas problem, like steve said, because the only "encoder" who isnt that dark is x264vfw, but i don't know why.
My knowledge is way to limited, but i know that vegas is converting all video inputs to rbg ... maybe thats a problem?
This describes the problem exactly: https://forums.creativecow.net/docs/forums/po…=983265&pview=t
So i think i need to apply the "levels" filter everytime
-
-
I also cannot open the settings.
- Uinstalled the connector and core
- Then installed both of the newest version
- Deleted all presets
This is the button (Grayed out)
https://i.imgur.com/Y67D3OQ.png
EDIT: I could fix this issue, with installing vegas pro 17 testversion > installing voukoder there > succesfully opening the dialoug > now i can open the presets in vegas pro 15 again
-
Would it also be possible to include a filter for tv range/pc range?
-
Quick comparison in vegas pro 15.
x264vfw with these additional commands (Extra command line):
--range tv --colorprim bt709 --transfer bt709 --colormatrix bt709
[Blockierte Grafik: https://i.imgur.com/Emajbfu.png]
Voukoder with just x264:
-
I now also notice the much darker colors for the output-
Before Voukouder i used x264vfw with these additional commands (Extra command line):
--range tv --colorprim bt709 --transfer bt709 --colormatrix bt709
With these commands i get proper colors/brightness (I think --range tv is the important one?)
When i use the Vegas Pro effect levels preset: "Computer-RGB to Studio-RGB", the colors looks correct with voukouder (slightly different when i compare it directly to the x264vfw output).
-
This is often a problem, when the "Pixel format" in the project settings is not set to "8-Bit"