Re: [Nuke-users] Re: neat video failing in 9.05

2015-06-04 Thread Sebastian Elsner|RISE
I had this before and deleting all caches of nuke manually made it work 
again in all versions


On 06/04/2015 06:28 PM, Howard Jones wrote:

Ok fixed in v06. - unless it was the v05 install that went wrong?
H


On 4 Jun 2015, at 17:16, Howard Jones mrhowardjo...@yahoo.com 
mailto:mrhowardjo...@yahoo.com wrote:


Hi

Anyone else seeing this?…

I can’t run neat video in 9.0v5 but it’s fine in Nuke9.0v4 and before.
This is the error...

nuke.createNode(OFXcom.absoft.neatvideo_v2)
Traceback (most recent call last):
File string, line 1, in module
RuntimeError: Constructor for OFXcom.absoft.neatvideo_v2 failed

Will try v06 later.

*H*




___
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


--

_*check out pointcloud9.com*_ http://pointcloud9.com/

**Sebastian Elsner - Pipeline Techincal Director - RISE*

t: +49 30 20180300 _sebast...@risefx.com _ mailto:sebast...@risefx.com
f: +49 30 61651074 _www.risefx.com_ http://www.risefx.com/*

*RISE FX GmbH*
*Schlesische Straße 28, 10997 Berlin
An der Schanz 1A, 50735 Köln
Büchsenstraße 20, 70174 Stuttgart
Gumpendorferstraße 55, 1060 Wien
Geschaeftsfuehrer: Sven Pannicke, Robert Pinnow
Handelsregister Berlin HRB 106667 B*

___
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 crash on exit

2015-06-03 Thread Sebastian Elsner|RISE

This seems to be a common issue. We have it too.

On 06/03/2015 04:37 PM, Jake Richards wrote:
To maybe reiterate what Frank says, I can get consistent seg faults 
with the following code in linux and Nuke 9.0v4:


Nuke9.0 --safe
(paste and execute this code in the script editor)
###
from PyQt4 import QtGui,QtCore

class pyQtTestDialog(QtGui.QWidget):
def __init__(self):
super(pyQtTestDialog,self).__init__()
self.grid = QtGui.QGridLayout()
self.setLayout(self.grid)
self.OKButton = QtGui.QPushButton(Ok)
self.cancelButton = QtGui.QPushButton(Cancel)
self.grid.addWidget(self.OKButton,0,0,1,1)
self.grid.addWidget(self.cancelButton,0,1,1,1)
self.connect(self.OKButton,QtCore.SIGNAL('clicked()'),self.close)
self.connect(self.cancelButton,QtCore.SIGNAL('clicked()'),self.close)


nuke.menu(Nuke).addCommand(HI,t = pyQtTestDialog();t.show())
###

Click HI, then close the window and Nuke and I get a seg fault.
In Nuke 8.0v6 everything used to work fine.  What are the versions of 
Qt or PyQt that should be used?

My query reports:

('Qt version:', '4.8.4')

('PyQt version:', '4.10.2')


Thanks!

Jake




*From: *Frank Rueter|OHUfx fr...@ohufx.com
*To: *nuke-users@support.thefoundry.co.uk
*Sent: *Tuesday, June 2, 2015 9:20:16 PM
*Subject: *Re: [Nuke-users] Nuke crash on exit

I get it every time the moment I use the viewer.
-start nuke
-create checkerboard
-hook up checkerboard to viewer
-close nuke
-seg fault

Without my pipeline code (which does register a couple of PySide
widgets as nuke panels) it doesn't happen, but it never used to
happen before Nuke 8.

Reported this back when it started in Nuke 8



On 03/06/15 01:45, Rich Bobo wrote:

Frank,

I have been getting crashes on exit (Nuke 9.0v4 on Windows 7
Pro) for a while now… Not sure what leads to the problem -
it’s fairly random. Could be high memory usage, but I’m not
sure. My machine has 64 GB of RAM...

Rich


Rich Bobo
Senior VFX Compositor
Armstrong White
Email: rich.b...@armstrong-white.com
mailto:rich.b...@armstrong-white.com
http://armstrong-white.com/

Email: richb...@mac.com mailto:richb...@mac.com
Mobile:  (248) 840-2665
Web: http://richbobo.com/

On Jun 1, 2015, at 7:29 PM, Frank Rueter|OHUfx
fr...@ohufx.com mailto:fr...@ohufx.com wrote:

interestingly Nuke9 decided to seg fault on start up for
me as well now. If I keep trying it eventually launches.
anybody else?

On 31/05/15 18:02, Daniel Hartlehnert wrote:

Uh, segmentation fault crashes. Getting these alot! on 
Linux/Nuke7.
However, the crashes i talked about don't show any error 
message in the command line window. Usually its already gone as well.


Am 31.05.2015 um 05:22 schrieb Ben Dickson:

Might be due to this (not sure if this is still the case in 
Nuke 9):

On 23/11/13 02:54, The Foundry Support wrote:

Hi Ben

I managed to get this crashing consistently on Linux 
with your steps in Nuke
7/8 but not in 6.3v9.  I've reopened the bug.

Thanks

Jason

Ben Dicksonben.dick...@rsp.com.au  wrote:

There was a problem fixed in Nuke 6.3v8,

Bug #23576, Segmentation Fault on Nuke exit after 
using a custom PySide
window

However I am having a similar problem in Nuke 
7.0v8, on Linux.
[...]

On 30/05/15 15:39, Fredrik Averpil wrote:

Yeah, we get this too occasionally.
lör 30 maj 2015 kl. 05:12 skrev Frank Rueter|OHUfx 
fr...@ohufx.com
mailto:fr...@ohufx.com:

Same here since Nuke 8 (on linux and osx).  Quite 
annoying.
Reported it back then



On 30/05/15 06:36, Daniel Hartlehnert wrote:

I doubt its your pipeline. I've seen it across 
many companies i
have worked for. Like i said, it only happens 
when the script was
very memory heavy. Seems to have something to 
do with freeing the
memory.

Am 29.05.2015 um 20:23 schrieb Bruno-Pierre 
Jobin:

Same on Linux. I thought it was one of our 
pipeline tools that
cause the crashing but if you are also 
experiencing this,
its probably 

[Nuke-users] run tcl in context of knob

2012-01-18 Thread Sebastian Elsner, rise|fx
Hello,
 
I am trying to run the import_discreet_lut script which comes with nuke from a
gizmo. On that Gizmo I want the user to click a tcl button. The button creates a
colorlookup and the color lookup loads a predefined lut. The import_discreet
script only works in the context of the colorlookups lut knob, but running from
another node's tcl button does not work. I have found the tcl command in which
is supposed to run a command in the context of a knob, but how would I get that
knob? This is what I have so far:
 
ColorLookup
set lookupnode [stack 0]
#missing command here to get the knob
#set lutknob [knob $lookupnode.lut] did not work 
in $lutknob {
    import_discreet_lut
}
 
Cheers
 
Sebastian 
___
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