Flatbuffers: selectable custom LUT files #334
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
awawa-dev
force-pushed
the
Flatbuffers_Custom_LUT_files_API
branch
from
3488738
to
ba42c26
Compare
chbartsch
pushed a commit
to chbartsch/HyperHDR
that referenced
this pull request
Nov 29, 2022
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The JSON API for controlling tone mapping has been extended to include an optional LUT file name for FlatBuffers.
This allows to select proper LUT for tone mapping depending on the external video properties.
For example you can have two or more LUT files for selection: one for SDR, one for HDR, one for DV etc.
HyperHDR expects that these files are located in HyperHDR home folder e.g. /home/pi/.hyperhdr
What kind of change does this PR introduce? (check at least one)
If changing the UI of web configuration, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)