Sony FDR-AX700 and Colour Space of Sony's XAV-S Videos

MH7 wrote on 2/1/2023, 10:35 PM

Okay, I have the following video camera mentioned and I've noticed, when I use MediaInfo to look at and analyze one of the videos filmed with this camera of mine, that it says that the colour space is YUV. Although, now looking at it looks like the colour space is BT709, which I guess is Rec.709 (from the quick search I did just now when searching for BT.709). So, given this, how should I go about setting the correct settings for this video inside VEGAS Pro 18?

All required additional info is in my signature below.

General
CompleteName                     : D:\Videos\Sony AX700 4K Videos\C0003.MP4
Format/String                    : XAVC
CodecID/String                   : XAVC (XAVC/mp42/iso2)
FileSize/String                  : 13.6 GiB
Duration/String                  : 19 min 55 s
OverallBitRate_Mode/String       : Variable
OverallBitRate/String            : 97.6 Mb/s
Encoded_Date                     : UTC 2019-08-07 07:16:50
Tagged_Date                      : UTC 2019-08-07 07:16:50

Video
ID/String                        : 1
Format/String                    : AVC
Format/Info                      : Advanced Video Codec
Format_Profile                   : High@L5.1
Format_Settings                  : CABAC / 2 Ref Frames
Format_Settings_CABAC/String     : Yes
Format_Settings_RefFrames/String : 2 frames
CodecID                          : avc1
CodecID/Info                     : Advanced Video Coding
Duration/String                  : 19 min 55 s
BitRate_Mode/String              : Variable
BitRate/String                   : 95.9 Mb/s
BitRate_Maximum/String           : 100.0 Mb/s
Width/String                     : 3 840 pixels
Height/String                    : 2 160 pixels
DisplayAspectRatio/String        : 16:9
FrameRate_Mode/String            : Constant
FrameRate/String                 : 25.000 FPS
ColorSpace                       : YUV
ChromaSubsampling/String         : 4:2:0
BitDepth/String                  : 8 bits
ScanType/String                  : Progressive
Bits-(Pixel*Frame)               : 0.462
StreamSize/String                : 13.3 GiB (98%)
Encoded_Date                     : UTC 2019-08-07 07:16:50
Tagged_Date                      : UTC 2019-08-07 07:16:50
colour_range                     : Limited
colour_primaries                 : BT.709
transfer_characteristics         : xvYCC
matrix_coefficients              : BT.709
Metas                            : 4
CodecConfigurationBox            : avcC

Audio
ID/String                        : 2
Format/String                    : PCM
Format_Settings                  : Big / Signed
CodecID                          : twos
Duration/String                  : 19 min 55 s
BitRate_Mode/String              : Constant
BitRate/String                   : 1 536 kb/s
Channel(s)/String                : 2 channels
SamplingRate/String              : 48.0 kHz
BitDepth/String                  : 16 bits
StreamSize/String                : 219 MiB (2%)
Encoded_Date                     : UTC 2019-08-07 07:16:50
Tagged_Date                      : UTC 2019-08-07 07:16:50

Other
ID/String                        : 3
Type                             : Time code
Format/String                    : QuickTime TC
Duration/String                  : 19 min 55 s
FrameRate/String                 : 25.000 FPS
TimeCode_FirstFrame              : 00:19:16:08
TimeCode_LastFrame               : 00:39:11:24
TimeCode_Stripped/String         : Yes
Encoded_Date                     : UTC 2019-08-07 07:16:50
Tagged_Date                      : UTC 2019-08-07 07:16:50

Last changed by MH7

John 14:6 | Romans 10:9-10, 13, 10:17 | Ephesians 2:8-9
————————————————————————————————————

Aussie VEGAS Post 20 User as of 9th February 2023 — Build 411 (Upgraded from VEGAS Pro 18)

VEGAS Pro Help: VEGAS Pro FAQs and TROUBLESHOOTING GUIDES

My YouTube Channel: https://www.youtube.com/@TechWiredGeek

Video Cameras: Sony FDR-AX700 and iPhone 12 Pro Max (iOS 17)

============================================

My New Productivity Workstation/Gaming PC 2024

CPU: AMD R7 7800X3D

Motherboard: ASRock X670E Steel Legend (AM5)

