Re: [Nuke-users] Email not in spam test - please respond

[Nico Dufort]

Still going to spam for me.

On Sun, Mar 13, 2016 at 5:17 PM, Bruno-Pierre Jobin 
wrote:

>  Spam for me.
>
>
> > On Mar 13, 2016, at 7:57 PM, Martin Constable 
> wrote:
> >
> > Not spam for me.
> >
> > Sent from my iPhone
> >
> >> On 14 Mar 2016, at 7:55 AM, Hugo Léveillé  wrote:
> >>
> >> Not spam for me
> >>
> >> Sent from my iPhone
> >>
> >>> On Mar 13, 2016, at 7:51 PM, Howard Jones 
> wrote:
> >>>
> >>> Hi
> >>>
> >>> Could anyone tell me if this is not in spam please? Only need a couple
> of replies, before this gets too noisey.
> >>>
> >>> Thanks
> >>>
> >>> Howard___
> >>> 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
> > ___
> > 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
>



-- 
"Attention, attention. Here and now, boys," the mynah repeated. "Here and
now, boys."
___
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] bug - inputs switching when saving

[Nico Dufort]

We've experienced something a bit similar when decloning nodes (no facility
code involved, just plain vanilla Nuke).
We first noticed that back on 6.3 and it still seems to be an issue on 9.x.



​

On Mon, Jul 13, 2015 at 4:57 PM, niki  wrote:

> Hello
>
>
> long time since I used this list so please excuse me if I am repeating a
> bug that may be already known.
>
> I'm currently working at Cutting Edge in Sydney and we have noticed a
> pretty bad bug in both v08 and v9.0v5.
> At some point after working on a shot for some time our scripts become
> corrupted and on Save the merge inputs swap randomly between the matte and
> a side or jump to different nodes all together.
>
> So far we have noted that it seems to be only the A stream and the Matte
> that is affected. The B stream seems to remain correct.
>
> The only solve we have found is to remove all merge nodes.
> Save file
> Replace all merge nodes.
>
> Has anyone else seems this ?
>
> Many Thanks
>
> Niki
>
>
>
>
> nb_n...@yahoo.com.au
> www.nikibern.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
>



-- 
"Attention, attention. Here and now, boys," the mynah repeated. "Here and
now, boys."
___
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] Adobe anyone?

[Nico Dufort]

Natron  ;)

On Tue, Apr 28, 2015 at 2:50 PM, Elias Ericsson Rydberg <
elias.ericsson.rydb...@gmail.com> wrote:

> Fusion, and maybe shake? ;-)
> Den 28 apr 2015 23:26 skrev "Chris Noellert" :
>
>> What competes with Nuke?
>>
>> On Apr 28, 2015, at 2:21 PM, Diogo Girondi 
>> wrote:
>>
>> Ha! It took at least 19 years for Adobe to include interactive round
>> corners for shapes in Illustrator. That is how ridiculous things become
>> once there is no real competitors for a software.
>>
>> On ter, 28 de abr de 2015 at 06:51 Charles Bedwell <
>> charles.bedw...@encorepost.com> wrote:
>>
>>>   Adobe doesn't put enough effort into its existing applications. It
>>> wouldn't kick anything into overdrive, it would put everything on the back
>>> burner (see Adobe Illustrator for the past 10 years).
>>>
>>>  Adobe purchased Aldus to obtain Page Maker, but was prevented from
>>> purchasing Freehand for 10 years due to fears it would control the vector
>>> graphics market. 10 years later they purchased Macromedia and left Freehand
>>> to die while steadily increasing the price of Illustrator, adding 3 or 4
>>> features per release. Freehand supported multiple pages in 1991.
>>> Illustrator? 2008.
>>>
>>>  I'll just leave this here: http://adobegripes.tumblr.com
>>>
>>>
>>>
>>>
>>> On 26 Apr 2015, at 11:20 pm, J Bills  wrote:
>>>
>>>I'd love to see Adobe win the bid.  I think there's a lot of work to
>>> be done leveraging all of that tech across the various apps, and a company
>>> like Adobe could put enough resources to make it happen where I think the
>>> Foundry has had enough to pull the raw ingredients together and pry these
>>> apps out of the studios and out into the open - but to properly merge them
>>> anytime soon, and mass market them correctly to maximize sales and cross
>>> pollination, takes possibly more muscle than they have.  Not to say that
>>> they couldn't get there but Adobe stepping in would kick everything into
>>> overdrive.
>>>
>>> Modo makes a TON of sense for them to finally enter the 3d market with,
>>> since it's got it's hooks firmly planted in the design world.
>>>
>>>  Nuke (and Mari) would make a great base for a Photoshop rewrite.  A non
>>> destructive, truly float capable Photoshop that still maintains
>>> interactivity?  Wow.  We've all known dating back to Shake that this is a
>>> much better way to work, but I imagine any attempt that Apple or anyone
>>> else has ever made at a Photoshop killer was probably met with lots of
>>> patent litigation.
>>>
>>>  Lots more could be done with Katana.  Anyone that worked at Sony knows
>>> it's gold.  Would be cool to see it pushed up the priority list or further
>>> integrated with Nuke.
>>>
>>> I imagine the real prize for Adobe is Modo, but I'd hope nothing happens
>>> to the purity of Nuke and that they wouldn't strip it for tech and then
>>> leave it for dead, like Avid/Apple/etc.  I had thought the future of Nuke
>>> was relatively safe but I suppose nothing is ever a sure thing.
>>>
>>> Let's hope this isn't the kiss of death.  Fusion makes me cringe (but
>>> the price is right!)
>>>
>>>
>>> On Sun, Apr 26, 2015 at 11:18 AM, Ron Ganbar  wrote:
>>>
 That would actually be a welcome thing.
 An Adobe purchase might turn out to be a good thing in the end. It
 doesn't all need to end up like Apple buying Nothing Real. It can end up
 like Blackmagic buying Fusion. Who knows.
  R





 Ron Ganbar
 email: ron...@gmail.com
 tel: +44 (0)7968 007 309 [UK]
  +972 (0)54 255 9765 [Israel]
 url: http://ronganbar.wordpress.com/

   On Sun, Apr 26, 2015 at 9:11 PM, Gil Woodley 
 wrote:

> I see a subscription model in the future...
>
> On Sun, Apr 26, 2015 at 8:02 PM, Elias Ericsson Rydberg <
> elias.ericsson.rydb...@gmail.com> wrote:
>
>> I would have loved to see Side FX aquire The Foundry.
>>  Den 26 apr 2015 19:59 skrev "Jose Fernandez de Castro" <
>> pixelcowbo...@gmail.com>:
>>
>>> That would be really terrible news if they got acquired by Adobe...
>>>
>>> On Sun, Apr 26, 2015 at 10:38 AM, Ron Ganbar 
>>> wrote:
>>>
 I was thinking of Freehand. I loved Freehand. Took me years to get
 used to illustrator.

 R
   On 26 Apr 2015 20:16, "Randy Little" 
 wrote:

> Macromedia did fine after purchase accept for freehand.
> On Apr 26, 2015 1:07 PM, "Ron Ganbar"  wrote:
>
>> Yeah, the Telegraph are spot on.
>>
>>  I agree with Diogo. Hope The Foundry won't end up like
>> Macromedia...
>>
>>
>>
>> Ron Ganbar
>> email: ron...@gmail.com
>> tel: +44 (0)7968 007 309 [UK]
>>  +972 (0)54 255 9765 [Israel]
>> url: http://ronganbar.wordpress.com/
>>
>> On Sun, Apr 26, 2015 at 7:53 PM, Chris Noellert <
>>>

Re: [Nuke-users] The forums are moving

[Nico Dufort]

One thing I would like to add is that more and more shops have removed or
will be cutting off internet access to their artists because of
requirements made by certains clients when working on projects.

If people have to use their phone/tablet at work to interact with other
Nuke users and developers, chances are that doing so through email will be
a lot more simple and convenient than navigating a community forum that is
not always as accessible and portable as email on such devices.

My personal bit: unless the search functions of the forum is also updated,
it is a lot easier to search for something in one's mailbox than on the
forum.

Just a thought.
nico

On Tue, Feb 3, 2015 at 9:30 AM, Emma Handley 
wrote:

