Hi Hugo
First off, thanks for the code. It doesn't seem to be working for me but maybe
it will after you get a chance to play with it.
Out of curiosity, how hard would it be to parse, say, a resolution directory
and change it to the proxy res? Would this be best done with TCL or Python?
eg.:
/pfcluster/Alphaville/PRODUCTION/01_joyluck/RENDERS/3D_ELEMENTS/joyluck_lightTex_v019_ln/LaserGlow/4096x3112/joyluck_lightTex_v019_ln_LaserGlow.####.exr
^ ^ ^
would become
/pfcluster/Alphaville/PRODUCTION/01_joyluck/RENDERS/3D_ELEMENTS/joyluck_lightTex_v019_ln/LaserGlow/1024x778/joyluck_lightTex_v019_ln_LaserGlow.####.exr
^ ^ ^
But my real question is: everybody has to do this with shots they're using
proxies for? That seems really nuts to me. I can't imagine everyone has
automatic scripts to do this sort of thing.
Here's to it
Bill
On Mar 31, 2012, at 6:29 PM, Hugo Leveille wrote:
> On a phone right now so the syntax is probably wrong, but if you want to set
> the proxy format to the same as the root format, you could do it in the
> onUserCreate callback
>
> Something like:
>
> def setProxy():
>
> n = nuke.thisNode()
> n['proxy_format'].setValue(n['format'].value()']
> n['file'].setValue(n['proxy'].value()']
>
> nuke.addOnUserCreate(setProxy,nodeClass = 'Read')
>
> Like I said on a phone so probably a few typo here and there, but this would
> set the proxy formar to the same as the file and set the same path ( just do
> a replace string function to set it to your proxy
>
> Sent from my iPhone
>
> On 2012-03-31, at 7:16 PM, "Bill Gilman" <[email protected]> wrote:
>
>> Sorry, my question wasn't very clear.
>>
>> I'm finding that when I bring an element into nuke, the "proxy" path field
>> has to be set by hand, along with the proxy format for that node. Would
>> love to have a way to have it automatically set itself with default values
>> and/or a slight modification (using something like [value root.resFolder] or
>> similar.
>>
>> Thanks for the code below, although I'm finding that if I change the name of
>> the proxy format from "myProxy" to "dcProxy" it fails when I try to start
>> nuke. Switching it back makes it work again. Strange behavior, seems to
>> me...
>>
>>
>> On Mar 30, 2012, at 12:28 PM, Dan Walker wrote:
>>
>>> You could put it in your global init.py or menu.py (not on the application
>>> level). Each time Nuke is executed, what you see below will be autoset.
>>>
>>> nuke.root()['proxy'].setValue(1) ###### enables proxy mode
>>>
>>> nuke.root()['proxy_type'].setValue(0) ###### sets proxy type 0 = format, 1
>>> = scale
>>>
>>> myProxy = nuke.addFormat("1920 1080 1.0 myProxy") ###### create a custom
>>> proxy format spec
>>>
>>> nuke.root()['proxy_format'].setValue(myProxy) ######set your custom proxy
>>> format spec
>>>
>>>
>>>
>>> -Dan
>>>
>>>
>>> On Fri, Mar 30, 2012 at 10:26 AM, Bill Gilman <[email protected]> wrote:
>>> Is there a way to set the proxy format globally, instead of having to do it
>>> node by node?_______________________________________________
>>> 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
> _______________________________________________
> 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
