[Nuke-users] Switch title_color of a node through drop down menu
Hello Nukers, I'm trying to find a way to change the color of a node (title_color) which would be driven by cascading pulldown choice menu. For example, if the first item is chosen, the node would be yellow and if the second one is chosen, it would turn blue. I found this thread in the mailing list archive but I can't figure out where to paste that code... https://www.mail-archive.com/nuke-users@support.thefoundry.co.uk/msg03405.html I'm very new to python so please give a lot of details. Thanks! -- Bruno-Pierre Jobin ___ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
Re: [Nuke-users] Switch title_color of a node through drop down menu
hello,
you can add an expression to you the knobChanged of your node, like:
set cut_paste_input [stack 0]
version 7.0 v5
push $cut_paste_input
NoOp {
name NoOp1
knobChanged
\nn=nuke.thisNode()\ntc=n\['tile_color']\nk=n\['color'].getValue()\nenumColor
= \[ \[1, 0, 0] ,\[0, 1, 0] ,\[0, 0, 1] ,\[1, 1, 0] ]\nr =
enumColor\[int(k)]\[0]\ng = enumColor\[int(k)]\[1]\nb =
enumColor\[int(k)]\[2]\nhexColour = int('%02x%02x%02x%02x' %
(r*255,g*255,b*255,1),16)\ntc.setValue(hexColour)\n
tile_color 0xff01
selected true
xpos -262
ypos -214
addUserKnob {20 User}
addUserKnob {4 color M {red green blue yellow }}
}
Hope this help!
Olivier
2014-03-15 15:37 GMT-04:00 Bruno-Pierre Jobin bpjo...@gmail.com:
Hello Nukers,
I'm trying to find a way to change the color of a node (title_color) which
would be driven by cascading pulldown choice menu. For example, if the
first item is chosen, the node would be yellow and if the second one is
chosen, it would turn blue.
I found this thread in the mailing list archive but I can't figure out
where to paste that code...
https://www.mail-archive.com/nuke-users@support.thefoundry.co.uk/msg03405.html
I'm very new to python so please give a lot of details.
Thanks!
--
Bruno-Pierre Jobin
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
Re: [Nuke-users] Switch title_color of a node through drop down menu
Here is something to get you started: http://pastebin.com/2SbLf5PH This adds a callback for nodes of class "NoOp", which you will have to change to react to your gizmo class or whatever other node you want this to work with. Have a look and see if it makes sense. Cheers, frank On 3/16/14, 8:37 AM, Bruno-Pierre Jobin wrote: Hello Nukers, I'm trying to find a way to change the color of a node (title_color) which would be driven by cascading pulldown choice menu. For example, if the first item is chosen, the node would be yellow and if the second one is chosen, it would turn blue. I found this thread in the mailing list archive but I can't figure out where to paste that code... https://www.mail-archive.com/nuke-users@support.thefoundry.co.uk/msg03405.html I'm very new to python so please give a lot of details. Thanks! -- Bruno-Pierre Jobin ___ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users -- vfx compositing | workflow customisation and consulting ___ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
Re: [Nuke-users] Switch title_color of a node through drop down menu
Awesome! Thanks guys I'll have a look at this! On Sat, Mar 15, 2014 at 5:03 PM, Frank Rueter|OHUfx fr...@ohufx.com wrote: Here is something to get you started: http://pastebin.com/2SbLf5PH This adds a callback for nodes of class NoOp, which you will have to change to react to your gizmo class or whatever other node you want this to work with. Have a look and see if it makes sense. Cheers, frank On 3/16/14, 8:37 AM, Bruno-Pierre Jobin wrote: Hello Nukers, I'm trying to find a way to change the color of a node (title_color) which would be driven by cascading pulldown choice menu. For example, if the first item is chosen, the node would be yellow and if the second one is chosen, it would turn blue. I found this thread in the mailing list archive but I can't figure out where to paste that code... https://www.mail-archive.com/nuke-users@support.thefoundry.co.uk/msg03405.html I'm very new to python so please give a lot of details. Thanks! -- Bruno-Pierre Jobin ___ Nuke-users mailing listnuke-us...@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users -- [image: ohufxLogo 50x50] http://www.ohufx.com *vfx compositing http://ohufx.com/index.php/vfx-compositing | workflow customisation and consulting http://ohufx.com/index.php/vfx-customising * ___ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users -- Bruno-Pierre Jobin www.bpjobin.com inline: ohufxLogo_50x50.png___ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
Re: [Nuke-users] Switch title_color of a node through drop down menu
It is also worth mentioning that knobChanged callback code can be specified in the menu.py file, applying to an entire node class, or knobChanged code can be stored and run in specific nodes only.To store knobChanged code in a specific node, you can store the code to a special hidden knob called "knobChanged". This code will the be executed anytime you change anything on the node.For example, if you have a noOp node with a dropdown menu specifying colors, like this:NoOp {name NodeColoraddUserKnob {20 NodeColor}addUserKnob {4 node_color t "Set Node Color" M {red green blue yellow}}}And you write some code to change the color of the node depending on the dropdown value, you can set the value of the knobChanged knob on that node if you select the node and execute this code:http://pastebin.com/mCPm5HkZBe careful with knobChanged knobs in nodes though. This code is executed constantly, so be very careful to put most of your code in conditionals with the relevant knob name, and keep it simple. Otherwise your scripts can really grind to a halt!Hope that helps!
On Saturday, 2014-03-15 at 2:12p, Bruno-Pierre Jobin wrote:
Awesome! Thanks guys I'll have a look at this!On Sat, Mar 15, 2014 at 5:03 PM, Frank Rueter|OHUfx fr...@ohufx.com wrote:
Here is something to get you
started:
http://pastebin.com/2SbLf5PH
This adds a callback for
nodes of class "NoOp", which you will have to change to react to
your gizmo class or whatever other node you want this to work
with.
Have a look and see if it makes sense.
Cheers,
frank
On 3/16/14, 8:37 AM, Bruno-Pierre Jobin
wrote:
Hello Nukers,
I'm trying to find a way to change the color of a
node (title_color) which would be driven by cascading pulldown
choice menu. For example, if the first item is chosen, the
node would be yellow and if the second one is chosen, it would
turn blue.
I found this thread in the mailing list archive
but I can't figure out where to paste that code...
https://www.mail-archive.com/nuke-users@support.thefoundry.co.uk/msg03405.html
I'm very new to python so please give a lot of details.
Thanks!
--
Bruno-Pierre Jobin
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
--
vfx
compositing | workflow
customisation and consulting
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
-- Bruno-Pierre Jobinwww.bpjobin.com
___Nuke-users mailing listNuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
Re: [Nuke-users] Switch title_color of a node through drop down menu
indeed. that is the difference between Oliver's and my replies.
This code is executed constantly, so be very careful to put
most of your code in conditionals with the relevant knob name, and
keep it simple. Otherwise your scripts can really grind to a
halt!
Yup, which is why I always try to do the conditional statements at
the very top and try to bail out at the first possible moment.
You definitely want to be extra diligent with your code's efficiency
if used as a global callback.
On 3/16/14, 10:52 AM, Jed Smith wrote:
It is also worth mentioning that knobChanged callback code
can be specified in the menu.py file, applying to an entire
node class, or knobChanged code can be stored and run in
specific nodes only.
To store knobChanged code in a specific node, you can store
the code to a special hidden knob called "knobChanged". This
code will the be executed anytime you change anything on the
node.
For example, if you have a noOp node with a dropdown menu
specifying colors, like this:
NoOp {
name NodeColor
addUserKnob {20 NodeColor}
addUserKnob {4 node_color t "Set Node Color" M {red green
blue yellow}}
}
And you write some code to change the color of the node
depending on the dropdown value, you can set the value of the
knobChanged knob on that node if you select the node and
execute this code:
http://pastebin.com/mCPm5HkZ
Be careful with knobChanged knobs in nodes though. This
code is executed constantly, so be very careful to put most of
your code in conditionals with the relevant knob name, and
keep it simple. Otherwise your scripts can really grind to a
halt!
Hope that helps!
On Saturday, 2014-03-15 at 2:12p,
Bruno-Pierre Jobin wrote:
Awesome! Thanks guys I'll have a look at
this!
On Sat, Mar 15, 2014 at 5:03 PM, Frank Rueter|OHUfx
fr...@ohufx.com
wrote:
Here
is something to get you started:
http://pastebin.com/2SbLf5PH
This
adds a callback for nodes of class "NoOp",
which you will have to change to react to your
gizmo class or whatever other node you want
this to work with.
Have a look and see if it makes sense.
Cheers,
frank
On 3/16/14, 8:37 AM, Bruno-Pierre Jobin
wrote:
Hello Nukers,
I'm trying to find a way to
change the color of a node
(title_color) which would be driven
by cascading pulldown choice menu.
For example, if the first item is
chosen, the node would be yellow and
if the second one is chosen, it
would turn blue.
I found this thread in the
mailing list archive but I can't
figure out where to paste that
code...
https://www.mail-archive.com/nuke-users@support.thefoundry.co.uk/msg03405.html
I'm very new to python so please
give a lot of details.
Re: [Nuke-users] Switch title_color of a node through drop down menu
you are right Frank, thanks
it's better to add condition test to the nodeChanged of the node with a
pulldown knod added. In this sample :red, green, blue, yellow
code='''
k=nuke.thisKnob()
if k.name() == 'color':
tc=n['tile_color']
c=k.getValue()
enumColor = [ [1, 0, 0] ,[0, 1, 0] ,[0, 0, 1] ,[1, 1, 0] ]
r = enumColor[int(c)][0]
g = enumColor[int(c)][1]
b = enumColor[int(c)][2]
hexColour = int('%02x%02x%02x%02x' % (r*255,g*255,b*255,1),16)
tc.setValue(hexColour)
'''
nuke.selectedNode()['knobChanged'].setValue(code)
2014-03-15 18:40 GMT-04:00 Frank Rueter|OHUfx fr...@ohufx.com:
indeed. that is the difference between Oliver's and my replies.
This code is executed constantly, so be very careful to put most of your
code in conditionals with the relevant knob name, and keep it simple.
Otherwise your scripts can really grind to a halt!
Yup, which is why I always try to do the conditional statements at the
very top and try to bail out at the first possible moment.
You definitely want to be extra diligent with your code's efficiency if
used as a global callback.
On 3/16/14, 10:52 AM, Jed Smith wrote:
It is also worth mentioning that knobChanged callback code can be
specified in the menu.py file, applying to an entire node class, or
knobChanged code can be stored and run in specific nodes only.
To store knobChanged code in a specific node, you can store the code to
a special hidden knob called knobChanged. This code will the be executed
anytime you change anything on the node.
For example, if you have a noOp node with a dropdown menu specifying
colors, like this:
NoOp {
name NodeColor
addUserKnob {20 NodeColor}
addUserKnob {4 node_color t Set Node Color M {red green blue yellow}}
}
And you write some code to change the color of the node depending on the
dropdown value, you can set the value of the knobChanged knob on that node
if you select the node and execute this code:
http://pastebin.com/mCPm5HkZ
Be careful with knobChanged knobs in nodes though. This code is executed
constantly, so be very careful to put most of your code in conditionals
with the relevant knob name, and keep it simple. Otherwise your scripts can
really grind to a halt!
Hope that helps!
On Saturday, 2014-03-15 at 2:12p, Bruno-Pierre Jobin wrote:
Awesome! Thanks guys I'll have a look at this!
On Sat, Mar 15, 2014 at 5:03 PM, Frank Rueter|OHUfx fr...@ohufx.comwrote:
Here is something to get you started:
http://pastebin.com/2SbLf5PH
This adds a callback for nodes of class NoOp, which you will have to
change to react to your gizmo class or whatever other node you want this to
work with.
Have a look and see if it makes sense.
Cheers,
frank
On 3/16/14, 8:37 AM, Bruno-Pierre Jobin wrote:
Hello Nukers,
I'm trying to find a way to change the color of a node (title_color)
which would be driven by cascading pulldown choice menu. For example, if
the first item is chosen, the node would be yellow and if the second one is
chosen, it would turn blue.
I found this thread in the mailing list archive but I can't figure out
where to paste that code...
https://www.mail-archive.com/nuke-users@support.thefoundry.co.uk/msg03405.html
I'm very new to python so please give a lot of details.
Thanks!
--
Bruno-Pierre Jobin
___
Nuke-users mailing listnuke-us...@support.thefoundry.co.uk,
http://forums.thefoundry.co.uk/http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
--
[image: ohufxLogo 50x50] http://www.ohufx.com *vfx compositing
http://ohufx.com/index.php/vfx-compositing | workflow customisation and
consulting http://ohufx.com/index.php/vfx-customising *
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
--
Bruno-Pierre Jobin
www.bpjobin.com
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
___
Nuke-users mailing listnuke-us...@support.thefoundry.co.uk,
http://forums.thefoundry.co.uk/http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
--
[image: ohufxLogo 50x50] http://www.ohufx.com *vfx compositing
http://ohufx.com/index.php/vfx-compositing | workflow customisation and
consulting http://ohufx.com/index.php/vfx-customising *
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
inline: image/pnginline: ohufxLogo_50x50.png___
Nuke-users
Re: [Nuke-users] day rates in the UK
In short, being senior is not just about being great, it's about achieving the quality on time and in budget. If you can do that then you may be worth your expectations. I couldn't agree more. It's years of experience that enables people to delivery within the context of a show and problem solve with the right priorities in mind, not just the skill to make something look amazing (regardless of the time and resources it may require). This sort of experience should enable you to keep your value as an artist up. while you may be way more expensive than a junior, you will need way less time to deliver what's required, so the bottom line for the employer is not an increases payroll, but a more efficient delivery schedule. I have had juniors on my team who, despite not being able to do the tricky comps, turned out to be more effective in the grand scheme than some of the seniors. The right combo of experienced seniors/leads and juniors can be quite amazing in terms of efficiency and quality. Unfortunately, companies often do not value experience because it seems expensive on paper, when all they do is compare the hourly/daily rate for juniors and seniors; particularly when those companies are managed by accountant type people that don't understand or want to understand the actual work the company is doing. On 16/03/14 13:20, Howard Jones wrote: Taking this from a different angle. Not every show is uber VFX. Some shows cannot afford that level or even require that level. They still need VFX. Does that mean they can't afford senior compositors? No, if anything it means they cant afford not to hire seniors. Why? Because if budgets are tight, you need to hit the ground running. So hypothetically thinking... I need to hire a senior, not because the work is uber-hard or requires uberVFX. It doesn't (always). It's hard enough, requires consummate keying skills/ problem solving but it's not cutting edge. Too hard for a genuine mid range artist, requires a senior. Now here's the problem. Finding a senior who can tailor their VFX to suit the budget. I dont want cheap crap, I don't need uberVFX, I need good enough and fast. Often I find a lot of time is wasted getting the seniors to work down to the show's expectations and budget. In short too much pixel fucking. However at the end of the day I would still want a senior and pay what is affordable. Just a good senior on a simpler show should be faster, less demanding, than a junior/mid. (If only) I guess there are a range of shops you can go to to fill up your trolley, but if you pay a bit more you expect a better quality. Whether quality translates to good enough and fast or perfect and considered, depends on show budget. However good enough and slow at a premium rate is just a waste. In short, being senior is not just about being great, it's about achieving the quality on time and in budget. If you can do that then you may be worth your expectations. Howard On 15 Mar 2014, at 02:53, Neil Scholes n...@uvfilms.co.uk wrote: Absofrigin-lutley! Very interesting thread, and considering the shear skill set needed and uber high level of expertise required for great vfx creation, the right price can always be negotiated confidently and reasonably. Neil Scholes Sent from my iPad On 14 Mar 2014, at 23:37, adam jones adam@mac.com wrote: well said frank. you have put into word in an elegant way what I try and explain to people all of the time, its a slow road but the more artists that think this way the easier it will become. cheers -adam On 15/03/2014, at 10:20 AM, Frank Rueter|OHUfx fr...@ohufx.com wrote: Either way, most qualified people I know tend to be under paid, and based on my experience, companies will always try to
Re: [Nuke-users] day rates in the UK
Yes, I agree it's not always über vfx, but as you both point out extremely well, experience can be invaluable. I can only speak as someone who has been steadily learning Nuke and Houdini for the past 4 years; and what is obvious to me is that the knowledge to solve problems, and thus be truly effective, is vast and complex. I can clearly see how experience on even a modest budget, is priceless. Neil Sent from my iPad On 16 Mar 2014, at 01:02, Frank Rueter|OHUfx fr...@ohufx.com wrote: In short, being senior is not just about being great, it's about achieving the quality on time and in budget. If you can do that then you may be worth your expectations. I couldn't agree more. It's years of experience that enables people to delivery within the context of a show and problem solve with the right priorities in mind, not just the skill to make something look amazing (regardless of the time and resources it may require). This sort of experience should enable you to keep your value as an artist up. while you may be way more expensive than a junior, you will need way less time to deliver what's required, so the bottom line for the employer is not an increases payroll, but a more efficient delivery schedule. I have had juniors on my team who, despite not being able to do the tricky comps, turned out to be more effective in the grand scheme than some of the seniors. The right combo of experienced seniors/leads and juniors can be quite amazing in terms of efficiency and quality. Unfortunately, companies often do not value experience because it seems expensive on paper, when all they do is compare the hourly/daily rate for juniors and seniors; particularly when those companies are managed by accountant type people that don't understand or want to understand the actual work the company is doing. On 16/03/14 13:20, Howard Jones wrote: Taking this from a different angle. Not every show is uber VFX. Some shows cannot afford that level or even require that level. They still need VFX. Does that mean they can't afford senior compositors? No, if anything it means they cant afford not to hire seniors. Why? Because if budgets are tight, you need to hit the ground running. So hypothetically thinking... I need to hire a senior, not because the work is uber-hard or requires uberVFX. It doesn't (always). It's hard enough, requires consummate keying skills/ problem solving but it's not cutting edge. Too hard for a genuine mid range artist, requires a senior. Now here's the problem. Finding a senior who can tailor their VFX to suit the budget. I dont want cheap crap, I don't need uberVFX, I need good enough and fast. Often I find a lot of time is wasted getting the seniors to work down to the show's expectations and budget. In short too much pixel fucking. However at the end of the day I would still want a senior and pay what is affordable. Just a good senior on a simpler show should be faster, less demanding, than a junior/mid. (If only) I guess there are a range of shops you can go to to fill up your trolley, but if you pay a bit more you expect a better quality. Whether quality translates to good enough and fast or perfect and considered, depends on show budget. However good enough and slow at a premium rate is just a waste. In short, being senior is not just about being great, it's about achieving the quality on time and in budget. If you can do that then you may be worth your expectations. Howard On 15 Mar 2014, at 02:53, Neil Scholes n...@uvfilms.co.uk wrote: Absofrigin-lutley! Very interesting thread, and considering the shear skill set needed and uber high level of expertise required for great vfx creation, the right price can always be negotiated confidently and reasonably. Neil Scholes Sent from my iPad On 14 Mar 2014, at 23:37, adam jones adam@mac.com wrote: well said frank. you have put into word in an elegant way what I try and explain to people all of the time, its a slow road but the more artists that think this way the easier it will become. cheers -adam On 15/03/2014, at 10:20 AM, Frank Rueter|OHUfx fr...@ohufx.com wrote: Either way, most qualified people I know tend to be under paid, and based on my experience, companies will always try to take the piss as the people that negotiate with you often don't have a clue where your skill set fits into their copmany, and what you actually bring to the table - and most don't want to know either. To quote somebody from a local python mailing list: The criteria used for hiring often don't match the culture in the workplace. This can easily be transferred to rates and quality of work, i.e. the rates offered to the artists often don't match the expected performance I have had requests from some of the big facilities basically asking me if I know a junior that could
