:) Great! Thanks Frank!
On Wed, Dec 18, 2013 at 2:38 AM, Frank Rueter <[email protected]> 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]> <[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 > 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 Androidhttp://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]> > <[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]> <[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]> > <[email protected]><mailto:[email protected]> <[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 > [email protected]<mailto:[email protected]> > <[email protected]>, > http://forums.thefoundry.co.uk/http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python > _______________________________________________ > Nuke-python mailing > [email protected]<mailto:[email protected]> > <[email protected]>, > http://forums.thefoundry.co.uk/http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python > _______________________________________________ > Nuke-python mailing > [email protected]<mailto:[email protected]> > <[email protected]>, > http://forums.thefoundry.co.uk/http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python > > _______________________________________________ > Nuke-python mailing > [email protected]<mailto:[email protected]> > <[email protected]>, > http://forums.thefoundry.co.uk/http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python > > _______________________________________________ > Nuke-python mailing > [email protected]<mailto:[email protected]> > <[email protected]>, > http://forums.thefoundry.co.uk/http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python > > _______________________________________________ > Nuke-python mailing > [email protected]<mailto:[email protected]> > <[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 [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 [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
