multithreaded workspace loading?
unfortunately not, it's a limitation of the system (osx, win).
Loading and creation of graphical object, plugs, etc, can only be done in the what we call 'the main thread' which is by definition single threaded.
I can't do anything to improve this bottleneck.
The only solution is to send a feature request to Apple or Microsoft?:D
But don't expect miracles before osx 15 or Win 19....
Loading and creation of graphical object, plugs, etc, can only be done in the what we call 'the main thread' which is by definition single threaded.
I can't do anything to improve this bottleneck.
The only solution is to send a feature request to Apple or Microsoft?:D
But don't expect miracles before osx 15 or Win 19....
Olivier Sens
www.brainmodular.com
www.brainmodular.com
Just because I am never satisfied with a simple answer
I have been googling for more information about this subject but cannot seem to find much info on the subject. Any suggestions where I can can find info to satisfy my curiosity?
I did find this discussion which is not directly relevant http://stackoverflow.com/questions/3055 ... -windows-7
but a couple of comments made me wonder if something along these lines would be a possible workaround if programmed in Usine?
"A classic case is operating on sequential data in a big data file. Split the file into 4 smaller files, run the program 4 times, and you're done in 15 minutes instead of an hour"
"The most you could do (if relevant in your case) to better use your CPU is to slice your input into N chunks, and run the program multiple time on each chunk, then do something to combine the inputs once they are all done"
Another thing I know I mentioned elsewhere in the forum but I'll repeat, is an option for quick program exit would be nice (apart from the brutal seeming task manager process kill)
In my large workspace, it takes about the same time to close HH as it does to load my workspace. In a situation as I experienced first hand last weekend on stage, I setup all my gear on stage, launched HH, launched my workspace and of course as murphy's law would have it, had some strange never before seen issue with my sound card not properly initializing so had to close HH, reboot my computer and lauch HH/workspace again, the whole process taking about 5 min despite my fast OS boot with SSD. Fortunately the DJ playing before me was able to continue to avoid interruption but regardless anything to speed up this process would be greatly welcome. Perhaps in this scenario I should consider a force quit of the Usine process? (would have been setup sooner but it took longer than expected to setup all equipment and get the rear speakers in place for surround, 1hr setup time in total!)
I did find this discussion which is not directly relevant http://stackoverflow.com/questions/3055 ... -windows-7
but a couple of comments made me wonder if something along these lines would be a possible workaround if programmed in Usine?
"A classic case is operating on sequential data in a big data file. Split the file into 4 smaller files, run the program 4 times, and you're done in 15 minutes instead of an hour"
"The most you could do (if relevant in your case) to better use your CPU is to slice your input into N chunks, and run the program multiple time on each chunk, then do something to combine the inputs once they are all done"
Another thing I know I mentioned elsewhere in the forum but I'll repeat, is an option for quick program exit would be nice (apart from the brutal seeming task manager process kill)
In my large workspace, it takes about the same time to close HH as it does to load my workspace. In a situation as I experienced first hand last weekend on stage, I setup all my gear on stage, launched HH, launched my workspace and of course as murphy's law would have it, had some strange never before seen issue with my sound card not properly initializing so had to close HH, reboot my computer and lauch HH/workspace again, the whole process taking about 5 min despite my fast OS boot with SSD. Fortunately the DJ playing before me was able to continue to avoid interruption but regardless anything to speed up this process would be greatly welcome. Perhaps in this scenario I should consider a force quit of the Usine process? (would have been setup sooner but it took longer than expected to setup all equipment and get the rear speakers in place for surround, 1hr setup time in total!)
Interesting subject, so regarding would it be an improvement to have a faster GPU as well as GPU dedicated memory? I do see a greater improvement using a new DX11 graphics card with faster GPU and 2GB memory than I did before on my 1GB DX10 card. I was unsure if it was specific to the DX support causing issues.
I believe a lot of us has run into bottlenecks before regarding HollyHock and after awhile I noticed graphical performance at some point was more heavily dependent, so quite possibly gurulogic although you have a fast SSD and CPU as I do...maybe you are having some bottleneck performance on the GPU side? Just a thought as I have ran into issues before.
I have several other systems, AIO, tablets, and laptops which have decent processing and ram, however lack on the GPU and in the end my primary studio computer seems to always outperform with the upgraded GPU. Also have you updated to 1.1.008m yet, I have noticed over the last several updates my load and unload times were much faster on my main computer. On the others they still take a while.
-S
I believe a lot of us has run into bottlenecks before regarding HollyHock and after awhile I noticed graphical performance at some point was more heavily dependent, so quite possibly gurulogic although you have a fast SSD and CPU as I do...maybe you are having some bottleneck performance on the GPU side? Just a thought as I have ran into issues before.
I have several other systems, AIO, tablets, and laptops which have decent processing and ram, however lack on the GPU and in the end my primary studio computer seems to always outperform with the upgraded GPU. Also have you updated to 1.1.008m yet, I have noticed over the last several updates my load and unload times were much faster on my main computer. On the others they still take a while.
-S
"Every act of creation is first an act of destruction." -Picasso
see the 'QUIT' command here:is an option for quick program exit would be nice
http://www.sensomusic.com/wiki2/doku.ph ... en_strings
ps 1:
If you carefully in MSWord you'll notice that loading a big document is single threaded... I can't do better than Microsoft ...
ps 2:
Usine is actually one of the best audio soft for multithreading implementation. ie: loading a patch without glitch while the audio engine is on...
Olivier Sens
www.brainmodular.com
www.brainmodular.com
Thanks! I especially find the last tip on that page very usefulsenso wrote:see the 'QUIT' command here:is an option for quick program exit would be nice
http://www.sensomusic.com/wiki2/doku.ph ... en_strings
And yes, I do for the most part find Usine quite multicore efficient so no complaint here, but now that we can create huge workspaces in 64 bit Usine, it definately highlights the bottlenecks in my system..
Who is online
Users browsing this forum: Google [Bot] and 9 guests