RAM: Corsair Vengeance 32 GB (2 x 16 GB) DDR5-6000 CL30 Memory

Main SSD: Samsung 980 Pro 1 TB SSD
Storage SSD: Western Digital Black SN850X 2 TB SSD

GPU: Asus TUF GAMING OC Radeon RX 7800 XT (16 GB)

OS: Windows 11 (Build: 23H2)

Main Monitor: LG 27UD88-W 4K IPS

Secondary Monitor: LG 27UL850 4K HDR IPS

Comments

RogerS wrote on 2/1/2023, 11:07 PM

What project properties are set? If you're in 8 bit mode it is Rec709 so you're good to go. Most video is YUV.

Yelandkeil wrote on 2/1/2023, 11:18 PM

 

Video Colorspaces and Vegaspro-ACES

-- Hard&Software for 5.1RealHDR10 --

ASUS TUF Gaming B550plus BIOS3202: 
*Thermaltake TOUGHPOWER GF1 850W 
*ADATA XPG GAMMIX S11PRO; 512GB/sys, 2TB/data 
*G.SKILL F4-3200C16Q-64GFX 
*AMD Ryzen9 5950x + LiquidFreezer II-240 
*XFX Speedster-MERC319-RX6900XT <-AdrenalinEdition 24.12.1
Windows11Pro: 24H2-26100.3915; Direct3D: 9.17.11.0272

Samsung 2xLU28R55 HDR10 (300CD/m², 1499Nits/peak) ->2xDPort
ROCCAT Kave 5.1Headset/Mic ->Analog (AAFOptimusPack 6.0.9403.1)
LG DSP7 Surround 5.1Soundbar ->TOSLINK

DC-GH6/H-FS12060E_HLG4k120p: WB=manual, Shutter=125, ISO=auto/manual
HERO5_ProtuneFlat2.7k60pLinear: WB=4800K, Shutter=auto, ISO=800

VEGASPro22 + XMediaRecode/Handbrake + DVDArchi7 
AcidPro10 + SoundForgePro14.0.065 + SpectraLayersPro7 
K-LitecodecPack17.8.0 (MPC Video Renderer for HDR10-Videoplayback on PC) 

MH7 wrote on 2/1/2023, 11:27 PM

What project properties are set? If you're in 8 bit mode it is Rec709 so you're good to go.

Yes, I was using 8-bit full range.

Most video is YUV.

Really? I didn't know that. Thank you.

Something else I've noticed though, if I right click on the video inside VEGAS Pro 18, select the Rec.709 colour space, it then has an option to select 'Undefined', 'Limited, or 'Full'. But then the video looks a tad washed out like it's on the Legacy 8-Bit pixel format setting, yet it looks like some lights in the video are little less blown out, like a little more detail is retained. That's the best way that I can explain it, as it is in the Legacy 8-Bit pixel format setting.

.

Last changed by MH7 on 2/1/2023, 11:34 PM, changed a total of 1 times.

John 14:6 | Romans 10:9-10, 13, 10:17 | Ephesians 2:8-9
————————————————————————————————————

Aussie VEGAS Post 20 User as of 9th February 2023 — Build 411 (Upgraded from VEGAS Pro 18)

VEGAS Pro Help: VEGAS Pro FAQs and TROUBLESHOOTING GUIDES

My YouTube Channel: https://www.youtube.com/@TechWiredGeek

Video Cameras: Sony FDR-AX700 and iPhone 12 Pro Max (iOS 17)

============================================

My New Productivity Workstation/Gaming PC 2024

CPU: AMD R7 7800X3D

Motherboard: ASRock X670E Steel Legend (AM5)

RAM: Corsair Vengeance 32 GB (2 x 16 GB) DDR5-6000 CL30 Memory

Main SSD: Samsung 980 Pro 1 TB SSD
Storage SSD: Western Digital Black SN850X 2 TB SSD

GPU: Asus TUF GAMING OC Radeon RX 7800 XT (16 GB)

OS: Windows 11 (Build: 23H2)

Main Monitor: LG 27UD88-W 4K IPS

Secondary Monitor: LG 27UL850 4K HDR IPS

john_dennis wrote on 2/1/2023, 11:38 PM

@MH7 said: "... if I right click on the video inside VEGAS Pro 18, select the Rec.709 colour space, it then has an option to select 'Undefined', 'Limited, or 'Full'."

From the Mediainfo report for your video.

colour_range                     : Limited

MH7 wrote on 2/2/2023, 12:02 AM

@MH7 said: "... if I right click on the video inside VEGAS Pro 18, select the Rec.709 colour space, it then has an option to select 'Undefined', 'Limited, or 'Full'."

From the Mediainfo report for your video.

colour_range                     : Limited

Thanks mate! The answer was in my own post. 😁 LOL

John 14:6 | Romans 10:9-10, 13, 10:17 | Ephesians 2:8-9
————————————————————————————————————

Aussie VEGAS Post 20 User as of 9th February 2023 — Build 411 (Upgraded from VEGAS Pro 18)

VEGAS Pro Help: VEGAS Pro FAQs and TROUBLESHOOTING GUIDES

My YouTube Channel: https://www.youtube.com/@TechWiredGeek

Video Cameras: Sony FDR-AX700 and iPhone 12 Pro Max (iOS 17)

============================================

My New Productivity Workstation/Gaming PC 2024

CPU: AMD R7 7800X3D

Motherboard: ASRock X670E Steel Legend (AM5)

RAM: Corsair Vengeance 32 GB (2 x 16 GB) DDR5-6000 CL30 Memory

Main SSD: Samsung 980 Pro 1 TB SSD
Storage SSD: Western Digital Black SN850X 2 TB SSD

GPU: Asus TUF GAMING OC Radeon RX 7800 XT (16 GB)

OS: Windows 11 (Build: 23H2)

Main Monitor: LG 27UD88-W 4K IPS

Secondary Monitor: LG 27UL850 4K HDR IPS

MH7 wrote on 2/2/2023, 12:05 AM

Out of curiosity, how accurate is MediaInfo in displaying the correct info of videos?

John 14:6 | Romans 10:9-10, 13, 10:17 | Ephesians 2:8-9
————————————————————————————————————

Aussie VEGAS Post 20 User as of 9th February 2023 — Build 411 (Upgraded from VEGAS Pro 18)

VEGAS Pro Help: VEGAS Pro FAQs and TROUBLESHOOTING GUIDES

My YouTube Channel: https://www.youtube.com/@TechWiredGeek

Video Cameras: Sony FDR-AX700 and iPhone 12 Pro Max (iOS 17)

============================================

My New Productivity Workstation/Gaming PC 2024

CPU: AMD R7 7800X3D

Motherboard: ASRock X670E Steel Legend (AM5)

RAM: Corsair Vengeance 32 GB (2 x 16 GB) DDR5-6000 CL30 Memory

Main SSD: Samsung 980 Pro 1 TB SSD
Storage SSD: Western Digital Black SN850X 2 TB SSD

GPU: Asus TUF GAMING OC Radeon RX 7800 XT (16 GB)

OS: Windows 11 (Build: 23H2)

Main Monitor: LG 27UD88-W 4K IPS

Secondary Monitor: LG 27UL850 4K HDR IPS

Yelandkeil wrote on 2/2/2023, 12:16 AM

MediaInfo does transfer meta-data, does NOT analyse content/signal.
The Info is 100% accurate thus.

-- Hard&Software for 5.1RealHDR10 --

ASUS TUF Gaming B550plus BIOS3202: 
*Thermaltake TOUGHPOWER GF1 850W 
*ADATA XPG GAMMIX S11PRO; 512GB/sys, 2TB/data 
*G.SKILL F4-3200C16Q-64GFX 
*AMD Ryzen9 5950x + LiquidFreezer II-240 
*XFX Speedster-MERC319-RX6900XT <-AdrenalinEdition 24.12.1
Windows11Pro: 24H2-26100.3915; Direct3D: 9.17.11.0272

Samsung 2xLU28R55 HDR10 (300CD/m², 1499Nits/peak) ->2xDPort
ROCCAT Kave 5.1Headset/Mic ->Analog (AAFOptimusPack 6.0.9403.1)
LG DSP7 Surround 5.1Soundbar ->TOSLINK

