Re: [Nuke-users] Studio

2016-10-24 Thread Frank Rueter|OHUfx
Sounds like you just need Hiero rather than NS then if all you want to do is export nuke scripts. The main issues with exporting nuke scripts via Hiero/NS are: * pipeline settings for nuke are not picked up (e.g. custom knobs/callbacks in Read/Write nodes etc) * Depending on the complexity

Re: [Nuke-users] Studio

2016-10-24 Thread Gary Jaeger
Thanks Frank. I’ll see if Hiero will do what we need. Gary Jaeger / 650.728.7957 direct / 415.518.1419 mobile http://corestudio.com > On Oct 24, 2016, at 2:25 PM, Frank Rueter|OHUfx wrote: > > Sounds like you just need Hiero rather than NS then if all

Re: [Nuke-users] Studio

2016-10-24 Thread Deke Kincaid
This script below is pretty nice for cleaning up the mess of a script that Nuke Studio creates when you run create comp. http://fynnlaue.com/nuke-studio-comp-cleaner/ http://www.nukepedia.com/python/nodegraph/nuke-studio-comp-cleaner/ On Mon, Oct 24, 2016 at 4:34 PM, Frank Rueter|OHUfx

Re: [Nuke-users] Studio

2016-10-24 Thread Frank Rueter|OHUfx
Unless you need to interact with nuke comp scripts directly in the timeline (and use Nuke a bit like Flame) Hiero should be sufficient as it's the same thing when it comes to timeline and exporting. On 10/25/2016 11:45 AM, Gary Jaeger wrote: Thanks Frank. I’ll see if Hiero will do what we

Re: [Nuke-users] Studio

2016-10-24 Thread Ned Wilson
Related to this topic Frank - Are you aware of anyone who has written some sort of template-based Nuke script exporter for Studio or Hiero? I really wish that we could have more precise control over how these scripts are laid out. In addition, support for custom knobs would be awesome. I’d

[Nuke-users] Rendering arbitrary Write nodes with the FrameServer

2016-10-24 Thread Ned Wilson
Hello all, I have a setup here where there are some artists with Nuke licenses on their workstations who have gone on vacation. I have gone ahead and launched the FrameServer process on these workstations, and it speeds up my comp renders tremendously. However, there are certain instances

Re: [Nuke-users] Rendering arbitrary Write nodes with the FrameServer

2016-10-24 Thread Phillip Lange
Hi Ned, I has the same issue a while back and someone kindly pointed out that you can change the specified write node in the project settings for your comp script. When you're in your comp script just go to the studio tab and enter the write nodes name in the field. Then go back to the timeline

Re: [Nuke-users] node defaults (strings in label)

2016-10-24 Thread Deke Kincaid
the label uses basic html. So you can do things like: line break: center: bold: etc… just google for html formatting. On Mon, Oct 24, 2016 at 10:48 PM, adam jones wrote: > Hey all > > I am setting up some node defaults which I am all good with. > > the thing I wish to do

[Nuke-users] node defaults (strings in label)

2016-10-24 Thread adam jones
Hey all I am setting up some node defaults which I am all good with. the thing I wish to do is have some values reflected in the label of the node [value in] and the like what I can figure out is to have each value have its own line or returned. lacking the skills regards -adam

[Nuke-users] Studio

2016-10-24 Thread Gary Jaeger
We stopped trying with Studio a while back, in fact almost canceled our support because of it. But we have show where I thought I’d venture back since really all I need to create nuke scripts for all the shots and do it quickly to parcel out to trackers and compers. Probably use premiere or

Re: [Nuke-users] get pulldown index

2016-10-24 Thread Erik Johansson
p = nuke.Panel("Please select Input and Output Resolution") vals = ['format1', 'format2', 'format3'] p.addEnumerationPulldown('Input Format', ' '.join(vals)) p.show() val = p.value('Input Format') index = vals.index(val)print index ​ On Mon, Oct 24, 2016 at 4:33 PM, Daniel Hartlehnert

[Nuke-users] get pulldown index

2016-10-24 Thread Daniel Hartlehnert
Hi, i created a nuke panel and added an enumeration pulldown: p = nuke.Panel("Please select Input and Output Resolution") p.addEnumerationPulldown("Input Format“,format1 format2 format3) Now i want to know which index was selected by the user. If i use: p.value(‚Input Format‘) i only get

Re: [Nuke-users] get pulldown index

2016-10-24 Thread Daniel Hartlehnert
Ok, thanks. This example works. I tried to put it to use in my case, and failed though :( The pulldown should basically be a copy of the format list in the nuke script settings: This is what it got: allformats = nuke.formats() allformatlist = [] for i in allformats:

Re: [Nuke-users] get pulldown index

2016-10-24 Thread Daniel Hartlehnert
Ok, great, thanks a bunch! > Am 24.10.2016 um 21:23 schrieb Igor Majdandzic : > > Because you have to populate it with my method via dictionary. I added it. > Now it works. > allformats = nuke.formats() > > f = '' > for i in nuke.formats(): > f += ' ' +

Re: [Nuke-users] get pulldown index

2016-10-24 Thread Igor Majdandzic
Because you have to populate it with my method via dictionary. I added it. Now it works. allformats = nuke.formats() f = '' for i in nuke.formats(): f += ' ' + i.name() dict = {'formats': f} allformatlist = [] for i in allformats: allformatlist.append(i.name()) print allformatlist