AcademySoftwareFoundation / AcademySoftwareFoundation/OpenColorIO
Feature Request for looks
- Lingua principale
- C++
- Stelle
- 2.1k
- Fork
- 503
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
Hi everyone,
we had a bit of a conversation about looks in the UX group yesterday and I wanted to create a feature request so it can be discussed more broadly.
I am trying to find a simple solution for non-OCIO experts like me to load looks in a DCC software. Expert users in many VFX studios combine "Views + Looks" but I would like something simpler, if possible. ;-)
So yesterday someone (I can't remember the name, sorry!) threw the idea of [active_looks]. You could have 50 looks available in the config, but only 5 "active"... exactly like displays and views. I'd be curious to see what people thinks of this feature request. In an OCIO config, it could look like this :
```
active_displays: [Display - sRGB, Display - Rec.1886 / Rec.709 Video, Display - P3-D65, Display - P3-DCI]
active_views: [Output - SDR Video - ACES 1.0, ACES 1.1, Output - HDR Cinema (108 nits & P3 lim) - ACES 1.1, Raw]
active_looks: [Vision, Earthy, Complement, Bipack]
```
The idea would be then to have a dropdown menu in "Viewers" for the active looks, if that makes sense. Here is a mockup to give you an idea :

Blender has kinda done something similar :

I know that Nuke and Katana have come up with "OCIOLookTransform" nodes as well but I guess in the viewer it would be more convenient.


A mockup in a render engine would be like this for example :

Thanks,
Chris
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
La richiesta non indica file, test o punti di ingresso. Inizia esaminando come active_displays e active_views sono rappresentati ed esposti in Viewers, quindi determina come dovrebbero integrarsi la configurazione active_looks proposta e il dropdown; il lavoro sarà completato quando saranno concordati la sintassi di configurazione e il comportamento del viewer.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- cpp
- Ambito
- design, desktop
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100