DC-GH6/H-FS12060E_HLG4k120p: WB=manual, Shutter=125, ISO=auto/manual
HERO5_ProtuneFlat2.7k60pLinear: WB=4800K, Shutter=auto, ISO=800

VEGASPro22 + XMediaRecode/Handbrake + DVDArchi7 
AcidPro10 + SoundForgePro14.0.065 + SpectraLayersPro7 
K-LitecodecPack17.8.0 (MPC Video Renderer for HDR10-Videoplayback on PC) 

MH7 wrote on 2/2/2023, 12:24 AM

MediaInfo does transfer meta-data, does NOT analyse content/signal.
The Info is 100% accurate thus.

Ah, okay. Thank you! 👍

John 14:6 | Romans 10:9-10, 13, 10:17 | Ephesians 2:8-9
————————————————————————————————————

Aussie VEGAS Post 20 User as of 9th February 2023 — Build 411 (Upgraded from VEGAS Pro 18)

VEGAS Pro Help: VEGAS Pro FAQs and TROUBLESHOOTING GUIDES

My YouTube Channel: https://www.youtube.com/@TechWiredGeek

Video Cameras: Sony FDR-AX700 and iPhone 12 Pro Max (iOS 17)

============================================

My New Productivity Workstation/Gaming PC 2024

CPU: AMD R7 7800X3D

Motherboard: ASRock X670E Steel Legend (AM5)

RAM: Corsair Vengeance 32 GB (2 x 16 GB) DDR5-6000 CL30 Memory

Main SSD: Samsung 980 Pro 1 TB SSD
Storage SSD: Western Digital Black SN850X 2 TB SSD

GPU: Asus TUF GAMING OC Radeon RX 7800 XT (16 GB)

OS: Windows 11 (Build: 23H2)

Main Monitor: LG 27UD88-W 4K IPS

Secondary Monitor: LG 27UL850 4K HDR IPS

Wolfgang S. wrote on 2/2/2023, 1:47 AM

MediaInfo does transfer meta-data, does NOT analyse content/signal.
The Info is 100% accurate thus.

Unfortunately, it are metadata really - Yelandkeil is right here.

But a lot of our rec709 cameras recorde also what was called "superwhite" - so luminance ranges higher then 235 (up to 255). So, how do you call a footage that shows luminance signals in the range of 16 to 255? What is then found in the metadata for that, what is shown in Medainfo? Mediainfo will show only the metadata, but what if those metadatas are simply wrong?

Please be also aware that you can adjust the scope range in the waveform monitor in Vegas in additon! That makes it more complicated. Given the settings for the scope range, 100% in the waveformmonitor can be 235 or 255.

But then the video looks a tad washed out like it's on the Legacy 8-Bit pixel format setting, yet it looks like some lights in the video are little less blown out, like a little more detail is retained. That's the best way that I can explain it, as it is in the Legacy 8-Bit pixel format setting.

.

This happens if your camera has recorded 0..255 or (more likely) 16..255 in reality, and if your project settings compress the luminance range to the legal range again. Then the signal becomes more flat, since the contrast is reduced here.

I would suggest you to analyse your footage in terms of the real luminance range it has, and set the project settings according to those findings.

Last changed by Wolfgang S. on 2/2/2023, 1:51 AM, changed a total of 1 times.

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

john_dennis wrote on 2/2/2023, 9:00 AM

Like Shakira's hips, the Histogram don't lie. The Waveform display might be a little coy at times.

Wolfgang S. wrote on 2/2/2023, 9:26 AM

Like Shakira's hips, the Histogram don't lie. The Waveform display might be a little coy at times.

That is exactly the point: the histogram shows signals in the color channels green and magenta up to 255. But the luminance goes up to something about 235 only. Funny enough,

You have set the scopes to studio RGB. Means, 100% in the waveform are 235. Ok, it goes a little bit higher then 100%, what is in line with the luminance in the histogram.

But to set it to limited is a question mark, since the scopes go higher then 235 = 100%. However, to set them to default or full does here not change a lot.

But try for fun to set the project properties to video (either 8bit video or 32 bit video level). You will see immediately, that the luminance range becomes compressed, and that in all tools. In the waveform, in the RGB parade, in the vectorscope but also in the histogram.

Last changed by Wolfgang S. on 2/2/2023, 9:31 AM, changed a total of 2 times.

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

