Thanks Larry!

And I've merged this PR into master now, so hopefully this will be fixed. -- lg -- Larry Gritz lg@...

Reminder: OSL TSC meeting ( every other week ) When: 09/16/2021 2:00pm to 3:00pm (UTC-07:00) America/Los Angeles Where: https://zoom.us/j/100511909 Organizer: Chris Kulla ckulla@... View

Hi, I've been able to make it work by changing the prototype of the osl_get_attribute callback and passing the TypeDesc casted into a long long instead of passing its address. This is exactly what is

Open Shading Language discussion list Upcoming Events OSL TSC meeting ( every other week ) When: Thursday, September 16, 2021, 2:00pm to 3:00pm (GMT-07:00) America/Los

Reminder: OSL TSC meeting ( every other week ) When: 09/16/2021 2:00pm to 3:00pm (UTC-07:00) America/Los Angeles Where: https://zoom.us/j/100511909 Organizer: Chris Kulla ckulla@... View

I found a solution by using the ASWF CI build image for OSL. Refer here for details.

Hi, OCIOv2 now generates an OSL shader program. But I face some irritating syntax changes to accommodate OSL when generating the shader code. To simplify the generation of the code, I would like to

Hi, For the OCIOv2 project, I developed a unit test framework to compile and excecute an OSL shader code. And, I now need to run the OSL unit tests on a Linux platform (I did all my tests on macOS

Open Shading Language discussion list Upcoming Events OSL TSC meeting ( every other week ) When: Thursday, September 16, 2021, 2:00pm to 3:00pm (GMT-07:00) America/Los

Following the discussion during the TSC meeting, the add of some color mgt in the texture() method is a challenging topic (compare to adding color mgt in transformc()) even if the API change could be

I'm not "justifying" necessarily, I'm just explaining how things came to be in this state. From the beginning, OSL needed OIIO for its image handling, the TextureSystem, and also a lot of great

OSL TSC meeting ( every other week ) When: 09/02/2021 2:00pm to 3:00pm (UTC-07:00) America/Los Angeles Where: https://zoom.us/j/100511909 Organizer: Chris Kulla ckulla@... View

Reminder: OSL TSC meeting ( every other week ) When: 09/02/2021 2:00pm to 3:00pm (UTC-07:00) America/Los Angeles Where: https://zoom.us/j/100511909 Organizer: Chris Kulla ckulla@... View

Reminder: OSL TSC meeting ( every other week ) When: 09/02/2021 2:00pm to 3:00pm (UTC-07:00) America/Los Angeles Where: https://zoom.us/j/100511909 Organizer: Chris Kulla ckulla@... View

Hi, We are currently trying to make getattribute() calls work on GPU with OptiX 7.3 and OSL 1.11.9.0 but we are facing an issue. We've implemented the osl_get_attribute() callback in cuda and it's

Happy monthly release day! We have tagged "v1.11.15.0" and moved the "release" branch marker to that position. This is the latest supported production release of OSL. It guarantees API, ABI, and link

Yes, and also there is a branch called "release" that at all times points to the latest supported release. (We move the branch marker whenever we tag releases.) Yes, exactly. From the point of view of

Thanks for the fast answers. Does the tag 'v1.11.14.2' represent the last official version? What about the input parameter which is also a color4 ? Should I have two input parameters (like for the

Hi, The post is not a question but a comment on the current implementation in OSL of the color mgt support. I faced a problem when developing the OSL unit test framework for OCIO, and I want to share