Re: parseColorSpaceFromString() issue


Sean Looper <sean....@...>
 

I don't think so. I used to use the "colorspace" attribute stored on assets at my *previous* job to determine color space and only fall back to the file name if that didn't exist. Naming conventions are fragile things, as we know.

On Fri, Oct 3, 2014 at 6:13 PM, Sam Richards <sam.ri...@...> wrote:
I'm going through this right now, and have the horrible problem of trying to educate people to add the right color space to their filename, knowing full well that there is a strong likelyhood that initially things will only get worse, where they are writing files out as linear, but calling them log. 

Is it a horrible idea to use the ICC profile name that is in the file-header (assuming we could ever get that right?) to do the mapping? I'm sure the adobe products are at least trying to write that out correctly (its a shame Nuke isnt).

Sam.



On Thu, Oct 2, 2014 at 10:16 AM, <mike...@...> wrote:
On Wednesday, October 1, 2014 2:23:56 PM UTC-7, Mark Boorer wrote:

If you feel like knocking up a pull request containing your patch, I'll merge it (assuming it's all good). Otherwise I'm happy to do so on your behalf.


Thanks Mark.  If you wouldn't mind handling the pull request, that'd be helpful.  I'm afraid I'm still not fully up to speed on git.

-miker

--
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+u...@....
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+u...@....
For more options, visit https://groups.google.com/d/optout.

Join {ocio-dev@lists.aswf.io to automatically receive all group messages.