I just tried it with some stub files, and it looks like you're right. Have
you reported this as a bug?
In the meantime, you should be able to get around it with an onUserCreate
callback.
-Nathan
-----Original Message-----
From: [email protected]
Sent: Friday, April 19, 2013 2:06 PM
To: Nuke user discussion
Subject: Re: [Nuke-users] Nuke 7.0v3 or 7.0v1 ?
so 7.0v5 is the contender... thanks for the feedback.
Anyone aware of the file-browser issue though ? or have a custom read
node as a work around ?
thx,
Ari
No, you’re right. 7.0v6 also has at least one regression as well, though
it will only cause problems for people doing specific things with Python.
At this point, 7.0v5 seems to the best choice for a 7.0 release.
-Nathan
From: Richard Bobo
Sent: Friday, April 19, 2013 1:06 PM
To: Nuke user discussion
Subject: Re: [Nuke-users] Nuke 7.0v3 or 7.0v1 ?
Ari,
I believe that 7.0v3 was pulled from distribution with a semi-serious bug.
You should go to 7.0v4 or higher. Someone please correct me if I'm
wrong...
Rich
Rich Bobo
Senior VFX Compositor
Armstrong-White
http://armstrong-white.com/
Email: [email protected]
Mobile: (248) 840-2665
Web: http://richbobo.com/
"A man should never be ashamed to own that he has been in the wrong, which
is but saying that he is wiser today than he was yesterday."
- Alexander Pope (1688-1744) English Poet
On Apr 19, 2013, at 3:54 PM, [email protected] wrote:
We're considering rolling out Nuke 7.0v3, but I'm curious if there was
anything major which makes 7.0v1 a better choice for now ?
Also, has there been a fix to the file browser's change for numbered
files ?
ie. our proprietary file format has no prefix nor suffix, only numbered
frames. As of Nuke7's release, the file browser won't display numbered
files (sans prefix/suffix) as singular sequences. This presents a major
workflow inconvenience where the comper has to explicity set the frame
range in and out in every read node. Multiply that times over 1,700
shots
in a film... and oy.
thx,
Ari
Blue Sky
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
--------------------------------------------------------------------------------
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
