No, just doLocalise() ...either 0 or 1 depending on whether it's selected or all...
On 26 December 2013 18:42, Frank Rueter <[email protected]> wrote: > Hm, interesting. Does the script editor print 'copying on windows' when > you try to run it? > > > > > On 27/12/13 07:14, Michael Garrett wrote: > > Hi Frank, > > Jut got back in front of the coal face. > I'm getting the same issue as Holger, the paths are being created on my > local cache volume but the copying isn't happening. Like him, I'm on Win 7 > (Enterprise SP1) > > Hopefully it's a quick fix! > > Michael > > > > > On 21 December 2013 19:39, Frank Rueter <[email protected]> wrote: > >> Ok, thank for the heads up Howard. >> >> >> >> On 21/12/13 23:26, Howard Jones wrote: >> >>> Hi Frank >>> >>> It could have been that but I cant confirm, as it worked since. I use a >>> tool to set up reads in one go and part of it is to set up cache to always >>> then run localise. >>> >>> I could easily have not used the tool, when testing in which case what >>> you describe may have been the case. >>> >>> Are you saying though that it goes through the motions if it shouldn't >>> cache? >>> >>> I cant confirm now until New Year. Not going to be any where near a Nuke >>> til then, yaye! >>> >>> >>> Howard >>> >>> On 21 Dec 2013, at 01:07, Frank Rueter <[email protected]> wrote: >>>> >>>> Holger, Howard: >>>> are you sure you have your caching preferences set up properly? >>>> The only time I can reproduce what you are describing is when my "auto >>>> localise from" knob in the preferences is not set up to properly to include >>>> the existing Read nodes ni the localisation process (or if the nodes in >>>> question are set to never cache). >>>> >>>> Otherwise it works on linux and osx for me (don't have windows). >>>> Could you please confirm? >>>> >>>> Cheers, >>>> frank >>>> >>>> >>>> On 21/12/13 13:43, Frank Rueter wrote: >>>>> Are there any errors in the terminal when you try to localise? >>>>> >>>>> On 21/12/13 03:30, Howard Jones wrote: >>>>>> Ah - that's what I saw too - thought it was user error. (Mac) >>>>>> >>>>>> >>>>>> On 20 Dec 2013, at 14:26, Holger Hummel|Celluloid VFX < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>> hey Frank, >>>>>>> >>>>>>> i just tried this briefly on one of our Windows (7, 64bit) machines. >>>>>>> but unfortunately it's not copying any files. it creates all the >>>>>>> subfolders in the localise folder >>>>>>> and the progess bar does what it should, it progresses. but insanely >>>>>>> fast - due to the fact >>>>>>> that it does not actually copy any files. >>>>>>> >>>>>>> cheers, >>>>>>> Holger >>>>>>> >>>>>>> >>>>>>> Frank Rueter wrote: >>>>>>> >>>>>>>> and here is the file actually attached >>>>>>>> >>>>>>>> On 18/12/13 17:36, Frank Rueter wrote: >>>>>>>>> Here is an updated version that implements a bunch of suggestions >>>>>>>>> from this thread. >>>>>>>>> This supports stereo and offers to use 1-4 concurrent threads for >>>>>>>>> the file copying. >>>>>>>>> >>>>>>>>> This is ignoring the setting for disk cache size in the >>>>>>>>> preferences, so be clean up after yourself ;). >>>>>>>>> It'd be great to get some feedback on this so I can throw it up on >>>>>>>>> Nukepedia if it works for everybody. >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> frank >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On 16/12/13 21:29, Frank Rueter wrote: >>>>>>>>>> Hola everybody, >>>>>>>>>> >>>>>>>>>> I had a quick look at this this morning and realised I would have >>>>>>>>>> to re-write everything from scratch - but then couldn't resists :-D. >>>>>>>>>> Could some of you test the attached file and tell me how you get >>>>>>>>>> on? >>>>>>>>>> Just put it into your NUKE_PATH and put this into your menu.py: >>>>>>>>>> >>>>>>>>>> import LocaliseThreaded >>>>>>>>>> LocaliseThreaded.register() >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> This will replace the default localising behaviour with a >>>>>>>>>> threaded one. >>>>>>>>>> The maximum threads are half of your Nuke threads (nuke.THREADS) >>>>>>>>>> at the moment (I will make this a preference though). There will be >>>>>>>>>> info >>>>>>>>>> about concurrent threads in the progress bar as it does it's thing. >>>>>>>>>> >>>>>>>>>> It's work in progress at this stage but since my day is coming to >>>>>>>>>> an end, I thought it would be good to get it out there for a test >>>>>>>>>> run, so I >>>>>>>>>> know more in the morning. >>>>>>>>>> >>>>>>>>>> Things I still need/want to do: >>>>>>>>>> >>>>>>>>>> * support split file knobs for stereo projects >>>>>>>>>> * support proxy knobs (should I, not sure if the default >>>>>>>>>> does?) >>>>>>>>>> * refactor the code so that multiple threads can tackle the >>>>>>>>>> same >>>>>>>>>> read node (at the moment one Read node is allocated one >>>>>>>>>> task) >>>>>>>>>> * benchmark the copy function (currently shutil.copy2). Pretty >>>>>>>>>> sure it's not the fastest one for large files and I might >>>>>>>>>> have >>>>>>>>>> to roll my own to speed things up. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Let me know how it works, especially if you are on windows as I >>>>>>>>>> can't test that here. >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> frank >>>>>>>>>> >>>>>>>>>> P.S.: If somebody is an expert with python threading with a >>>>>>>>>> little bit of time on their hands, get in touch, I'm pretty sure the >>>>>>>>>> way >>>>>>>>>> I'm doing this can be optimised, especially for trying to dynamically >>>>>>>>>> allocate threads to efficiently deal with outstanding tasks. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 14/12/13 23:23, Howard Jones wrote: >>>>>>>>>>> I was wondering that. It was going to be my next question >>>>>>>>>>> (honest) >>>>>>>>>>> >>>>>>>>>>> Howard >>>>>>>>>>> >>>>>>>>>>> On 14 Dec 2013, at 08:19, Thorsten Kaufmann < >>>>>>>>>>>> [email protected]> 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 <%2B49%20711%2093%2030%2048%2078> >>>>>>>>>>>> F +49 711 93 30 48 90 <%2B49%20711%2093%2030%2048%2090> >>>>>>>>>>>> M +49 151 19 55 55 02 <%2B49%20151%2019%2055%2055%2002> >>>>>>>>>>>> >>>>>>>>>>>> [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 >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>> >>>>>>> -- >>>>>>> Holger Hummel - [email protected] >>>>>>> >>>>>>> Celluloid Visual Effects GmbH & Co. KG >>>>>>> Paul-Lincke-Ufer 39/40, 10999 Berlin >>>>>>> phone +49 (0)30 / 54 735 220<%2B49%20%280%2930%20%2F%2054%20735%20220> - >>>>>>> [email protected] >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>> >>>> _______________________________________________ >>>> 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 >> > > > > _______________________________________________ > Nuke-python mailing [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
