Hi Frank

I have had the same experience. I thought the new localisation would be 
awesome, but it was working better in Nuke9.
I have resorted to turn off the auto-localisation and I have made keyboard 
shortcuts to turn it on/off on selected nodes. And another shortcut to reload 
all read nodes.

That seems to work better, at least in a comp environment. I’m not sure how 
well it works in the timeline. 
Basically each time I want to check the local cache is up to date, I turn it 
off then on again and it re-localises the files. Then I press the reload all 
Read nodes to clear the buffer and voila!

I’m hoping for a functioning localisation in the next release, fingers crossed!
here’s what I have in my menu.py


def localOff():
    for i in nuke.selectedNodes('Read'):
        p = i['localizationPolicy']
        p.setValue(2)
        
    for i in nuke.selectedNodes('DeepRead'):
        p = i['localizationPolicy']
        p.setValue(2)
        
    for i in nuke.selectedNodes('ReadGeo'):
        p = i['localizationPolicy']
        p.setValue(2)

def localOn():
    for i in nuke.selectedNodes('Read'):
        p = i['localizationPolicy']
        p.setValue(0)
        
    for i in nuke.selectedNodes('DeepRead'):
        p = i['localizationPolicy']
        p.setValue(0)
        
    for i in nuke.selectedNodes('ReadGeo'):
        p = i['localizationPolicy']
        p.setValue(0)        
            
menubar.addMenu("Cache").addCommand("set selected nodes localization OFF", 
'localOff()', "F1")
menubar.addMenu("Cache").addCommand("set selected nodes localization ON", 
'localOn()', "F2")



def reload():
    for node in nuke.allNodes():
        if node.Class() == "Read":
            node.knob("reload").execute()
        if node.Class() == "DeepRead":
            node.knob("reload").execute()
        if node.Class() == "ReadGeo":
            node.knob("reload").execute()

menubar.addMenu("Cache").addCommand("reload all Read", 'reload()', "F6")




> On 22/05/2016, at 16:36, Frank Rueter|OHUfx <fr...@ohufx.com> wrote:
> 
> Hi all,
> 
> I had hoped that in Nuke/Hiero/NukeStudio/blabla v10 the localisation would 
> be fixed in away that Nuke would recognise if the original clips have 
> changed, but it doesn't seem to be the case.
> I am constantly updating clips in Nuke that already live in the timeline 
> (Hiero), and once I localise the clips, Hiero won't look at the updated 
> original files on the server ever again. F5, F8, nothing works other than 
> manually deleting the localised files.
> Am I missing something or is this actually still not workable?
> 
> I find this not just frustrating but rather dangerous, as you are looking at 
> temporary (localised) files and may approve them, when in reality the files 
> on the server that will be delivered to the client may be entirely different.
> 
> Anybody else?
> I'm on Centos 7
> 
> Cheers,
> frank
> 
> -- 
> <ohufxLogo_50x50.png> <http://www.ohufx.com/> vfx compositing 
> <http://ohufx.com/index.php/vfx-compositing> | workflow customisation and 
> consulting 
> <http://ohufx.com/index.php/vfx-customising>_______________________________________________
> 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

Reply via email to