Re: [Nuke-users] linking expression to pulldown choice

Turn it into a value: [value WIPECONTROL.wipe_duration] jrab > On Mar 12, 2017, at 10:48 PM, Darren Coombes wrote: > > say i have a pulldown choice menu, and i have each line in the pulldown as a > number, depicting amount of frames. > > 06 > 12 > 18 > 40 > 60 > >

Re: [Nuke-users] .tmp files left behind

As an aside, we are writing our frames to a temp locally, then copying them. One of our td's ran quite a few tests and determined that the network load was significantly higher (and ultimately slower) with network only renders. Rendering locally and then a cp /tmp/finishedframe ->

Re: [Nuke-users] The forums are moving

Hey all - does it really matter if: we get the email we reply to the email and everyone gets it. the 'community' gets the email if you reply online in the 'community' you get the email. sort of like the list with the benefit of the online 'community' and the list being able to talk to each

Re: [Nuke-users] The forums are moving

in the first place. The forum doesn't just email me through some AI that knows what it thinks I want to read. On Feb 4, 2015 2:39 PM, John RA Benson j...@illum-mg.fr mailto:j...@illum-mg.fr wrote: Hey all - does it really matter if: we get the email we reply to the email and everyone gets

[Nuke-users] Re: [Nuke-python] Writing IPTC photometadata

you could try using exiftool in an afterFrameRender callback: http://www.sno.phy.queensu.ca/~phil/exiftool/ jrab On 03/31/2014 09:47 PM, Richard Bobo wrote: Hi all, Has anyone had to write IPTC metadata in their PNG output

[Nuke-users] Exporting AE to nuke

Hi Simon - I'm glad you mis-read the original post ;) We've got a project where it's all done in AE but now need to rebuild in nuke - if you've got anything you can pass on, it would be really helpful. Cheers - JRAB On Jan 23, 2014, at 9:35 AM, Simon Björk bjork.si...@gmail.com wrote:

[Nuke-users] AE to Nuke script conversions?

Hey there - We have a 2d animation project that was done in After Effects by a third party company. We need to take it and add particles and turn it into a stereo comp in nuke, so our in house artists can make it work with the tools we usually work with and really plus it out over time.

Re: [Nuke-users] Nuke takes *forever* to unload memory (Windows 7)

There was a bug in 6.2v3 that had to do with dependencies, so deleting dependencies upstream of a node in a large tree went into a loop that was pretty time consuming to delete. I wonder if this came back in some form? I used this code to test: def deleteUpstreamNodes(node):

Re: [Nuke-users] Droste infinite zoom in Nuke

Awesome! jrab On Aug 9, 2013, at 5:10 PM, Francois Lord li...@francoislord.com wrote: I did it in Shake, with an absurdly long expression in two separate warpX nodes. As I remember it, the first node warped in log and the second one reverted it back. So inbetween the two nodes, I could

Re: [Nuke-users] FFMPEG and Tiffs

what was the command line you were using? offhand, I'd say ffmpeg isn't reading a float tiff, or a compression setting, if that's the case. I know it doesn't have a problem with 16 bit uncompressed. It won't care about the colorspace, unless you specify something. jrab On Jun 8, 2013, at

Re: [Nuke-users] EXR file size Mantra vs Nuke re-render

even though the mantra render may have been specified to be 16 bit, maybe there is a channel or 2 in the header that is 32? I've seen some strange file size issues and after checking with exrheader discovered that the Z was in 32 bit. Even nuke's autocrop wouldn't shrink a file as much as

Re: [Nuke-users] Copy/Paste is causing Nuke to crash

any internal gizmos in the copy? There was an bug that I think was fixed in 6.3v4 that caused a mega loop onCreate inside a gizmo we had. If the copy/paste freeze isn't happening with Nuke nodes but does with a custom gizmo (eliminating the randomness) there could be a

Re: [Nuke-users] Tiff metadata / tags

Yes, these are all pretty clever ideas! As for the logs, uh, no. Succesfully completing jobs don't leave a trail, unless you ask to keep the log before rendering. At least that's for logs I can get at. So that frame that took an hour still rendered successfully

Re: [Nuke-users] Tiff metadata / tags

while i appreciate everone's help, you pegged it: your response is sort of inappropriate and semi-arrogant. This thread concerns accessing a basic function that I figured nuke was capable of: metadata/tagging in a tiff format. the reasons are really

[Nuke-users] Tiff metadata / tags

Hey out there - Does anyone know of a way to embed certain tiff tags into a (tiff) render? A ModifyMetaData node doesn't seem to do it unless there is a magic key I don't know of. We are rendering tiffs and having some odd render issues. I'm hoping by adding TIFFTAG_HOSTCOMPUTER

Re: [Nuke-users] Tiff metadata / tags

arbitrary TIFF metadata, but a simple solution (if you've got the time to run test renders) would just be to do a Text node burn-in with [info hostname] as a text expression. -Nathan -Original Message- From: John RA Benson Sent: Tuesday, January 29, 2013 1:08 AM To: Nuke user discussion

Re: [Nuke-users] Tiff metadata / tags

kinds of render issues are you running into exactly? -Nathan -Original Message- From: John RA Benson Sent: Tuesday, January 29, 2013 9:24 AM To: nuke-users@support.thefoundry.co.uk Subject: Re: [Nuke-users] Tiff metadata / tags ha - yes, but that kind of ruins the render ;) the issue pops

Re: [Nuke-users] Question about project format VS centerpoints in Transforms etc

do you really need the project setting format? Wouldn't the gizmos' input format be better? In that case, you already said it: a simple =width/2 and =height/2 in center x and y might be all you need. jrab On 01/04/2013 07:52 PM, � wrote: Hello there, This might be super obvious to the rest

Re: [Nuke-users] making obsolete nodes invisible?

outside of that system for something like this. On Thu, Oct 18, 2012 at 9:25 AM, John RA Benson john.benson.macg...@gmail.com wrote: Hello - is there any good way to make obsolete nodes invisible? Sure, not adding it to the menus hides it a bit, but you can still find it with a tab. We can't remove

[Nuke-users] making obsolete nodes invisible?

Hello - is there any good way to make obsolete nodes invisible? Sure, not adding it to the menus hides it a bit, but you can still find it with a tab. We can't remove them or it will break old scripts. thanks JRAB ___ Nuke-users mailing list

[Nuke-users] general defaults override location?

general question related to the thread concerning default overrides for the write node: will ALL defaults work properly if they go into the menu.py? Even if they are not menu related? I've been setting them in init.py, which was working fine until I tried that with the viewer lut default.

Re: [Nuke-users] Re: ??? redguard1.glow ???

