Hi Ron,
I don't think Howard mentioned having ~ in an autosave, he just asked
the difference between a .autosave file and ~ file. I think you
misread his first message and confusion has stemmed from there :)
Cheers,
Peter.
On 14/05/2015 15:00, Ron Ganbar wrote:
So I wonder what's
Thanks.
Hmm… bit confused…
There is only ‘~’ and ‘.autosave’ no .autosave~’
but are you saying that ‘~’ preceeds the autosave, that is, it’s a back up of
the last autosave?
H
On 14 May 2015, at 12:15, Ron Ganbar ron...@gmail.com wrote:
Far as I recall, all the nuke files ending with a
That has been known to happen to me. Not the first time.
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 Thu, May 14, 2015 at 5:07 PM, Peter Crossley cross...@thefoundry.co.uk
wrote:
Hi Ron,
I don't
If no foundry people read this on the list you can send it to support at
the foundry and I'll probably be able to answer your question just take a
little longer
On May 14, 2015 7:58 AM, Ron Ganbar ron...@gmail.com wrote:
Oh God. Beyond me, Howard.
Remembering what I was told way back when - the
Hi,
Ron is correct. Scripts ending in a tilde are backups of the existing
script. Though, they're only made once per session for a particular script.
For example if you load a fresh Nuke, open a script make some changes and
save, then a new backup will be made. However, subsequent changes/saves
But what's the logic behind this appearing in an autosave file as Howard
was asking?
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 Thu, May 14, 2015 at 4:46 PM, Babak Khataee
So I wonder what's happening with Howard's scripts.
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 Thu, May 14, 2015 at 4:59 PM, Babak Khataee
babak.khat...@thefoundry.co.uk wrote:
Oh sorry, forgot
Oh God. Beyond me, Howard.
Remembering what I was told way back when - the tilde that comes after the
.nk means what I said earlier. As it relates to autosave - I'm not sure.
Ron Ganbar
email: ron...@gmail.com
tel: +44 (0)7968 007 309 [UK]
+972 (0)54 255 9765 [Israel]
url:
Oh sorry, forgot to add that. Backups aren't made when autosaving, hence no
.autosave~, they're only made when explicitly saving a script.
On 14 May 2015 at 14:47, Ron Ganbar ron...@gmail.com wrote:
But what's the logic behind this appearing in an autosave file as Howard
was asking?
Ron
Hi
I had both ‘~’ and ‘autosaves’ in the same history of the scripts.
We auto version up when you save so in this case there were 60 versions of t he
script, but within these about 8 also had .autosaves and at least the same with
‘~’.
I’m suspecting that because Nuke9 seems somewhat flakey
Because you can be specific about what you want to delete? Instead of letting
an algorithm decide.
Am 15.05.2015 um 04:46 schrieb Marten Blumen:
What's the advantage of selecting/deleting 3d points? just use the RMS/Track
Error slider to set the threshold on the AutoTracks tab. bad ones go
Correct me if I'm wrong, but I'm fairly certain the tilde-suffixed backup files
are created by the OS, not Nuke itself.
-Nathan
From: Babak Khataee
Sent: Thursday, May 14, 2015 6:46 AM
To: Nuke user discussion
Subject: Re: [Nuke-users] script endings query
Hi,
Ron is correct. Scripts
Yes. It looks different with mov32 or mov64. I noticed on short quick times too
and even when they are generated in nuke
On 15/05/2015, at 06:23, John Stewart li...@stewartvfx.com wrote:
I am noticing on longer H.264 quicktimes read in nuke (not generated by
nuke), that the timing of the
Hello all,
I have a plate connected to a CameraTracker, and am attempting to get
a decent solve. With the camera tracker selected and connected to the
viewer, I switch into 3D view. From there, I can clearly visualize
some of the solved tracking points that are in error. What I want to
do is
Hey all,
One other contributing issue is having the CurveTreeWidget visible, so if
you shrink the Paint's panel such that the CurveTreeWidet (the strokes
list) you should see a big improvement in the performance. This has a
bigger effect on perf than having the Dope Sheet or Curve Editor open in
Good tip - thanks!
On 14 May 2015, at 17:57, Frank Harrison fr...@thefoundry.co.uk wrote:
Hey all,
One other contributing issue is having the CurveTreeWidget visible, so if you
shrink the Paint's panel such that the CurveTreeWidet (the strokes list) you
should see a big improvement in
I am noticing on longer H.264 quicktimes read in nuke (not generated by
nuke), that the timing of the clip itself changes depending on if you
use a 64bit decoder or a 32bit decoder. Anyone else ever see that?
We're on 9.0v5.
John
___
Nuke-users
Hi There,
Just wondering if anybody else has come across this ?
The rotopaint node when either the dopesheet or curve editor is visible seems
to be very unresponsive/laggy.
Windows 8 and Nuke 9.0v5
Hi Bram
I have seen similar with planar track then the dope sheet open can render the
script nearly unworkable. Close the Dope sheet in this case.
I have logged a bug (no idea number) but worth prodding support.
Might be the reason clone is nearly unusable in 9 compared to 8 too so might
test
Thanks Howard - will do
From: nuke-users-boun...@support.thefoundry.co.uk
[nuke-users-boun...@support.thefoundry.co.uk] on behalf of Howard Jones
[mrhowardjo...@yahoo.com]
Sent: 14 May 2015 17:21
To: Nuke user discussion
Subject: Re: [Nuke-users] rotopaint vs
Unfortunately nothing. It doesn't work that way. It could be so easy, but its
not :(
Am 14.05.2015 um 20:34 schrieb Ned Wilson:
Hello all,
I have a plate connected to a CameraTracker, and am attempting to get
a decent solve. With the camera tracker selected and connected to the
viewer, I
You aren't missing much. You can hope they are outside the error
threshold and tweak that down. I usually set min length to 3 (stock
setting) Max track error to 3 and max error to as low as possible and
still have enough trackers. I start at 5. If five doesn't work I start
thinking
Connect a second viewer to the same node. Have one be 2D and one 3D, then
you don't have to switch everytime you've selected a node in 2D
Den 14 maj 2015 21:02 skrev Randy Little randyslit...@gmail.com:
You aren't missing much. You can hope they are outside the error
threshold and tweak
Nice Frank! Making the Viewer full-screen and hiding the stroke list brings
it back to full speed- OsX 10.10.3, Gtx980. 9.05
On 15 May 2015 at 04:57, Frank Harrison fr...@thefoundry.co.uk wrote:
Hey all,
One other contributing issue is having the CurveTreeWidget visible, so if
you shrink the
Because sometimes the software thinks bad tracks are good so setting error
threshold isnt enough.
On May 14, 2015 10:46 PM, Marten Blumen mar...@gmail.com wrote:
What's the advantage of selecting/deleting 3d points? just use the
RMS/Track Error slider to set the threshold on the AutoTracks tab.
If the tracks are red then they are never used in the influence of the
track.
ᐧ
--
Deke Kincaid
Media Entertainment OEM Development Manager
The Foundry
Skype: dekekincaid
Tel: (310) 399 4555 - Mobile: (310) 883 4313
Web: www.thefoundry.co.uk
Email: d...@thefoundry.co.uk
On Thu, May 14, 2015 at
Far as I recall, all the nuke files ending with a tilde are
one-version-previous to the latest. So the autosave will be the autosave
previous to the one called autosave, in case the last one is corrupt.
Ron Ganbar
email: ron...@gmail.com
tel: +44 (0)7968 007 309 [UK]
+972 (0)54 255 9765
Hi
May be a dumb question but does anyone know the difference between a script
ending in
‘.autosave’ and ending in
‘~’
This may be a mac osx thing but the autosave is obvious - it’s the ‘~’ that is
not.
Just cleaning up a load of both of these left over from, I guess, crashes -
getting a
What's the advantage of selecting/deleting 3d points? just use the
RMS/Track Error slider to set the threshold on the AutoTracks tab. bad ones
go red - delete them...
On 15 May 2015 at 07:28, Daniel Hartlehnert dah...@gmx.de wrote:
Unfortunately nothing. It doesn't work that way. It could be so
29 matches
Mail list logo
