LocaliseThreaded v1.5


 
This location is for Registered Users Only.
Perhaps you need to login or register.
Contributor: Frank Rueter
Website: www.ohufx.com
This makes the built in localisation of files threaded for background processing
Requirements:
9.0, 8.0, 7.1, 7.0 or later
Linux, Mac, Windows
18 Jan 2016
552

v1.5 - fixed bug where ReadGeo nodes were not localised


 

v1.4 - adds proxy support


v1.3 - fixed a bug with Read nodes set to 'start at' or 'offset'


v1.2 - fixed a bug with one of hte logger commands (thanks Mitja for reporting it)


v1.1 - fixed bug triggered by multiple slashes in themiddle of the filre path. Added logger


LocaliseThreaded is a helper script that casues the built in localisation feature to be happening in one or more extra threads, meaning localisation can:

  • be optimised to use multiple threads (the effect of this will depend on your setup)
  • run in the background. Which means you can keep working while the localisation is happening

To activate this feature, place the file in your NUKE_PATH and add the following to your menu.py:

 

import LocaliseThreaded
LocaliseThreaded.register()

 

This will cause the built in localisation to use the custom process, the workflow remains as outlined in the docs.

 

Please login in order to download these files.

Comments   

 
0 # George Anison 2014-10-20 18:58
Thank you for this!!!

It's really useful since the Nuke's localise is very slow over the network.

By the way, I've found a minor bug: The script doesn't work when the Read node has "start at" activated.

Hope you can fix it.

Greetings.
 
 
0 # Frank Rueter 2014-10-21 00:37
Hi George, yes, I'm aware of that. I do believe though that this is a Nuke bug, or is this working for you with the default localising?
 
 
0 # George Anison 2014-11-17 00:53
Hello Frank, the default local cache from Nuke works normally setting the "start at" and doing the cache. Please, try it.
 
 
+1 # Frank Rueter 2014-11-17 01:52
oops, you are indeed right, sorry. I will have a look and update this soon
 
 
0 # Frank Rueter 2014-11-18 06:46
Hi George, I just fixed this. Let me know if you have any trouble with v1.3
 
 
0 # George Anison 2014-11-18 23:35
Thank you Frank! It works perfectly now :)
 
 
0 # George Anison 2015-04-15 12:06
Hi Frank, could it be possible to localise the proxy files with your script?
 
 
0 # Frank Rueter 2015-04-15 16:52
sure. just need to find the time to add a couple of lines for that.
will try and check it out later
 
 
0 # Frank Rueter 2015-05-10 04:34
v1.4 has proxy support now
 
 
0 # George Anison 2015-05-13 18:49
Great!!! I've been begging for that feature for years!!! Thanks Frank.
 
 
0 # Johannes Hezer 2015-08-19 15:57
Hi Frank,
thanks for this..
I have not looked at the code, but what I d love to have would be a button to say localise current Frame and or a frame range...
I ll look into this when I do have time, but maybe this is a bit complicated or you can tip me off in the right direction.
Cheers
Johannes
 
 
0 # Frank Rueter 2015-08-19 16:03
I can have a look tomorrow.
 
 
0 # Carlos Trijueque 2016-01-18 16:23
Hi Frank,

Could it be possible to have it working with the ReadGeo nodes as the default Localize does?

Thanks!
 
 
0 # Frank Rueter 2016-01-18 19:22
I see, it's throwing an error if it can't finr the Read node specific knobs. Will have a look...
 
 
0 # Frank Rueter 2016-01-18 19:36
Actually I'm only modifying the copying part itself. For collecting of knobs that should be localised I use the default nuke.localiseFiles()
I just tested it and it does not localise ReadGeo nodes. Are you using custom code for that?

I deliberately duck punched the default implementation rather than completely replacing it so everything else would work like the default.
 
 
+1 # Frank Rueter 2016-01-18 20:46
try v1.5 now
 
 
0 # Carlos Trijueque 2016-01-19 09:28
Works like a charm.

Thanks Frank!
 
 
+1 # Andrew Mumford 2017-05-23 20:27
Frank - what kind of speed up increase should I see under osX ?

I'm seeing close to half the speed of a Finder drag to desktop copy on Sierra / Nuke 10.5v3 - from a Mac / G-RAID Server using SMB 3.0 ?

Thx for any help
 
 
0 # Frank Rueter 2017-05-23 20:35
Hi Andrew, I think that would all be experimental and very dependent on your setup. The main motivation was to localise in the background rather than have to wait for a script to become responsive again.
This script is somewhat redundant now that the built in localisation happens in the background anyway.
 
 
0 # Albert Tam 2022-09-26 16:17
LocaliseThreade d seems to be about 10% slower than the native localise that comes with Nuke.

Any ideas what we could be doing wrong?

- Windows 10 Pro
- Nuke 12.2v9
 

You have no rights to post comments

We have 2789 guests and 129 members online