nnel, Nuke will not load anything beyond that line in the .nk script and you'll have an incomplete script in the DAG. erik John RA Benson wrote: This thread finally prompted me to do some sharing - I've fixed a lot of bad layers in scripts with some simple python (well, with regul

Re: [Nuke-users] Re: ??? redguard1.glow ???

are those scripts really just toast? We have been running into it more and more and more lately :(     From: nuke-users-boun...@support.thefoundry.co.uk [mailto:nuke-users-boun...@support.thefoundry.co.uk] On Behalf Of John RA Benson Sent: Thursday, April 12, 2012 7:49 AM To: Nuke user

Re: [Nuke-users] Re: ??? redguard1.glow ???

This thread finally prompted me to do some sharing - I've fixed a lot of bad layers in scripts with some simple python (well, with regular expressions, which are simple but can be confusing). Some of these scripts were recovered from dead because of broken clones or empty {}. The usual...

[Nuke-users] Too many open files

Hey there - Having some strange rendering issues: Very simple script, 3 read nodes (exr's), just a over b for each. Except it's 4488 frames long. After a thousand frames or so, the render fails: OSError: [Errno 24] Too many open files: '/path/to/frames.4249.exr' I'm not sure if this is due

Re: [Nuke-users] Too many open files

did in my experience. Ari Sent from my iPhone On Nov 27, 2011, at 12:10 PM, John RA Benson john.benson.macg...@gmail.com wrote: Hey there - Having some strange rendering issues: Very simple script, 3 read nodes (exr's), just a over b for each. Except it's 4488 frames long. After

Re: [Nuke-users] other channel in vray multichannel EXR

Does nuke really have a bad name handling bug if the layer names aren't written to the exr spec? Seems like it would be a lot better to make the fixes upstream than wait/have nuke do a fix that could end up creating other issues. I'd be curious how other viewers read your layer? I have to

Re: [Nuke-users] Nothing is named pathToMyNukeScript

Actually - Since then, I've found lots of causes and made lots of fixes to scripts that have that problem - usually a busted clone, knobs with {} instead of {{something}}, or a rotoshape bug. In this case however, if that's really the attached script, there's no saving it - it's been lopped

Re: [Nuke-users] recommended Linux

aha - looks like the lib fix we did is normal - but see Peter Pearson's note at the end. jrab On Oct 7, 2011, at 17:32, Hugh Macdonald li...@hughmacdonald.co.uk wrote: For anyone going with Ubuntu, do be aware that the system has some newer libraries that Nuke is shipped with... To get

Re: [Nuke-users] Re: Disappearing nodes on script re-open

with 4 dup scripts, could you be getting a too many open files error also? just curious if it might open completely if you launched from a system that doesn't have network access. I've fixed a few that way. Also check for variable with only {} as the value, but those occur normally also. In any

Re: [Nuke-users] Re: [Nuke-python] enumeration knobs being saved with int instead of txt

. On Thu, 2 Jun 2011 13:07:00 +0200, John RA Benson john.benson.macg...@gmail.com wrote: Has anyone had the problem where an enumeration knob is returning the index instead of the txt? Is there a fix for this, as some shots get it, but most of the time the knob will be correct. I don't know what

Re: [Nuke-users] Re: [Nuke-python] enumeration knobs being saved with int instead of txt

6.2v1 On Jun 6, 2011, at 9:57, Wouter Klouwen wou...@thefoundry.co.uk wrote: Can you tell us what version of Nuke you're using? Thanks. On Thu, 2 Jun 2011 13:07:00 +0200, John RA Benson john.benson.macg...@gmail.com wrote: Has anyone had the problem where an enumeration knob

[Nuke-users] enumeration knobs being saved with int instead of txt

Has anyone had the problem where an enumeration knob is returning the index instead of the txt? Is there a fix for this, as some shots get it, but most of the time the knob will be correct. I don't know what would cause it to save txt in some cases and the index in others. for instance, this

[Nuke-users] updating nodes based on DAG?

Hello - Someone showed me a neat trick with a node to re-define the postage stamp. The hardcoded values of 80 and 45 are the width and height of my icon image, but they can be whatever values it takes to make the image fit in the node: set cut_paste_input [stack 0] version 6.2 v1 Read {

[Nuke-users] Nothing is named error

Hello - We're occasionally getting a very hard to understand error message: 'Nothing is named /path/to/my/script' however, the path does NOT include the .nk extension. I've managed to fix scripts by deleting {} removing version ... in the script header (we rolled back to 6.2v1 from

Re: [Nuke-users] Error in expression node on script load

are doing? cheers JRAB On May 18, 2011, at 11:45 PM, John RA Benson wrote: hey there - this makes me wonder - is there a way to force reloading the script? I've seen this with some of our gizmos that are built at launch, where the nodes that depend on them error because (i'm guessing

Re: [Nuke-users] Error in expression node on script load

hey there - this makes me wonder - is there a way to force reloading the script? I've seen this with some of our gizmos that are built at launch, where the nodes that depend on them error because (i'm guessing) the gizmo is still building itself after the node that depends on it is created.

Re: [Nuke-users] Rendering multiple writes sequentially

wow - thats a good tip - what on earth could postage stamps have to do with render order and is that a bug or a feature? It wouldn't ever have occurred to me to try turning them off to debug a problem like this. Good to know, thanks- jrab On May 17, 2011, at 18:05, Peter Pearson

Re: [Nuke-users] setting the default render view in the write node?

. once it gets messed up, it's always broken). -Nathan -Original Message- From: John RA Benson Sent: Friday, May 06, 2011 6:27 AM To: Nuke user discussion Subject: Re: [Nuke-users] setting the default render view in the write node? Actually, not the 'view' knob, but the 'multi_view

[Nuke-users] setting the default render view in the write node?

I just came upon a very frustrating problem in trying to get some images rendered. We have a left eye render that is done first and the comp's 'look' is based on that before rendering the right eye. To simplify the pipe, all the reads and writes are %v (for L and R). Usually, this hasn't been

Re: [Nuke-users] Nuke deleting scripts

unfortunately, I've been seeing this a lot too. The bad news is, your script didn't really save completely. Open it in a text editor and chances are you'll see a script that doesn't end with }. Could have been a network problem or Nuke crashed during the save? I hope your backups are working.

Re: [Nuke-users] knob stuff in text format?

thanks, Frank! JRAB On Mar 30, 2011, at 3:36 AM, Frank Rueter wrote: If I remember correctly it indicates wether a field is selected in the curve editor. On Mar 30, 2011, at 11:23 AM, John RA Benson wrote: Hey there - Just wondering - what does the 'i' in the expression inside

[Nuke-users] knob stuff in text format?

Hey there - Just wondering - what does the 'i' in the expression inside the knob value mean? I'm assuming 'l' means label, 't' means tooltip, 'R' is range, but 'i'? In this instance, for a center knob in a transform, I created the expression for a horizon knob in a gizmo. In text form it looks

[Nuke-users] ERROR: cannot set mapsize to 0 columns, 1 rows

Anyone know what this error means? [ 8:49.12] ERROR: cannot set mapsize to 0 columns, 1 rows I've seen it with other User knobs too. Not sure if it's actually causing problems. thanks JRAB___ Nuke-users mailing list

Re: [Nuke-users] Re: [ Nuke-users ] ERROR: cannot set mapsize to 0 columns, 1 rows

good to know! but, wow that's weird. I'm not setting a mapsize knob anywhere - what the heck is it for, anyway? in fact, I deleted the mapsize line that was created with the gizmo and i think that's when the error showed up. great - 8 hours later and now I can't reproduce the error with or

Re: [Nuke-users] Re: chan exporter rounding values?

I wonder if this might be related to the color picker/knobs differences bug? Concerning that bug: any knob that is using a color picker is rounding the results to 3 decimal places, or a funny rounded floating point which is still not correct. It's a surprisingly obvious bug - just use the