I always have to go through the save process twice, as I don't want to depend on the automated save that usine does on close. That data could get lost later if you open up another wkp, and then close usine. So I always deliberately save my wkp first. This takes about 60-90 seconds (lots of kontakt data!) so my total shutdown time is about 4 minutes. When you are in a bar praying nobody unplugs your power, this can seem very long!
I also don't use autoload, as it doesn't load the most recent version of the wkp if there was any trouble in shutdown the last time.
(But maybe this has been fixed even in the latest V4? Senso did mention shutdown times).
-e
Statistics: Posted by woodslanding — 17 Nov 2009, 21:06
]]>
Also, I don't know why it is necessary for Usine to do a lengthy save of all current patches when exiting the program, especially when I have autoload disabled?
Statistics: Posted by gurulogic — 17 Nov 2009, 20:47
]]>
I save usine very regularly, and save all my subpatches independently anyway
so I would +1 for option to turn off undo. I would leave it on, but turn it off if patching gets slow.
-e
Statistics: Posted by woodslanding — 17 May 2009, 01:00
]]>
Usine is more designed to have several small patches on the grid than a single huge patch.
.
I didn't really know that when I first started this patch. Now it's a big patch and I have tried to split it into two patches but when I cut part of the patch to paste into a new patch, not all off the interface items remember their size and position correctly so I have left it as a large patch, besides I prefer the overview for editing how I have it..
Anyways, an option to turn off off undo was just a suggestion as I usually have no use for undo and it seems to slow things down...
Statistics: Posted by gurulogic — 16 May 2009, 20:02
]]>
Also, generally it's a better approach for the maintenance of patch, like in programming stuffs : you split your routines into a collection of sub-routines, etc.
Statistics: Posted by senso — 16 May 2009, 09:11
]]>
Statistics: Posted by gurulogic — 15 May 2009, 22:31
]]>
]]>
Statistics: Posted by 23fx23 — 16 Apr 2009, 22:03
]]>
]]>
These things are just a guess, as I really don't know...The next version is supposed to come with new memory optimizations, so maybe that will help?
Statistics: Posted by gurulogic — 15 Apr 2009, 23:09
]]>
today I considerate how slow is patch with many wires versus the same structure made in c++ SDK ... its nothing new - it must be slower ... but I have rather big subpatch with many wires but very simple math modules and some array operations (+,-,abs,*,etc) it costs about 3% of CPU .. but if I multiplicate this subpatch few times everything getting very sloooow.... making every new wire is 2 seconds waiting for refreshing ... its slow (compare to max or pd)
the same structure as user module in c++ is 0.15% of cpu and i can multiplicate it how many times I need.
i now that usine is generally rather fast ... but its possible to improve performance of wires comunications? big patches can be realy slow and getting slow very fast - few subpatches are enough.
sory im not english nativespeaker
best regards
nelson
Statistics: Posted by nelson — 15 Apr 2009, 22:38
]]>