| |
|---|
Virtual Townhall / BoF | |
Color Interop ID namespace | If it’s a CIF color space, no namespace required. If it’s not, a namespace is required However, if a user wants “my_studio:official_interop_id”, it now conflicts with the built-in IDs - this comment was from Sean How do we want to handle this? Is there a default name if a config author doesn’t supply one? The issue comes if someone already has a color space named one of the official CIF color spaces, but it is defined differently - what does an application do? Should it respect the namespace:name if it finds it first, and only after if it doesn’t find a match, default to the CIF defaults with namespace stripped We have some time to figure it out, please respond on the PR/issue, we’ll try to get feedback at SIGGRAPH as well
|
Config merging | PR is up! #2179 Formalizing this makes the process much more transparent - allows config authors to control what happens to their config, and what gets merged, vs an application doing it in the background with no visibility on what is happening. This is already implemented in Flame. Many merging strategies are available to choose what works for your situation. Different sections of your config can have different merge strategies. Does not edit core library functionality - is getting added to AppHelpers Large number of unit tests to hopefully cover scenarios and edge cases Example: difference in reference spaces - merging will deal with this based on your chosen merge strategy Duplicates of color spaces that have different names - i.e. camera log formats. There’s an option to keep one of those, and add the other name as an alias
Kevin - supportive, but need to make sure a config author can turn the ability to merge off if they need to Mark - does not support this feature, wishes to keep this as currently is, with applications creating in-memory color spaces. Does not wish to give the user control in this area - seems dangerous. Seems like added complexity we don’t need, when all of this is already possible through the library if you know what you’re doing. Thomas - looks good, would have used this functionality when at Weta Cuneyt - this feature would have been extremely useful when implementing OCIO in 3Ds Max. Not all application devs are super familiar with color, and catching edge cases is complicated. Would love to rely on OCIO for this. There was a lot of discussion around this and I was unable to take effective notes and participate in the discussion at the same time. If folks would like the recording, please reach out.
|
AMF transform ID attribute formatting | |