|
Re: Is the const type qualifier only in CG?
hmmm tried to do that last night, but something went left of field. I now have a branch thats up to date with imageworks/master but the commits are in the future.. doesn't really matter as I'm hoping
hmmm tried to do that last night, but something went left of field. I now have a branch thats up to date with imageworks/master but the commits are in the future.. doesn't really matter as I'm hoping
|
By
Malcolm Humphreys <malcolmh...@...>
·
#383
·
|
|
Re: Is the const type qualifier only in CG?
That's no problem at all.
FYI, this really easy to solve with the 'rebase' command. Say you
have a branch and you want to incorporate all changes on spi/master.
(I've already setup the spi remote,
That's no problem at all.
FYI, this really easy to solve with the 'rebase' command. Say you
have a branch and you want to incorporate all changes on spi/master.
(I've already setup the spi remote,
|
By
Jeremy Selan <jeremy...@...>
·
#378
·
|
|
Re: Is the const type qualifier only in CG?
Whoops, I should live by that mantra 'update or die'. I have a few
too many different checkouts of ocio, still a bit in svn land, goto to
get used to using local git branches.
This fixed this issue
Whoops, I should live by that mantra 'update or die'. I have a few
too many different checkouts of ocio, still a bit in svn land, goto to
get used to using local git branches.
This fixed this issue
|
By
Malcolm Humphreys <malcolmh...@...>
·
#380
·
|
|
Re: Is the const type qualifier only in CG?
Yes, if you look att Processor.cpp : 381, you'll see that on apple
platforms we always insert a sampling of the tex2 even if it's not
needed. It appeared that without this, if the 3dlut was unused
Yes, if you look att Processor.cpp : 381, you'll see that on apple
platforms we always insert a sampling of the tex2 even if it's not
needed. It appeared that without this, if the 3dlut was unused
|
By
Jeremy Selan <jeremy...@...>
·
#374
·
|
|
Re: Is the const type qualifier only in CG?
I already fixed this too; thought it was checked in last week. hold
for details.
-- Jeremy
<malcolmh...@...> wrote:
I already fixed this too; thought it was checked in last week. hold
for details.
-- Jeremy
<malcolmh...@...> wrote:
|
By
Jeremy Selan <jeremy...@...>
·
#373
·
|
|
Re: Is the const type qualifier only in CG?
I'm having an unrelated problem when using a noop processor eg. scene_linear -> data on the gpu.
I'm getting a EXC_BAD_ACCESS when issuing glBegin(GL_QUADS). Having another shader for this case which
I'm having an unrelated problem when using a noop processor eg. scene_linear -> data on the gpu.
I'm getting a EXC_BAD_ACCESS when issuing glBegin(GL_QUADS). Having another shader for this case which
|
By
Malcolm Humphreys <malcolmh...@...>
·
#379
·
|
|
Re: Is the const type qualifier only in CG?
No problem! Let me know if you have any troubles with the updated version.
I should also probably update the ociodisplay program to query the
glsl version, and select the best profile
No problem! Let me know if you have any troubles with the updated version.
I should also probably update the ociodisplay program to query the
glsl version, and select the best profile
|
By
Jeremy Selan <jeremy...@...>
·
#371
·
|
|
Re: Review: Building/config related docs
Committed.
Thanks!
-- Jeremy
<malcolmh...@...> wrote:
Committed.
Thanks!
-- Jeremy
<malcolmh...@...> wrote:
|
By
Jeremy Selan <jeremy...@...>
·
#370
·
|
|
Re: Is the const type qualifier only in CG?
Oh snap, you have already fixed this. I haven't updated for a few days.
Sorry for the list noise.
.malcolm
Oh snap, you have already fixed this. I haven't updated for a few days.
Sorry for the list noise.
.malcolm
|
By
Malcolm Humphreys <malcolmh...@...>
·
#377
·
|
|
Re: Is the const type qualifier only in CG?
Those who are having trouble with GLSL, are you on the most recent
version of OCIO?
I made a commit last week (which is in version 0.7.5), where on OSX
the const keyword would be omitted for GLSL 1.0
Those who are having trouble with GLSL, are you on the most recent
version of OCIO?
I made a commit last week (which is in version 0.7.5), where on OSX
the const keyword would be omitted for GLSL 1.0
|
By
Jeremy Selan <jeremy...@...>
·
#369
·
|
|
Re: Is the const type qualifier only in CG?
Hi Mark,
Thanks for the reply, well that makes sense why it hasn't really been an issue till now.
How would you recommend to solve these types of issues? I can see two obvious ways. if/then blocks
Hi Mark,
Thanks for the reply, well that makes sense why it hasn't really been an issue till now.
How would you recommend to solve these types of issues? I can see two obvious ways. if/then blocks
|
By
Malcolm Humphreys <malcolmh...@...>
·
#376
·
|
|
Re: Is the const type qualifier only in CG?
There is a const qualifier in GLSL, and it should work on other
platforms without issue. The difference may be that OSX only supports
GLSL 1.20 currently, which is far behind most of NVidia's and
There is a const qualifier in GLSL, and it should work on other
platforms without issue. The difference may be that OSX only supports
GLSL 1.20 currently, which is far behind most of NVidia's and
|
By
Mark Alexander <malex...@...>
·
#368
·
|
|
Is the const type qualifier only in CG?
Is the 'const' qualifier in glsl? I have to change the following to get the glsl shader to compile on OSX.
I'm cool to add another if glsl or cg block, just wondering if this could be something
Is the 'const' qualifier in glsl? I have to change the following to get the glsl shader to compile on OSX.
I'm cool to add another if glsl or cg block, just wondering if this could be something
|
By
Malcolm Humphreys <malcolmh...@...>
·
#375
·
|
|
Review: Replaced config->getRoleNameByIndex
When building some UI menus, I wanted to get a list of defined roles. Config::getRoleNameByIndex() only returned the resolved colorspace name.
--snip--
Replaced config->getRoleNameByIndex (which
When building some UI menus, I wanted to get a list of defined roles. Config::getRoleNameByIndex() only returned the resolved colorspace name.
--snip--
Replaced config->getRoleNameByIndex (which
|
By
Malcolm Humphreys <malcolmh...@...>
·
#372
·
|
|
Re: Review: Building/config related docs
LGTM
LGTM
This is a good fix till we add boost/shared_ptr.hpp to ocio or replace it with tr1/memory in OpenColorTypes.h. Right now you need boost on linux to build.
.malcolm
+1
.malcolm
LGTM
LGTM
This is a good fix till we add boost/shared_ptr.hpp to ocio or replace it with tr1/memory in OpenColorTypes.h. Right now you need boost on linux to build.
.malcolm
+1
.malcolm
|
By
Malcolm Humphreys <malcolmh...@...>
·
#367
·
|
|
Context/per-shot grades
If I understand correctly, the Context allows you to set a search path including env-variables (e.g $SEQ/$SHOT), so you can define a FileTransform, and it'll look in the shot's directory before the
If I understand correctly, the Context allows you to set a search path including env-variables (e.g $SEQ/$SHOT), so you can define a FileTransform, and it'll look in the shot's directory before the
|
By
"dbr/Ben" <b...@...>
·
#366
·
|
|
Re: Review: Building/config related docs
Oh, good point - I forgot PYTHONPATH also. Mentioned both of these, and few other minor changes:
https://github.com/dbr/OpenColorIO/commit/573356952ca30f90b3cb4aafa925b33cbf974f99
Also a
Oh, good point - I forgot PYTHONPATH also. Mentioned both of these, and few other minor changes:
https://github.com/dbr/OpenColorIO/commit/573356952ca30f90b3cb4aafa925b33cbf974f99
Also a
|
By
"dbr/Ben" <b...@...>
·
#365
·
|
|
Re: Review: Building/config related docs
rock and roll these docs are great.
The only thing I can see is missing is a section on NUKE_PATH in the environment section.
.malcolm
rock and roll these docs are great.
The only thing I can see is missing is a section on NUKE_PATH in the environment section.
.malcolm
|
By
Malcolm Humphreys <malcolmh...@...>
·
#364
·
|
|
0.7.5 Released
**Version 0.7.5 (Jan 13 2011):**
* ociodisplay enhancements
* gpu display bugfix (glsl profile 1.0 only)
* Makefile enhancements
* Nuke installation cleanup
* Doc generation using
**Version 0.7.5 (Jan 13 2011):**
* ociodisplay enhancements
* gpu display bugfix (glsl profile 1.0 only)
* Makefile enhancements
* Nuke installation cleanup
* Doc generation using
|
By
Jeremy Selan <jeremy...@...>
·
#358
·
|
|
Re: Review: Building/config related docs
This makes sense as you get to release. The code gets the most frequent updates and the webpage represents the current used version.
This makes sense as you get to release. The code gets the most frequent updates and the webpage represents the current used version.
|
By
Joseph Slomka <jsl...@...>
·
#357
·
|