I was wondering... thread shutil, followed by nuke.localise to register in nuke. (Which is then fast)
I assume import nuke is to allow doing it all outside of Nuke? Howard > On 15 Dec 2013, at 05:14, Frank Rueter <[email protected]> wrote: > > I might be a bit dense in my allergy stricken state, what exactly do you mean? > > >> On 14/12/13 21:19, Thorsten Kaufmann wrote: >> This also sounds like a job for "import nuke" no? ;) >> Thorsten Kaufmann >> Production Pipeline Architect >> ____________________________________ >> >> Mackevision Medien Design GmbH >> Forststra?e 7 >> D-70174 Stuttgart >> >> T T +49 711 93 30 48 78 >> F +49 711 93 30 48 90 >> M +49 151 19 55 55 02 >> >> [email protected] >> http://www.mackevision.de >> >> Gesch?ftsf?hrer: Armin Pohl, Joachim Lincke, Karin Suttheimer >> HRB 243735 Amtsgericht Stuttgart >> ________________________________________ >> Von: [email protected] >> [[email protected]] im Auftrag von Frank Rueter >> [[email protected]] >> Gesendet: Samstag, 14. Dezember 2013 01:11 >> An: Nuke Python discussion; Justin Fpc >> Betreff: Re: [Nuke-python] nuke localise >> >> I have wrote my own localising script from scratch just before this feature >> was implemented. I will have a peek next week if I can quickly adapt it to >> use the localising settings in the preferences and nodes. If so it will be >> threaded and we should get the best of both worlds until the built in >> feature is more flexible to allow background processing. >> >> Sent with AquaMail for Android >> http://www.aqua-mail.com >> >> On 13 December 2013 9:58:43 PM Justin Fpc wrote: >> >> Hi all, >> >> I would be very interested if there is anyway to manage this localising in >> background. >> I've also tested to use the threading method and found the same >> problem/cause as Frank. >> >> >> Justin >> >> >> 2013/12/13 Howard Jones >> <[email protected]<mailto:[email protected]>> >> Thanks for testing. That would have stumped me. >> >> I contacted support. >> >> Howard >> >> On 12 Dec 2013, at 23:48, Frank Rueter >> <[email protected]<mailto:[email protected]>> wrote: >> >> I remember now: >> I tried this a while ago myself and failed because doLocalise() is a wrapper >> function using nuke.localiseFiles which seems to be compiled. >> Since nuke.localiseFiles takes care of the progress bar (presumably juggling >> it's own threads) it's not just a matter of using >> >> thread = threading.Thread(target=doLocalise, args=(True,)) >> >> thread.start() >> >> or >> >> >> thread = threading.Thread(target=nuke.localiseFiles, args=(readKnobList,)) >> >> thread.start() >> >> >> Both the above do the job, but you won't get the progress bar and the main >> thread is still blocked. >> >> There might be a way but I don't know how, other than basically writing the >> localisation logic yourself. >> So best to push that feature request to make nuke.localiseFiles thread-able. >> >> >> Cheers, >> frank >> >> >> >> On 13/12/13 12:15, Frank Rueter wrote: >> Yes, you should be able to. I have a quick peek... >> >> On 13/12/13 11:29, Howard Jones wrote: >> Ok done. Out of interest can this be run in a separate thread? My python >> brain hasn't got round threading, but i can run doLocalise(0) so could I >> thread it instead? >> >> Howard >> >> On 12 Dec 2013, at 22:02, Frank Rueter >> <[email protected]><mailto:[email protected]> wrote: >> >> I have asked for this in the pas as well, so please bug support to up the >> priority ;) >> >> >> On 11/12/13 05:23, Howard Jones wrote: >> Hi >> Is it possible to run localise from a shell or in the background? >> H >> _______________________________________________ >> Nuke-python mailing list >> [email protected]<mailto:[email protected]>, >> http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >> _______________________________________________ >> Nuke-python mailing list >> [email protected]<mailto:[email protected]>, >> http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >> _______________________________________________ >> Nuke-python mailing list >> [email protected]<mailto:[email protected]>, >> http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >> >> _______________________________________________ >> Nuke-python mailing list >> [email protected]<mailto:[email protected]>, >> http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >> >> _______________________________________________ >> Nuke-python mailing list >> [email protected]<mailto:[email protected]>, >> http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >> >> _______________________________________________ >> Nuke-python mailing list >> [email protected]<mailto:[email protected]>, >> http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >> >> >> _______________________________________________ >> Nuke-python mailing list >> [email protected], http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python > > _______________________________________________ > Nuke-python mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python _______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
