Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does ofxRPIWindow pass HDR images or 10bit images? #8

Open
docdude opened this issue Aug 10, 2021 · 0 comments
Open

Does ofxRPIWindow pass HDR images or 10bit images? #8

docdude opened this issue Aug 10, 2021 · 0 comments

Comments

@docdude
Copy link

docdude commented Aug 10, 2021

Trying to render ofFloatImages to handle HDR, EXR, 10bit images.
The new raspberry kernel 5.10 handles HDR metadata now verified using the following tool drm_info, https://github.com/ascent12/drm_info

`
Node: /dev/dri/card1
├───Driver: vc4 (Broadcom VC4 graphics) version 0.0.0 (20140616)
│ ├───DRM_CLIENT_CAP_STEREO_3D supported
│ ├───DRM_CLIENT_CAP_UNIVERSAL_PLANES supported
│ ├───DRM_CLIENT_CAP_ATOMIC supported
│ ├───DRM_CLIENT_CAP_ASPECT_RATIO supported
│ ├───DRM_CLIENT_CAP_WRITEBACK_CONNECTORS supported
│ ├───DRM_CAP_DUMB_BUFFER = 1
│ ├───DRM_CAP_VBLANK_HIGH_CRTC = 1
│ ├───DRM_CAP_DUMB_PREFERRED_DEPTH = 24
│ ├───DRM_CAP_DUMB_PREFER_SHADOW = 0
│ ├───DRM_CAP_PRIME = 3
│ ├───DRM_CAP_TIMESTAMP_MONOTONIC = 1
│ ├───DRM_CAP_ASYNC_PAGE_FLIP = 1
│ ├───DRM_CAP_CURSOR_WIDTH = 64
│ ├───DRM_CAP_CURSOR_HEIGHT = 64
│ ├───DRM_CAP_ADDFB2_MODIFIERS = 1
│ ├───DRM_CAP_PAGE_FLIP_TARGET = 0
│ ├───DRM_CAP_CRTC_IN_VBLANK_EVENT = 1
│ ├───DRM_CAP_SYNCOBJ = 1
│ └───DRM_CAP_SYNCOBJ_TIMELINE = 0
├───Device: platform brcm,bcm2711-vc5
│ └───Available nodes: primary
├───Framebuffer size
│ ├───Width: [0, 7680]
│ └───Height: [0, 7680]
├───Connectors
│ ├───Connector 0
│ │ ├───Object ID: 32
│ │ ├───Type: HDMI-A
│ │ ├───Status: connected
│ │ ├───Physical size: 1600x900 mm
│ │ ├───Subpixel: unknown
│ │ ├───Encoders: {0}
│ │ ├───Modes
│ │ │ ├───[email protected] preferred driver phsync pvsync
│ │ │ ├───[email protected] driver phsync pvsync 256:135
│ │ │ ├───[email protected] driver phsync pvsync 256:135
│ │ │ ├───[email protected] driver phsync pvsync 256:135
│ │ │ ├───[email protected] driver phsync pvsync 256:135
│ │ │ ├───[email protected] driver phsync pvsync 256:135
│ │ │ ├───[email protected] driver phsync pvsync 16:9
│ │ │ ├───[email protected] driver phsync pvsync 16:9
│ │ │ ├───[email protected] driver phsync pvsync 16:9
│ │ │ ├───[email protected] driver phsync pvsync 16:9
│ │ │ ├───[email protected] driver phsync pvsync 16:9
│ │ │ ├───[email protected] driver phsync pvsync 16:9
│ │ │ ├───[email protected] driver phsync pvsync 16:9
│ │ │ ├───[email protected] driver phsync pvsync 16:9
│ │ │ ├───[email protected] driver phsync pvsync 16:9
│ │ │ ├───[email protected] driver phsync pvsync 16:9
│ │ │ ├───[email protected] driver phsync pvsync interlace
│ │ │ ├───[email protected] driver phsync pvsync interlace 16:9
│ │ │ ├───[email protected] driver phsync pvsync interlace 16:9
│ │ │ ├───[email protected] driver phsync pvsync
│ │ │ ├───[email protected] driver phsync pvsync 16:9
│ │ │ ├───[email protected] driver phsync pvsync interlace 16:9
│ │ │ ├───[email protected] driver phsync pvsync 16:9
│ │ │ ├───[email protected] driver phsync pvsync 16:9
│ │ │ ├───[email protected] driver phsync pvsync 16:9
│ │ │ ├───[email protected] driver phsync pvsync 16:9
│ │ │ ├───[email protected] driver phsync pvsync 16:9
│ │ │ ├───[email protected] driver phsync pvsync
│ │ │ ├───[email protected] driver phsync pvsync 16:9
│ │ │ ├───[email protected] driver phsync pvsync 16:9
│ │ │ ├───[email protected] driver phsync pvsync 16:9
│ │ │ ├───[email protected] driver nhsync nvsync
│ │ │ ├───[email protected] driver phsync pvsync
│ │ │ ├───[email protected] driver nhsync nvsync 16:9
│ │ │ ├───[email protected] driver nhsync nvsync interlace dblclk 4:3
│ │ │ ├───[email protected] driver nhsync nvsync 16:9
│ │ │ ├───[email protected] driver nhsync nvsync 4:3
│ │ │ ├───[email protected] driver nhsync nvsync 16:9
│ │ │ ├───[email protected] driver nhsync nvsync 4:3
│ │ │ ├───[email protected] driver nhsync nvsync 4:3
│ │ │ ├───[email protected] driver nhsync nvsync
│ │ │ ├───[email protected] driver nhsync nvsync 4:3
│ │ │ └───[email protected] driver nhsync pvsync
│ │ └───Properties
│ │ ├───"EDID" (immutable): blob = 223
│ │ ├───"DPMS": enum {On, Standby, Suspend, Off} = On
│ │ ├───"link-status": enum {Good, Bad} = Good
│ │ ├───"non-desktop" (immutable): range [0, 1] = 0
│ │ ├───"TILE" (immutable): blob = 0
│ │ ├───"CRTC_ID" (atomic): object CRTC = 76
│ │ ├───"Colorspace": enum {Default, SMPTE_170M_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, opRGB, BT2020_CYCC, BT2020_RGB, BT2020_YCC, DCI-P3_RGB_D65, DCI-P3_RGB_Theater} = Default
│ │ ├───"left margin": range [0, 100] = 0
│ │ ├───"right margin": range [0, 100] = 0
│ │ ├───"top margin": range [0, 100] = 0
│ │ ├───"bottom margin": range [0, 100] = 0
│ │ ├───"max bpc": range [8, 12] = 8
│ │ └───"HDR_OUTPUT_METADATA": blob = 0

`
My app works great with the addon, thanks. It will render normal SDR images and even 10bit images if i use the dtoverlay=vc4-fkms-3d-pi4 but wont render the 10bit image if I use the KMS overlay (vc4-kms-3d-pi4)..

This is the image source https://github.com/jursonovicst/gradient

I use ofxTinyEXR addon for EXR images but again no output.
I don't believ it's an issue with the addon, just trying to figure out how to configure it to pass higher bit images as it seems the kernel drivers can already process HDR data.

I found this: https://developer.qualcomm.com/docs/adreno-gpu/developer-guide/tutorials/android/hdr10.html which I am going to test, but the required extensions do not seem to be part of my Mesa library(newest version 21.2) .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant