Thank you Frank! it works fine!
2011/10/6 Frank Rueter fr...@beingfrank.info
b = nuke.nodes.Blur()
k = nuke.Double_Knob( 'test', 'test')
b.addKnob(k)
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
Hallo everyone,
please note that we decided to release the source code of the script. We
received some emails and realized that it was impossible for us to improve the
script that it suits all need.s So if you visit the blog
www.compflows.blogspot.com. you will now find the source code.
We
Hey everyone,
i am having this weird issue, never saw it before.
I keyed some footage and using a checkerboard on the the BG input of my
primatte node, the pulled key looks excellent.
When i render (Write) it to disk and then use a merge node with a checkerboard
i have black in my edges (and
maybe check your read node - have youi got a colourspace change with premult on
(or off)?
I assume you're reading it back in but its unclear from your mail
H
From: Giso Spijkerman h...@gisospijkerman.nl
To: nuke-users@support.thefoundry.co.uk
Sent: Thursday, 6
hey Howard,
Yeah, i am reading it back in.
My write node and read node are pretty much the same. Just Linear Workspace
with premultipliying set to off.
The write node is exporting it to an 16bit float - 1 scanline Zip EXR and the
Read node is just reading a lineair file.
i am now trying if
Hey
Anyone experienced a bug while setting keyframes ? Often, when I set a
keyframe at let say frame 10, nuke will put a unwanted keyframe at frame
11. Happens alot with the roto node but I just noticed that it happens
with the cornerpin too.
--
Hugo Léveillé
TD Compositing, Vision
Just noticed that I had a F_Motion in the tree. If I remove it it seems
to fix the problem
On Thursday, October 06, 2011 7:12 AM, Hugo Léveillé
hu...@fastmail.net wrote:
Hey
Anyone experienced a bug while setting keyframes ? Often, when I set a
keyframe at let say frame 10, nuke will put a
Yep.. I have had the same problem.. only with V6.3.
On Thu, Oct 6, 2011 at 12:12 PM, Hugo Léveillé hu...@fastmail.net wrote:
Hey
Anyone experienced a bug while setting keyframes ? Often, when I set a
keyframe at let say frame 10, nuke will put a unwanted keyframe at frame
11. Happens alot
I have to agree with this. If you have the systems in place to manage file
deployment and synchronization across many machines, this kind of thing is
incredibly easy to solve (push out some startup scripts to set up an
environment, alter config files, etc.) If not, well... hindsight is 20/20. I
Hi John,
If you haven't done so already, could you please send this to
supp...@thefoundry.co.uk
Do you only have one keyframe set for the shape when seeing this?
Thanks,
Mark
On 06/10/2011 16:02, John Vanderbeck wrote:
We are having a strange problem here, and I'm wondering if anyone
I am trying to create a shuffleCopy node using python and set the out2 to new
layer but nuke doesn't let me do it, any advice on this?
Example:
if I pass a parameter here doesn't work:
nuke.nodes.ShuffleCopy()
and like this neither,
n = nuke.nodes.ShuffleCopy()
n.knob['out2'].setValue('new')
It was with only a single keyframe. I just tried it with two and it
works as expected, so the problem only occurs if you have 0 or 1
keyframes. This is different behavior from 6.2, and presumably a bug?
I'll get it submitted.
From: nuke-users-boun...@support.thefoundry.co.uk
There are a couple issues here. First of all, the layer you want to use needs
to exist before you can set the ShuffleCopy node to use it; you can’t set the
out knob to 'new,' since that’s not actually a layer. If you know what your
layer needs to be, you’ll need to add it via a Python or TCL
I'm seeing it here too
Howard
From: John Vanderbeck john.vanderb...@in-three.com
To: Nuke user discussion nuke-users@support.thefoundry.co.uk
Sent: Thursday, 6 October 2011, 19:55
Subject: RE: [Nuke-users] No feather points in 6.3 curve editor?
No feather
Right, thanks Diogo. I forgot to mention createNode...
-Nathan
From: Diogo Girondi
Sent: Thursday, October 06, 2011 5:22 PM
To: Nuke user discussion
Subject: Re: [Nuke-users] nuke python - ShuffleCopy
I believe he could also do:
nuke.createNode(Shuffle, in rgb red red green green blue
Yeah, we use RV to and I've already implemented the LUTs pulldown. Although
I can't figure out how to force No Conversion when RV opens. The Alexa's
auto default to DPX/Cineon.
Thoughts?!
Yeah, I'm feeling the same as you on FC too Nathan, although having that as
a secondary is nice and it
Thanks Wouter. Will do.
From: nuke-users-boun...@support.thefoundry.co.uk
[nuke-users-boun...@support.thefoundry.co.uk] on behalf of Wouter Klouwen
[wou...@thefoundry.co.uk]
Sent: Thursday, October 06, 2011 7:11 PM
To: nuke-users@support.thefoundry.co.uk
Initially, we were maintaining a customized version of rvui.mu that made any
base tweaks to the interface, settings, etc. that we needed, but this proved to
be a huge pain, since that file often changes between minor RV releases
(breaking everything).
Since then, I’ve switched to implementing
18 matches
Mail list logo
