|
Re: Building "universal" binaries for MacOS
Hi Robert,
I'm curious... will your changes be rolled into the main OCIO repository? (If not, I should probably make a patch to apply to the main one for the next time we need to update our OCIO
Hi Robert,
I'm curious... will your changes be rolled into the main OCIO repository? (If not, I should probably make a patch to apply to the main one for the next time we need to update our OCIO
|
By
Andrea Mantler <man...@...>
·
#1342
·
|
|
icc profiles not working
Hey guys
Has anyone tried baking out icc profiles recently?
I've been trying to bake one out with variations on the following command:
ociobakelut --format icc --inputspace acesproxy --outputspace
Hey guys
Has anyone tried baking out icc profiles recently?
I've been trying to bake one out with variations on the following command:
ociobakelut --format icc --inputspace acesproxy --outputspace
|
By
Alex Fry <al...@...>
·
#1341
·
|
|
Re: Brew install OCIO breaking under 10.9.3
Ignore this...
It was something broken in my brew..
Ignore this...
It was something broken in my brew..
|
By
Alex Fry <al...@...>
·
#1340
·
|
|
Brew install OCIO breaking under 10.9.3
Hey guys
"brew install opencolorio" is currently failing for me under MacOSX 10.9.3
Was this working a few weeks back?
-Alex
192-168-1-7:~ alex$ brew install opencolorio
==> Downloading
Hey guys
"brew install opencolorio" is currently failing for me under MacOSX 10.9.3
Was this working a few weeks back?
-Alex
192-168-1-7:~ alex$ brew install opencolorio
==> Downloading
|
By
Alex Fry <al...@...>
·
#1339
·
|
|
OpenColorIO COP2 nodes for Houdini as Nuke counterparts
------------------------------------------------------------------------------------
------------------------------------------------------------------------------------
OpenColorIO COP2 nodes for
------------------------------------------------------------------------------------
------------------------------------------------------------------------------------
OpenColorIO COP2 nodes for
|
By
wagen...@...
·
#1338
·
|
|
AllocationVars and Allocation tags problem
Good morning!
I have finally developed that OCIO enabled color selectors feature in Krita (some time ago I asked about reversed Display transformations in this list to make this feature). You can read
Good morning!
I have finally developed that OCIO enabled color selectors feature in Krita (some time ago I asked about reversed Display transformations in this list to make this feature). You can read
|
By
Dmitry Kazakov <dimu...@...>
·
#1337
·
|
|
Re: Using environment variables/context to point to a colorspace
Hi,
Thanks for the ticket.
I could indeed implement a callback for the OCIO colorspace nodes. I already have some code that sets the context variables of the OCIO ColorSpace node. The problem is then
Hi,
Thanks for the ticket.
I could indeed implement a callback for the OCIO colorspace nodes. I already have some code that sets the context variables of the OCIO ColorSpace node. The problem is then
|
By
donat...@...
·
#1336
·
|
|
Re: Problem in CDL implementation
This was discussed a while ago in "[ocio-dev] FileTransform interface changes",
https://groups.google.com/forum/#!searchin/ocio-dev/parameter/ocio-dev/dv9ZC28lq_c/D1QxOPPj__wJ
..and would become a
This was discussed a while ago in "[ocio-dev] FileTransform interface changes",
https://groups.google.com/forum/#!searchin/ocio-dev/parameter/ocio-dev/dv9ZC28lq_c/D1QxOPPj__wJ
..and would become a
|
By
dbr/Ben <dbr....@...>
·
#1335
·
|
|
Re: Yaml related warning message when compiling OCIO
Belated reply, but, those warnings can (hopefully) be ignored if you are just building OCIO
The problem is because "Config::getNumEnvironmentVars" returns an "int", when it should probably return an
Belated reply, but, those warnings can (hopefully) be ignored if you are just building OCIO
The problem is because "Config::getNumEnvironmentVars" returns an "int", when it should probably return an
|
By
dbr/Ben <dbr....@...>
·
#1334
·
|
|
Re: Using environment variables/context to point to a colorspace
Made a ticket about this,
https://github.com/imageworks/OpenColorIO/issues/364
As an alternative, could you do something with Python in Nuke? Maybe a menu item or addOnUserCreate callback which
Made a ticket about this,
https://github.com/imageworks/OpenColorIO/issues/364
As an alternative, could you do something with Python in Nuke? Maybe a menu item or addOnUserCreate callback which
|
By
dbr/Ben <dbr....@...>
·
#1333
·
|
|
Re: Using environment variables/context to point to a colorspace
Unfortunately the current version of OCIO only uses context variables when resolving file paths. Context variables are only used in search paths and the src parameter for a FileTransform.
Unfortunately the current version of OCIO only uses context variables when resolving file paths. Context variables are only used in search paths and the src parameter for a FileTransform.
|
By
Robert Minsk <rmi...@...>
·
#1332
·
|
|
Re: Good Morning!
Looking at the code OCIO implements Matrix*RGBA (column vector). In matrix operations RGBA*transpose(matrix) = matrix*RGBA. If you feel you are getting the wrong multiplication order then try using
Looking at the code OCIO implements Matrix*RGBA (column vector). In matrix operations RGBA*transpose(matrix) = matrix*RGBA. If you feel you are getting the wrong multiplication order then try using
|
By
Robert Minsk <rmi...@...>
·
#1331
·
|
|
Using environment variables/context to point to a colorspace
Hi,
I did post this question to OCIO-users and did not get any reaction, so I'm trying here as it might be a question related to development. Anyway I'm sorry if this is against posting rules.
I've
Hi,
I did post this question to OCIO-users and did not get any reaction, so I'm trying here as it might be a question related to development. Anyway I'm sorry if this is against posting rules.
I've
|
By
do...@...
·
#1330
·
|
|
Good Morning!
My name is Joshua Jackson. I'm writing a custom configuration with ocio and have a quick question:
Can I apply Matrix Transforms in a different order than RGB x MTX x etc... ?
For Chromatic
My name is Joshua Jackson. I'm writing a custom configuration with ocio and have a quick question:
Can I apply Matrix Transforms in a different order than RGB x MTX x etc... ?
For Chromatic
|
By
Joshua Jackson <joshua.a...@...>
·
#1329
·
|
|
No way to retreive "non-active" displays
If I have a config with displays "a", "b", "c" and an active_display list of "a" there is no way to get to displays "b" and "c". In fact reading in a config file and writing it back out will only
If I have a config with displays "a", "b", "c" and an active_display list of "a" there is no way to get to displays "b" and "c". In fact reading in a config file and writing it back out will only
|
By
Robert Minsk <rmi...@...>
·
#1328
·
|
|
Re: Building "universal" binaries for MacOS
Success! Now to make sure I have the same version on linux (in case anything else changed from 1.0.9), then build for Windows (fingers crossed that there's no glitches there!), and I'm ready to start
Success! Now to make sure I have the same version on linux (in case anything else changed from 1.0.9), then build for Windows (fingers crossed that there's no glitches there!), and I'm ready to start
|
By
Andrea Mantler <man...@...>
·
#1327
·
|
|
Re: Building "universal" binaries for MacOS
Thanks!
By
Andrea Mantler <man...@...>
·
#1326
·
|
|
Re: Building "universal" binaries for MacOS
If you do another pull the cmake file should use the internal lcms by default.
If you do another pull the cmake file should use the internal lcms by default.
|
By
rmi...@...
·
#1325
·
|
|
Re: Building "universal" binaries for MacOS
Yeah, I'm working at getting a universal version compiled now. Thanks!
Yeah, I'm working at getting a universal version compiled now. Thanks!
|
By
Andrea Mantler <man...@...>
·
#1324
·
|
|
Re: Building "universal" binaries for MacOS
> ld: warning: in /opt/local/lib/liblcms2.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
Your liblcms2 is not a universal library. I guess it came
> ld: warning: in /opt/local/lib/liblcms2.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
Your liblcms2 is not a universal library. I guess it came
|
By
rmi...@...
·
#1323
·
|