> You will have to go into the forums if you'd like to reply. There will be
> a link to take you straight to the conversation and we're making this as
> simple as possible.
>
> We didn't make the decision lightly and think that overall you will all
> enjoy being over at The Community.
>
> We'll share some more info shortly,
> Emma
>
>
> On 3 February 2015 at 16:44, Rich Bobo  wrote:
>
>> +1
>>
>>
>>
>> Rich Bobo
>> Senior VFX Compositor
>> Armstrong White
>> Email:  rich.b...@armstrong-white.com
>> http://armstrong-white.com/
>>
>> Email:  richb...@mac.com
>> Mobile:  (248) 840-2665
>> Web:  http://richbobo.com/
>>
>>
>> On Feb 3, 2015, at 11:04 AM, Ron Ganbar  wrote:
>>
>> I'm with Gary on this.
>> The Nuke mailing list is the only one I contribute towards just because I
>> don't have to go to a website to do so. It's happening in my email and
>> that's it. Easy.
>>
>>
>>
>> Ron Ganbar
>> email: ron...@gmail.com
>> tel: +44 (0)7968 007 309 [UK]
>>  +972 (0)54 255 9765 [Israel]
>> url: http://ronganbar.wordpress.com/
>>
>> On Tue, Feb 3, 2015 at 5:42 PM, Gary Jaeger  wrote:
>>
>>>
>>> > On Feb 3, 2015, at 3:40 AM, The Foundry 
>>> wrote:
>>> >
>>> > *The forums are moving*
>>>
>>> Oh dear.
>>>
>>> Will it allow us to behave the same? With never having to visit the
>>> forum once we set up the subscription? i.e. can we just send an email to "
>>> somenukeaddr...@foundry.com" to create a new topic? Can we just reply
>>> via email? Have every topic come in via email? In other words, behave just
>>> like the list?
>>>
>>> Gary Jaeger // Core Studio
>>> 249 Princeton Avenue
>>> Half Moon Bay, CA 94019
>>> 650 728 7060
>>> http://corestudio.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 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
>>
>
>
>
> --
> --
> Emma Handley
> Social Media & Community Executive
> The Foundry
> Skype: emma_foundry
> Tel: +44 20 7479 4350 
> - Fax: +44 (0)20 7930
> 8906
> Web: www.thefoundry.co.uk
> Email: *emma.hand...@thefoundry.co.uk *
>
> The Foundry Visionmongers Ltd.
> Registered in England and Wales No: 4642027
>
> ___
> 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
>



-- 
"Attention, attention. Here and now, boys," the mynah repeated. "Here and
now, boys."
___
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] Wireframe shader alpha in Nuke8

[Nico Dufort]

Hello again,

In Nuke8, should one use the hidden-line look of the wireframe shader, the
alpha is only the silhouette of the geometry, versus Nuke7's "replace" mode
of the shader.

Is that by design?  Is anyone else hacking their way around that through
shuffles and other nodes?

Cheers. nico

-- 
"Attention, attention. Here and now, boys," the mynah repeated. "Here and
now, boys."
___
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] GridWarp submesh resolution ignored?

[Nico Dufort]

Hello,

It has been brought to my attention that rendering a GridWarp in the GUI
and on the farm give different results.

My tests showed that no matter what value was entered under "submesh
resolution", when rendering in terminal mode, the output did not reflect
the entered value.  I tried extreme values, but it seems to always render
with a value of 10.  I tried to set a keyframe on that knob, hoping some
magic would happen, but no luck.

I tried a vanilla version of Nuke, and I could reproduce that, so that's
not our code getting in the way. I have tried under different 7.0 and 8.0
versions, and I always had the same result.

Has anyone experienced that behavior?  Any way around this?

Thanks
nico

-- 
"Attention, attention. Here and now, boys," the mynah repeated. "Here and
now, boys."
___
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] Re: keyboard shortcut to close a tab?

[Nico Dufort]

Matt, I tend to point artists to the Help>Nuke Key Assignment dialogue...
They won't believe what one can find in there... ;)


On Mon, Aug 26, 2013 at 9:30 AM, John Stewart  wrote:

