-
Notifications
You must be signed in to change notification settings - Fork 58
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
LUTPaths: when is it used/useful? #16
Comments
I’m also interested in knowing more about the use of LUTs in CineForm. |
Active Metadata is runs out of this path. CineForm FirstLight and GoPro Studio uses these for color correction and other visual enhancements that occur during decode. Also the defaults paths are typically overridden with system environment controls. |
I just noted that Active Metadata was not be supported within VDFM, some CineForm user will miss this (including myself). |
Good to know. I planned to collect some feedback and then have second attempt. What do you think about replacing Also related somehow.. |
Ok, atlbase can be removed with no loss by adding this fragment to settings.h
|
Cool. I will try that out. |
This didn't work for me. So I cleaned up the code a different way. I have removed settings.cpp/h and atlbase.h from the Windows builds. |
Great. |
An existing CineForm users will have these setup via the registry keys. New users can run with the defaults as they have not disk based database of active metadata changes. Users can manipulate the LUTPaths and DBPaths for interesting workflows like this https://vimeo.com/10024749 |
Has anyone implemented metadata support outside of first light? |
There is some weirdness here (hardcoded fully qualified path)
cineform-sdk/Codec/lutpath.cpp
Line 483 in 1eb2cb7
and here
cineform-sdk/DecoderSDK/SampleMetadata.cpp
Line 62 in 1eb2cb7
Is this actually executed at some point?
Also there are registry access, system variable access etc. Is it a convention shared between all CineForm-enabled programs? Which programs create these registry keys and lut files?
The text was updated successfully, but these errors were encountered: