AcademySoftwareFoundation / AcademySoftwareFoundation/OpenColorIO
Allow File Rules to leverage file format metadata
- Lenguaje dominante
- C++
- Estrellas
- 2.1k
- Forks
- 503
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
Currently the OCIO File Rules are only based on the path string for the media. This was done intentionally since dealing with file format metadata was deemed too complex for the first pass at the feature. However, it's definitely the case that there often is metadata in the file header that could be useful for determining what the appropriate color space is and it would be useful for the File Rules to be able to leverage it.
We do not want to add any dependencies for file format libraries on to OCIO to support this feature, so it needs to be implemented in such a way that the host application parses the files and provides the metadata in some neutral representation, such as a pair of field & value strings. OpenImageIO has some techniques for representing file-format agnostic metadata that might be a good model for how this could work (without adding a dependency on OIIO).
Of course the metadata in file headers is often wrong, so there needs to be sufficient control in the File Rules to control the relative precedence of what is in the file relative to the existing path-based rules.
Here is a presentation that [discussed OpenEXR](https://docs.google.com/presentation/d/1sY55UHYi2AJF6EPYDYY-mvaJUCzZCkWisrj-a9yhg2w/edit?usp=sharing) that is related.
Guía de contribución
Línea de trabajo
Comience revisando las OCIO File Rules existentes y la presentación de OpenEXR enlazada. Defina cómo se representan los metadatos de campos y valores proporcionados por el host y cómo se controla su precedencia con respecto a las reglas basadas en rutas. Se considera terminado cuando File Rules puede utilizar metadatos neutros sin añadir dependencias de bibliotecas de formatos de archivo.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- cpp
- Área
- backend-api-design
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 25/100