> Looks like on OSX it's alt+escape, FYI.
>
>
>
>
> matt estela wrote:
>
> Hooray! Everyone wins. :)
>
>
>
> On Monday, August 26, 2013, Frank Rueter wrote:
>
>> just to help prevent further firings, I have added this one to the random
>> tips banner on Nukepedia ;)
>>
>>
>> On 26/08/13 14:02, matt estela wrote:
>>
>> We have a winner! I'd asked several compers here, no-one knew. They're
>> all fired. Not mentioning any names. Alex Fry.
>>
>>
>>
>>
>> On 26 August 2013 11:57, David Yu  wrote:
>>
>>> shift escape?
>>>
>>>
>>>  On Mon, Aug 26, 2013 at 8:41 AM, matt estela  wrote:
>>>
   Been investigating this in downtime, thought someone might have
 solved it already:

  We're using groups a lot, ctrl-enter to open a group in a new tab is
 very handy. Surprised to find  there's no matching shortcut to close a tab.

  Anyone know how to define a keyboard shortcut to do this?

  -matt



  ___
 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
>>>
>>
>>
>>
>> ___
>> 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
>>
>>
>>  ___
> 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
>
>
> ___
> 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
>



-- 
"Attention, attention. Here and now, boys," the mynah repeated. "Here and
now, boys."
___
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] Tiff metadata / tags

[Nico Dufort]

While I am enjoying the microdots-spy approach to tag an image with secret
render host information, am I missing something or you could just check
your render logs?   Or... you don't have logs? =P


On Tue, Jan 29, 2013 at 10:50 AM, chris  wrote:

> or extending on that idea...
> since a single black pixel could be noticable in the middle of bright
> colored pixels, you could duplicate the pixel color next to it (or even
> average the pixels around it), and add an offset with the hostname value.
> this would probably be invisible even by the most critical eyes :)
>
> example if the pixel on the bottom left [0,0] is to hold the machine ID
> data:
> - average pixels [0,1], [1,1] and [1,0] to calculate the [0,0] color value
> - add tiny offset color value representing the machine ID to that pixel
> [0,0]
>
> obviously you'd want a second script which automatically calculates the
> machine ID from the 4 pixels on the bottom left.
>
> there's probably an easier way that i'm not aware of though ;)
> ++ chris
>
>
>
>
> On 1/29/13 at 7:27 PM, ze.m...@gmx.net (chris) wrote:
>
>  hmm, or if you can spare a single pixel somewhere, you could just burn in
>> the hostname as color (or alpha) value...
>> like in the bottom right corner, each render machine gets a slightly
>> different shade of black (ie render1 is 0.1, render2 is 0.2 etc)
>>
>> then if you have corrupt renders you could check the pixel value and see
>> where it came from.
>>
>> ++ chris
>>
>>
> __**_
> 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
>



-- 
"Attention, attention. Here and now, boys," the mynah repeated. "Here and
now, boys."
___
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] Nuke 7.0v2 not starting on Fedora 18 installed on macPro 3.1

[Nico Dufort]

>
> libGL error: failed to load driver: swrast


That might be related to mesa.  I don't know much about all this, but do
you have mesa installed?  I do remember similar issues the first time I
installed Nuke on Mint a long time ago, and that came from a bad graphics
driver--Mint offers three and the default one did not work for Nuke.


On Sat, Jan 19, 2013 at 4:02 PM, adam jones  wrote:

> hi there
>
> I am trying to set up a nuke 7.0v2 install on fedora 18 (not Live CD)
> mainly just a learning experience with linux.
>
> I have fedora 18 installed on a macbook pro 3.1
>
> plroblem being is when I goto start up nuke I get the splash screen then
> about 5 secs later just fades away.
>
> the error message I get in the terminal is :
>
> libGL error: Try again with LIBGL_DEBUG=verbose for more details.
> libGL error: failed to load driver: swrast
> libGL error: Try again with LIBGL_DEBUG=verbose for more details.
> X Error: GLXBadContext 170
>   Extension:153 (Uknown extension)
>   Minor opcode: 6 (Unknown request)
>   Resource id:  0x2800066
> X Error: BadAlloc (insufficient resources for operation) 11
>   Extension:153 (Uknown extension)
>   Minor opcode: 3 (Unknown request)
>   Resource id:  0xfe
> X Error: GLXBadContext 170
>   Extension:153 (Uknown extension)
>   Minor opcode: 6 (Unknown request)
>   Resource id:  0x280006c
> X Error: GLXBadContext 170
>   Extension:153 (Uknown extension)
>   Minor opcode: 3 (Unknown request)
>   Resource id:  0x2800066
> X Error: GLXBadContext 170
>   Extension:153 (Uknown extension)
>   Minor opcode: 6 (Unknown request)
>   Resource id:  0x2800071
> X Error: GLXBadContext 170
>   Extension:153 (Uknown extension)
>   Minor opcode: 3 (Unknown request)
>   Resource id:  0x2800066
> X Error: GLXBadContext 170
>   Extension:153 (Uknown extension)
>   Minor opcode: 6 (Unknown request)
>   Resource id:  0x2800082
> [xcb] Unknown sequence number while processing queue
> [xcb] Most likely this is a multi-threaded client and XInitThreads has not
> been called
> [xcb] Aborting, sorry about that.
> Nuke7.0: xcb_io.c:273: poll_for_event: Assertion
> `!xcb_xlib_threads_sequence_lost' failed.
>
>
> anyone have some suggestions at to what I need to do?
>
> -adam
> ___
> 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
>



-- 
"Attention, attention. Here and now, boys," the mynah repeated. "Here and
now, boys."
___
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] How to get all but one class in nuke.selectedNodes…?

[Nico Dufort]

If that code was just to build a list, definitively use Nathan's way as I
would write in the same manner.  It is clean, simple, and efficient.
If the loop is meant to do more than that, then you can use the default
loop layout and add statements as needed.

Cheers.

On Fri, Jan 4, 2013 at 4:24 PM, Rich Bobo  wrote:

> Nathan - Thanks!  I also was thinking about doing an on-the-fly filtering
> but, being a novice, I couldn't fathom the right syntax…
>
> I'll use your suggestion to make my code a bit shorter and keep Nico's
> solution in my toolkit for another day!
>
> Rich
>
>
> On Jan 4, 2013, at 7:17 PM, Nathan Rusch  wrote:
>
>   Looks like a reply to this showed up in nuke-python instead of
> nuke-users, so this is a duplicate response.
>
> It’s much more efficient to simply filter the nodes as you assemble a list:
>
> notViewers = [n for n in nuke.selectedNodes() if n.Class() != 'Viewer']
>
> -Nathan
>
>
>  *From:* Rich Bobo 
> *Sent:* Friday, January 04, 2013 4:12 PM
> *To:* Nuke user discussion 
> *Subject:* Re: [Nuke-users] How to get all but one class in
> nuke.selectedNodes…?
>
> Nico,
>
> Thanks for the speedy response!
>
> I only care about removing Viewers from the "selected collection" - I
> don't care about what they are actually connected to.
>
> As I was thinking about the problem, it did occur to me that maybe I need
> to treat the selected nodes as a list and use .remove, but I wasn't sure
> how to go about it. And, I was unfamiliar with the shorthand for working on
> a copy of the list!
>
> I'll give your code a try. ...If it works, I'm going home!  ;^)
>
> Thanks,
>
> Rich
>
>
>  On Jan 4, 2013, at 6:56 PM, Nico Dufort  wrote:
>
> Your code does nothing to remove anything from your collection.  Did you
> mean something similar to this:
>
> collection = nuke.selectedNodes()
> for n in collection[:]:   # use a copy of your list to be able to remove
> items from it
>if n.Class() == 'Viewer':
>n['selected'].setValue(False)
>collection.remove(n)
>
> At this point, your viewers are deselected and not part of your collection.
>
> That being said, you mentioned something about them being "connected", but
> your code did not address anything with connection.  Is this what you were
> after, or you really needed something around the connection between nodes
> and viewers to be dealt with?
>
> Cheers. nico
>
> On Fri, Jan 4, 2013 at 3:44 PM, Rich Bobo  wrote:
>
>> Hi,
>>
>> I can't get my brain to figure this out, so I'm reaching out to the
>> "collective brain"…  8^)
>>
>> I need a collection of nodes, minus any connected Viewers. So, selNodes =
>> nuke.selectedNodes()  --- but without any Viewers that may be connected...
>>
>> I can do this:
>>
>>  selNodes = nuke.selectedNodes()
>> for node in selNodes:
>> if node.Class() == 'Viewer':
>> node["selected"].setValue(False)
>> else:
>> node['selected'].setValue(True)
>>
>>  However, that does not change the original collection of nodes - it
>> still has all of the nodes that were connected when I set the origin
>> variable, including any Viewers. I want to *remove* any Viewer class nodes
>> from the selNodes collection!
>>
>> I know it's probably simple, but it's been a long week… Any help?
>>
>> Thanks!
>>
>> Rich
>>
>>
>> Rich Bobo
>> Senior VFX Compositor
>> Armstrong-White
>> http://armstrong-white.com/
>>
>> Email:  richb...@mac.com
>> Mobile:  (248) 840-2665 <%28248%29%20840-2665>
>> Web:  http://richbobo.com/
>>
>> "Until one is committed, there is hesitancy, the chance to draw back
>> ineffectiveness. Concerning all acts of initiative and creation, there is
>> one elementary rule - the ignorance of which kills countless ideas and
>> splendid plans; that the moment one definitely commits oneself, then
>> Providence moves too. Things occur to help that would never otherwise have
>> occurred. A whole stream of events issues from the choice, raising in one's
>> favour all manner of unforeseen incidents and meetings and material
>> assistance, which no man could have dreamed would have come his way."
>> - Goethe
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ___
>> Nuke-users mailing list
>> Nuke-users@support.thefoundry.co.uk, http://forums.thefo

Re: [Nuke-users] How to get all but one class in nuke.selectedNodes…?

[Nico Dufort]

Your code does nothing to remove anything from your collection.  Did you
mean something similar to this:

collection = nuke.selectedNodes()
for n in collection[:]:   # use a copy of your list to be able to remove
items from it
   if n.Class() == 'Viewer':
   n['selected'].setValue(False)
   collection.remove(n)

At this point, your viewers are deselected and not part of your collection.

That being said, you mentioned something about them being "connected", but
your code did not address anything with connection.  Is this what you were
after, or you really needed something around the connection between nodes
and viewers to be dealt with?

Cheers. nico

On Fri, Jan 4, 2013 at 3:44 PM, Rich Bobo  wrote:

> Hi,
>
> I can't get my brain to figure this out, so I'm reaching out to the
> "collective brain"…  8^)
>
> I need a collection of nodes, minus any connected Viewers. So, selNodes =
> nuke.selectedNodes()  --- but without any Viewers that may be connected...
>
> I can do this:
>
> selNodes = nuke.selectedNodes()
> for node in selNodes:
> if node.Class() == 'Viewer':
>  node["selected"].setValue(False)
> else:
> node['selected'].setValue(True)
>
>  However, that does not change the original collection of nodes - it still
> has all of the nodes that were connected when I set the origin variable,
> including any Viewers. I want to *remove* any Viewer class nodes from the
> selNodes collection!
>
> I know it's probably simple, but it's been a long week… Any help?
>
> Thanks!
>
> Rich
>
>
> Rich Bobo
>  Senior VFX Compositor
> Armstrong-White
> http://armstrong-white.com/
>
> Email:  richb...@mac.com
> Mobile:  (248) 840-2665
> Web:  http://richbobo.com/
>
>"Until one is committed, there is hesitancy, the chance to draw back
> ineffectiveness. Concerning all acts of initiative and creation, there is
> one elementary rule - the ignorance of which kills countless ideas and
> splendid plans; that the moment one definitely commits oneself, then
> Providence moves too. Things occur to help that would never otherwise have
> occurred. A whole stream of events issues from the choice, raising in one's
> favour all manner of unforeseen incidents and meetings and material
> assistance, which no man could have dreamed would have come his way."
>  - Goethe
>
>
>
>
>
>
>
>
>
>
>
>
> ___
> 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
>



-- 
"Attention, attention. Here and now, boys," the mynah repeated. "Here and
now, boys."
___
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] node properties dialog

[Nico Dufort]

Maybe not what you are after, but a Ctrl+Click on your wanted node will
open the properties in its own floating window, regardless of what settings
you have in your properties panel.  You can clear the properties bin, but
the floating panel of that one node will stick around.

nico

On Thu, Nov 22, 2012 at 11:00 AM, adam jones  wrote:

> Hey all
>
> I am sure it is right infront of me but I cant see it.
>
> is there a way to lock a node dialog in the props pane, basic so it wont
> close when you click the close all button or when it slips of the list when
> you reach maximum dialogs setting.
>
> -adam
>
> ___
> 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
>



-- 
"Attention, attention. Here and now, boys," the mynah repeated. "Here and
now, boys."
___
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