MH7 wrote on 2/2/2023, 8:08 PM

I would suggest you to analyse your footage in terms of the real luminance range it has, and set the project settings according to those findings.

Well, out of curiosity, how would I go about doing that?

John 14:6 | Romans 10:9-10, 13, 10:17 | Ephesians 2:8-9
————————————————————————————————————

Aussie VEGAS Post 20 User as of 9th February 2023 — Build 411 (Upgraded from VEGAS Pro 18)

VEGAS Pro Help: VEGAS Pro FAQs and TROUBLESHOOTING GUIDES

My YouTube Channel: https://www.youtube.com/@TechWiredGeek

Video Cameras: Sony FDR-AX700 and iPhone 12 Pro Max (iOS 17)

============================================

My New Productivity Workstation/Gaming PC 2024

CPU: AMD R7 7800X3D

Motherboard: ASRock X670E Steel Legend (AM5)

RAM: Corsair Vengeance 32 GB (2 x 16 GB) DDR5-6000 CL30 Memory

Main SSD: Samsung 980 Pro 1 TB SSD
Storage SSD: Western Digital Black SN850X 2 TB SSD

GPU: Asus TUF GAMING OC Radeon RX 7800 XT (16 GB)

OS: Windows 11 (Build: 23H2)

Main Monitor: LG 27UD88-W 4K IPS

Secondary Monitor: LG 27UL850 4K HDR IPS

RogerS wrote on 2/2/2023, 9:19 PM

There's a thread here with instructions and a list of actual levels. Shoot black with a lenscap on and whites into a light letting it completely blow out. Look at the histogram in Vegas.

MH7 wrote on 2/2/2023, 9:32 PM

There's a thread here with instructions and a list of actual levels. Shoot black with a lenscap on and whites into a light letting it completely blow out. Look at the histogram in Vegas.

Okay, I’ll definitely look at doing that. I have seen that thread. Thank you!

John 14:6 | Romans 10:9-10, 13, 10:17 | Ephesians 2:8-9
————————————————————————————————————

Aussie VEGAS Post 20 User as of 9th February 2023 — Build 411 (Upgraded from VEGAS Pro 18)

VEGAS Pro Help: VEGAS Pro FAQs and TROUBLESHOOTING GUIDES

My YouTube Channel: https://www.youtube.com/@TechWiredGeek

Video Cameras: Sony FDR-AX700 and iPhone 12 Pro Max (iOS 17)

============================================

My New Productivity Workstation/Gaming PC 2024

CPU: AMD R7 7800X3D

Motherboard: ASRock X670E Steel Legend (AM5)

RAM: Corsair Vengeance 32 GB (2 x 16 GB) DDR5-6000 CL30 Memory

Main SSD: Samsung 980 Pro 1 TB SSD
Storage SSD: Western Digital Black SN850X 2 TB SSD

GPU: Asus TUF GAMING OC Radeon RX 7800 XT (16 GB)

OS: Windows 11 (Build: 23H2)

Main Monitor: LG 27UD88-W 4K IPS

Secondary Monitor: LG 27UL850 4K HDR IPS

Yelandkeil wrote on 2/2/2023, 10:12 PM

Assuming you're about producing traditional TV-videos and won't go 32bit...blabla, you have 2 choices for project-setup: 

1, 
8bit legacy. 
This mode does tough neither your edit invironment nor properties of the footage you put onto timeline. 
Say you are editing with a computer monitor (its color space is sRGB or its color range=0-255), then you adjust all your footage right on the timeline till you're satified and, by rendering out, add the levels filter to limit your signal to 16-235 (that's the TV-video's color range). 

2, 
8bit full range. 
This is the idiot-easy mode presuming you alread sit in front of your computer monitor. 
Footage that you put onto timeline will be determined which color range they do have, if it's limited (16-235) then VEGAS expands the range to 0-255. 
After you finished your edit and go rendering, VEGAS converts your timeline signal automatically to standard TV-color range. 

2.1, 
During the edit if you find VEGAS's expansion is absurd and cuts too much details of your footage, you also can adjust the footage color range manually and vice versa. 

3, 
So, forget your Sony FDR-AX700, forget XAV-S, any source footage with no matter what kind range are all welcome in VEGAS. 

