-
Notifications
You must be signed in to change notification settings - Fork 186
Adding LensShadingCorrection maps and ToneCurve to controls metadata #356
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -1374,4 +1374,42 @@ controls: | |
| The nominal range is [-180, 180], where 0° leaves hues unchanged and the | ||
| range wraps around continuously, with 180° == -180°. | ||
|
|
||
| - EnableLensShadingCorrectionMapOutput: | ||
| type: bool | ||
| direction: inout | ||
| description: | | ||
| Indicates if the lens shading correction maps should be set in frame- | ||
| metadata for each frame. Returns true if tables are successfully set. | ||
|
|
||
| - LensShadingCorrectionMaps: | ||
| type: float | ||
| direction: out | ||
| description: | | ||
| A map giving the lens shading correction factors. Dimesnions of the | ||
| returned table is [number of channels, sizeX, sizeY] (planar tables) | ||
| size: [n] | ||
|
|
||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. My personal preference is probably for a single metadata control for this, maybe
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I agree that one single table would makes things less verbose. Question on this subject: How are monochrome camereas handled (I don't have any to test...)? From what I've seen they just fill RGB with the same values but maintain the RGB channels. Is this correct? |
||
| - LensShadingCorrectionMapSize: | ||
| type: uint32_t | ||
| direction: out | ||
| description: | | ||
| The number of channels/maps and the size of the lens shading correction | ||
| maps in pixels. E.g. [3, 32, 32] | ||
| size: [3] | ||
|
|
||
| - ToneCurve: | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd argue that GammaCurves are a subset of ToneCurves :) |
||
| type: float | ||
| direction: out | ||
| description: | | ||
| A profile tone curve to apply on linear RGB - as it seems it has the sRGB | ||
| gamma curve baked in. | ||
| size: [n] | ||
|
|
||
| - NoiseProfile: | ||
| type: float | ||
| direction: out | ||
| description: | | ||
| The noise profile [Scale, Offset]. | ||
| size: [2] | ||
|
|
||
| ... | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
iteratorfeels a bit verbose here. Could we leave it out and doinstead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure