Personally I would try to deal with that using a callback restrict to the Read 
class. I believe it would be simpler to do, and would encompass a broader range 
of circumstances while creating Read nodes inside Nuke.


On 15/12/2011, at 20:41, Paul Hudson <[email protected]> wrote:

> I asked the same things a while back.  There's a thread called "set default 
> colorspace by extension" if you want to search.
> 
> Essentially it boils down to overriding dropData and create_read().
> 
> 
> To override create_read():
> Define my_create_read() in your init.py
> 
> and then override the default create_read() like so:
> nukescripts.create_read = my_create_read
> 
> 
> 
> -Paul
> 
> 
> On Thu, Dec 15, 2011 at 11:38 AM, Nick Guth <[email protected]> wrote:
> Is there a way to have the colorspace of the read node be set per file type? 
> For example, every dpx would come in as srgb, exr's as linear, etc. I used to 
> have everything set to srgb in my menu.py, but now some of our shows are 
> coming in linear exrs and it's just an extra "uh oh" step if someone didn't 
> remember to set it properly.
> 
> Thanks!
> 
> -- 
> Nick
> 
> _______________________________________________
> Nuke-users mailing list
> [email protected], http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
> 
> _______________________________________________
> Nuke-users mailing list
> [email protected], http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Reply via email to