For production, your project must aim at parameters/properties of that product instead of source material which can, may and dare vary. 

4, 
Be assiduous and take some time to study the scopes till you know how they function and what they are monitoring. 
I can assure you, asking in any forum is the most silly way. 
Forgive my rudeness. 

-- Hard&Software for 5.1RealHDR10 --

ASUS TUF Gaming B550plus BIOS3202: 
*Thermaltake TOUGHPOWER GF1 850W 
*ADATA XPG GAMMIX S11PRO; 512GB/sys, 2TB/data 
*G.SKILL F4-3200C16Q-64GFX 
*AMD Ryzen9 5950x + LiquidFreezer II-240 
*XFX Speedster-MERC319-RX6900XT <-AdrenalinEdition 24.12.1
Windows11Pro: 24H2-26100.3915; Direct3D: 9.17.11.0272

Samsung 2xLU28R55 HDR10 (300CD/m², 1499Nits/peak) ->2xDPort
ROCCAT Kave 5.1Headset/Mic ->Analog (AAFOptimusPack 6.0.9403.1)
LG DSP7 Surround 5.1Soundbar ->TOSLINK

DC-GH6/H-FS12060E_HLG4k120p: WB=manual, Shutter=125, ISO=auto/manual
HERO5_ProtuneFlat2.7k60pLinear: WB=4800K, Shutter=auto, ISO=800

VEGASPro22 + XMediaRecode/Handbrake + DVDArchi7 
AcidPro10 + SoundForgePro14.0.065 + SpectraLayersPro7 
K-LitecodecPack17.8.0 (MPC Video Renderer for HDR10-Videoplayback on PC) 

Wolfgang S. wrote on 2/3/2023, 2:56 AM

Well, out of curiosity, how would I go about doing that?

Use the media generator inside Vegas, to generate a grey picture with a luminance range from 0 to 255.

Have a look to histogram and wafeform monitor, to see how the luminance looks like. Not composite, please.
Make that for different settings of the waveform monitor, to see at what pegel of the scops you will find the 100% and 0%.

And do that for different project settings.


When you have learned that, you have the basics to analyse your footage.
 

Off course, this is a silly answer only! :)

Last changed by Wolfgang S. on 2/3/2023, 4:18 AM, changed a total of 1 times.

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

Yelandkeil wrote on 2/3/2023, 3:41 AM

😁😁 I AM so silly that I forgot to tell him which preview window my scopes are monitoring. Ohyeye. 😰😰😰

I swear, from now on never reply silly and Silly.
Bye.

Last changed by Yelandkeil on 2/3/2023, 3:52 AM, changed a total of 1 times.

-- Hard&Software for 5.1RealHDR10 --

ASUS TUF Gaming B550plus BIOS3202: 
*Thermaltake TOUGHPOWER GF1 850W 
*ADATA XPG GAMMIX S11PRO; 512GB/sys, 2TB/data 
*G.SKILL F4-3200C16Q-64GFX 
*AMD Ryzen9 5950x + LiquidFreezer II-240 
*XFX Speedster-MERC319-RX6900XT <-AdrenalinEdition 24.12.1
Windows11Pro: 24H2-26100.3915; Direct3D: 9.17.11.0272

Samsung 2xLU28R55 HDR10 (300CD/m², 1499Nits/peak) ->2xDPort
ROCCAT Kave 5.1Headset/Mic ->Analog (AAFOptimusPack 6.0.9403.1)
LG DSP7 Surround 5.1Soundbar ->TOSLINK

DC-GH6/H-FS12060E_HLG4k120p: WB=manual, Shutter=125, ISO=auto/manual
HERO5_ProtuneFlat2.7k60pLinear: WB=4800K, Shutter=auto, ISO=800

VEGASPro22 + XMediaRecode/Handbrake + DVDArchi7 
AcidPro10 + SoundForgePro14.0.065 + SpectraLayersPro7 
K-LitecodecPack17.8.0 (MPC Video Renderer for HDR10-Videoplayback on PC) 

RogerS wrote on 2/3/2023, 4:15 AM

Use project settings of 8-bit video levels to assess white and black as that will affect the waveform (histogram should be the same between both though).