AcademySoftwareFoundation / AcademySoftwareFoundation/OpenColorIO
Allow File Rules to leverage file format metadata
- Vorherrschende Sprache
- C++
- Sterne
- 2.1k
- Forks
- 503
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
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.
Beitragsleitfaden
Rechercherichtung
Beginnen Sie mit der Durchsicht der vorhandenen OCIO File Rules und der verlinkten OpenEXR-Präsentation. Definieren Sie, wie vom Host bereitgestellte Feld- und Wertmetadaten dargestellt werden und wie ihre Priorität gegenüber pfadbasierten Regeln gesteuert wird. Als abgeschlossen gilt dies, wenn File Rules neutrale Metadaten verwenden können, ohne Abhängigkeiten von Bibliotheken für Dateiformate hinzuzufügen.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- cpp
- Bereich
- backend-api-design
- Issue-Typ
- Feature
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 25/100