HDRの録画画面のプレビューの色が濃すぎる
- Thread starter アリス
- Start date
Suslik V
Active Member
OBS Studio creates a log file each time you run it which contains very useful diagnostic information. Without a log file, it's much harder for any support volunteers to figure out problems and your post may be ignored.
To upload a log file, go to the Help menu > Log Files > Upload Last Log File. "Last Log File" is for the last session (the last time you ran OBS). In some cases you may be asked to select "Current Log File" instead, which is for the current session.
Click on the "Copy URL" button to copy the link to your clipboard, then paste the link in your forum...
To upload a log file, go to the Help menu > Log Files > Upload Last Log File. "Last Log File" is for the last session (the last time you ran OBS). In some cases you may be asked to select "Current Log File" instead, which is for the current session.
Click on the "Copy URL" button to copy the link to your clipboard, then paste the link in your forum...
返信ありがとうございます。
これで大丈夫ですか？
これで大丈夫ですか？
Suslik V
Active Member
Where do you see the "darker" picture - in OBS Preview window or in some media player? If in OBS, then can you make screenshot of the OBS Preview via right-click menu option - "Screenshot (Preview)" for Preview, "Screenshot (Source)" for source? And check if the screenshot itself is OK for you (has normal colors).
The capture was OK and shouldn't cause color errors.
This "BufferDesc.Format: 24" - means that the game picture was captured as 10-bit texture (
(details: https://obsproject.com/forum/threads/how-to-save-hdr-screenshots-with-obs-on-windows.186747/)
If color inaccuracies seen only in the media player - please, try to make test recording for few seconds, so OBS writes to its log the encoder activity/settings and errors if any. Then attach this new log to your post.
The capture was OK and shouldn't cause color errors.
Code:
19:48:31.240: [game-capture: 'ゲームキャプチャ'] DXGI_SWAP_CHAIN_DESC:
19:48:31.240: BufferDesc.Width: 3840
19:48:31.240: BufferDesc.Height: 2160
19:48:31.240: BufferDesc.RefreshRate.Numerator: 60
19:48:31.240: BufferDesc.RefreshRate.Denominator: 1
19:48:31.240: BufferDesc.Format: 24
...DXGI_FORMAT_R10G10B10A2_UNORM).(details: https://obsproject.com/forum/threads/how-to-save-hdr-screenshots-with-obs-on-windows.186747/)
If color inaccuracies seen only in the media player - please, try to make test recording for few seconds, so OBS writes to its log the encoder activity/settings and errors if any. Then attach this new log to your post.
色が濃い暗い画像はOBSプレビューウィンドウです。
スクリーンショットも録画動画も全て色が濃い暗いです。
スクリーンショットも録画動画も全て色が濃い暗いです。
Suslik V
Active Member
Log is OK. Preview and screenshots made by OBS should be OK. And this is strange that you see them darker. Maybe you can try other display device - other PC, smartphone (if you find a way) where the wide gamut supported, to view these ".jxr" screenshots?
From my side, your display device reporting very limited support for HDR (like 8-bit was up-scaled to 12-bit, because of poor panel):
This is too low numbers. I'm not an expert in HDR, but from logs on this forum you may find out that numbers close to let's say 90% (0.90) of gamut of the P3-D65 device better suits for HDR content than 73% (0.73) in your case. So, maybe you are looking at the picture that simply cannot be displayed better on this device? And this is normal for such display? The Windows itself can scale-up/sacle-down images on its own (to fit the bitness of the pictures to the screen). So, my guess was: "maybe you are looking at screenshots that were modified on the fly (during display)?".
From my side, your display device reporting very limited support for HDR (like 8-bit was up-scaled to 12-bit, because of poor panel):
08:46:18.939: relative_gamut_area=[709=0.998664, P3=0.736186, 2020=0.528164]This is too low numbers. I'm not an expert in HDR, but from logs on this forum you may find out that numbers close to let's say 90% (0.90) of gamut of the P3-D65 device better suits for HDR content than 73% (0.73) in your case. So, maybe you are looking at the picture that simply cannot be displayed better on this device? And this is normal for such display? The Windows itself can scale-up/sacle-down images on its own (to fit the bitness of the pictures to the screen). So, my guess was: "maybe you are looking at screenshots that were modified on the fly (during display)?".
Suslik V
Active Member
Do you have OBS log file from the moment when you connected other display? Just to compare info from the both display devices.
And meanwhile, can you set different "RGB10A2 Color Space" option of the Game Capture source? It is located somewhere at the bottom of the Game Capture properties (try to scroll Game Capture source Properties down).
I see that OBS is set to output:
And it is wise to make screenshots of the Display Capture source to make sure that problem exist only in the Game Capture.
And meanwhile, can you set different "RGB10A2 Color Space" option of the Game Capture source? It is located somewhere at the bottom of the Game Capture properties (try to scroll Game Capture source Properties down).
I see that OBS is set to output:
08:46:19.463: YUV mode: Rec. 2100 (PQ)/PartialAnd it is wise to make screenshots of the Display Capture source to make sure that problem exist only in the Game Capture.
これが他のディスプレイを接続したログファイルです。
ディスプレイに問題はない気がしますがどうですか？
RGB10A2カラースペースはRec2100PQを選択しています。
Rec2100PQを選択しないとHDRにならないと説明をうけました。
ですがRec2100PQを選択した途端、色がおかしくなります。
ディスプレイに問題はない気がしますがどうですか？
RGB10A2カラースペースはRec2100PQを選択しています。
Rec2100PQを選択しないとHDRにならないと説明をうけました。
ですがRec2100PQを選択した途端、色がおかしくなります。
Suslik V
Active Member
This display device is running at 8-bit per color component:
previous (LG) claimed that it was running 12-bit:
But both has same gamut that is close to 8-bit space. It is not right or wrong - just slightly different devices.
For some devices in the display settings (device menu, accessible by device buttons or via remote) it is possible to configure video mode of the device (HDR, 10-bit etc) but this all depends on manufacturer, model, port of the connection (at highest resolution and framerate not all interfaces can handle more that 8-bit - look at the manual what modes and at what conditions your device supports).
From the start of HDR development in OBS there were implemented 10-bit formats first, then was added 16-bit formats. Support for 12-bit is not implemented yet. So, for OBS it it better to have 10-bit devices or 16-bit devices. Thus, if you can set your display device to 10-bit mode - try it instead of 12-bit. As far as I understand Windows OS doing all math with 16-bit per component precision, so can fit anything to any display device.
As for the RGB10A2 textures - they can be in sRGB space or in Rec. 2100 (Rec.2020/BT.2020). OBS "doesn't know" what it is capturing right now, so user should select manually.
For implementation details see: https://github.com/obsproject/obs-studio/pull/6249
Because your texture is RGB10A2 ("BufferDesc.Format: 24" from the log) - then both values of the parameter already assumes 10-bit input. The math for proper rendering (without color errors) will be chosen depending on OBS Advanced settings and where the window lies (on which display device), because user can drag preview window to other device, for example to 8-bit device.
In OBS Advanced settings you specifying canvas parameters (or let's say "output" parameters). All sources that will be placed on this canvas can be in different bitness/spaces/color_formats etc. Thus, if you set 10-bit there - you forcing OBS to scale everything to 10-bit, so final output will be at 10-bit. If you set here 8-bit, you forcing all sources to be scaled on the fly to 8-bit, so final output will be at 8-bit.
I would experiment with RGB10A2 setting while keeping OBS Advanced at some 10-bit format. Color Range set to "Limited/Partial" are good for TV screens but you may try "Full" as well.
Darker colors (sometimes mistaken to very high contrast) is when full range video represented on full range monitor without proper scaling - software "thinks" that the video has Limited range (while it is truly Full range). So, take it in mind too (you can imagine 8-bit as "limited" and 10-bit as "full" - behavior is the same).
Edit: more about color range. Shaded image - means Limited range video represented on Full range monitor but software "thinks" that this is Full range video (while it is truly Limited range).
Code:
...
01:58:05.635: bits_per_color=8
Code:
...
19:47:10.688: bits_per_color=12For some devices in the display settings (device menu, accessible by device buttons or via remote) it is possible to configure video mode of the device (HDR, 10-bit etc) but this all depends on manufacturer, model, port of the connection (at highest resolution and framerate not all interfaces can handle more that 8-bit - look at the manual what modes and at what conditions your device supports).
From the start of HDR development in OBS there were implemented 10-bit formats first, then was added 16-bit formats. Support for 12-bit is not implemented yet. So, for OBS it it better to have 10-bit devices or 16-bit devices. Thus, if you can set your display device to 10-bit mode - try it instead of 12-bit. As far as I understand Windows OS doing all math with 16-bit per component precision, so can fit anything to any display device.
As for the RGB10A2 textures - they can be in sRGB space or in Rec. 2100 (Rec.2020/BT.2020). OBS "doesn't know" what it is capturing right now, so user should select manually.
For implementation details see: https://github.com/obsproject/obs-studio/pull/6249
Because your texture is RGB10A2 ("BufferDesc.Format: 24" from the log) - then both values of the parameter already assumes 10-bit input. The math for proper rendering (without color errors) will be chosen depending on OBS Advanced settings and where the window lies (on which display device), because user can drag preview window to other device, for example to 8-bit device.
In OBS Advanced settings you specifying canvas parameters (or let's say "output" parameters). All sources that will be placed on this canvas can be in different bitness/spaces/color_formats etc. Thus, if you set 10-bit there - you forcing OBS to scale everything to 10-bit, so final output will be at 10-bit. If you set here 8-bit, you forcing all sources to be scaled on the fly to 8-bit, so final output will be at 8-bit.
I would experiment with RGB10A2 setting while keeping OBS Advanced at some 10-bit format. Color Range set to "Limited/Partial" are good for TV screens but you may try "Full" as well.
Darker colors (sometimes mistaken to very high contrast) is when full range video represented on full range monitor without proper scaling - software "thinks" that the video has Limited range (while it is truly Full range). So, take it in mind too (you can imagine 8-bit as "limited" and 10-bit as "full" - behavior is the same).
Edit: more about color range. Shaded image - means Limited range video represented on Full range monitor but software "thinks" that this is Full range video (while it is truly Limited range).
Last edited:
パソコンのAMDの設定を変更して１０ビットには出来たようです。
それと全てをフルレンジに変更しました。ですが何も変わりません。
RGB10A2設定はRec2100PQだと色が暗くなりsRGBだと普通に見えます。
Rec2100PQじゃないとHDR映像にならないという情報は間違いなのですか？
sRGBでもHDR映像になるのですか？
それと全てをフルレンジに変更しました。ですが何も変わりません。
RGB10A2設定はRec2100PQだと色が暗くなりsRGBだと普通に見えます。
Rec2100PQじゃないとHDR映像にならないという情報は間違いなのですか？
sRGBでもHDR映像になるのですか？
Suslik V
Active Member
sRGB can be 8-bit, and 10-bit, and more (16-bit for sure). For more than 8-bits it usually named scRGB (one letter added). In the UI OBS ignores this nuance and simply keeps name same for both 8 and 10 bits (but the math algorithms, inside the program, they are different).
For you as user, only format of the texture (or buffer from where it copied) is important. You cannot store in the small buffer huge amount of data without loss.
Your OBS successfully captured texture
Casual PC screen is sRGB device and lacks some features of modern standard (for example, environment light affects human eye perception and should be taken into account, thus recorded video can has preferable "environment" where video should be viewed - for PC content it is bright room or office, but not cinema). Also, sRGB has special non-linearness that worked well for both: human eye and CRT-screen phosphors. Newer tech like TFT and AMOLED has different characteristics, so new standards developed. Thus, it is preferable to use Rec.2100 (PQ or HLG) when you producing new videos with 10-bit or more precision per color component. And that is why you set OBS canvas (output) "color space" in Advanced settings of OBS to "Rec.2100".
For you as user, only format of the texture (or buffer from where it copied) is important. You cannot store in the small buffer huge amount of data without loss.
Your OBS successfully captured texture
DXGI_FORMAT_R10G10B10A2_UNORM that is 10-bit texture. You have nothing to worry about. If OBS will report other texture buffer, lets say: "BufferDesc.Format: 28" (this is "DXGI_FORMAT_R8G8B8A8_UNORM" - one of the 8-bit formats), then it means that the game was rendered this way (8-bit) - OBS just captures format that was rendered by the game. And this can be changed only in the game graphics settings (if supported).Casual PC screen is sRGB device and lacks some features of modern standard (for example, environment light affects human eye perception and should be taken into account, thus recorded video can has preferable "environment" where video should be viewed - for PC content it is bright room or office, but not cinema). Also, sRGB has special non-linearness that worked well for both: human eye and CRT-screen phosphors. Newer tech like TFT and AMOLED has different characteristics, so new standards developed. Thus, it is preferable to use Rec.2100 (PQ or HLG) when you producing new videos with 10-bit or more precision per color component. And that is why you set OBS canvas (output) "color space" in Advanced settings of OBS to "Rec.2100".