Okay a few questions for a smooth recital.

[joojoo1234]

1. If you install a new version or copy in Usine. And pull the workspace from one to another new version or not. Does it put the patches in the new version or copy of the same version or is it pulling these patches from the old folder.

2. I had an occasion where it brought up in Absynth the wrong patch... what does usine do with absynth does it bring up patches or banks - what is the best way to organize this for smooth operation and minimum cpu - do extra patches your not using use the cpu much? I have store the absynth pane (as normal) and then I have a save function on top by the windows top bar? Whats the difference (does usine want one or the other?)

3. I am getting ocassional stops - or sometimes - due to cpu use. I have cloned and not copied. Do user curves use cpu - are they costly? Should I eliminate break points?

4. I am dismayed by the way Usine brinks up my workspace. Is it the workspace I just left or did I contaminate the fresh patch or is this to my benefit. I want the program to load a blank and then I manually choose my workspace.

5. I wish usine had an automatic program just like creative that would say speaker left front speaker left back... so I could hook up cables without second guessing and such. I guess I will make that myself.

6. It seems like patches move around in the sequencer window... I am speaking of their endings. Does Usine sometimes grade on a curve so to speak and place them slightly different? Can I snap them in the window?

I will read the manual again but could you one by one answer these as breifly so as not to take to much of your time. That time when it loaded the wrong absynth patch after over and over again doing it right was bizarre. Does the patch need to be in one specific place. Give me some tips on cpu usage.
Thanks. This program makes electronic music interesting to me when in general it doesn't.

[joojoo1234]

One thing that would be incredibly helpful is - for the live patch or for specific patches or modules what are those specific things that are cpu costly - would limiting the range of pitch help or the length of something or the rate of cycle.... you know what I mean. I like this.

[bsork]

I can't comment on much of this, but as for 4., you can choose whether to load the last used workspace in Setup/Interface. It's the autoload switch. If you have it turned on and quit normally the last time, it should bring up the workspace as it looked when quitting.

As for 1., I think it's wise to have your own creations in seperate folder(s).

[joojoo1234]

Well I got the computer to not stumble by eliminating half the random small files it was bring up in one patch - didn't matter much and I disabled my local internet connection inside my computer so no hidden program could spin... think I have some junk on this - its so hard to keep off... it worked.
I am on a x2 3800 amd - will bump the ram to 2 gig later. Hey would it speed things up much if certain files were on another drive? I am running xp home.

[senso]

thanks for feedbacks

1. If you install a new version or copy in Usine. And pull the workspace from one to another new version or not. Does it put the patches in the new version or copy of the same version or is it pulling these patches from the old folder.

I'm not sure I understand! Patches and wks files can be considered as a normal files, like if it was a .doc in Office. Copy, move, duplicate files as you want on your hard disk.

2. I had an occasion where it brought up in Absynth the wrong patch... what does usine do with absynth does it bring up patches or banks - what is the best way to organize this for smooth operation and minimum cpu - do extra patches your not using use the cpu much? I have store the absynth pane (as normal) and then I have a save function on top by the windows top bar? Whats the difference (does usine want one or the other?)

I don't use Absynth so I cant respond precisely, but on VST Usine loads patches (not banks)

3. I am getting ocassional stops - or sometimes - due to cpu use. I have cloned and not copied. Do user curves use cpu - are they costly? Should I eliminate break points?

In computers domain, everything has a cost! And User curves are calculated with a 64 bit precision. It can cost CPU if you have a lot of points.

4. I am dismayed by the way Usine brinks up my workspace. Is it the workspace I just left or did I contaminate the fresh patch or is this to my benefit. I want the program to load a blank and then I manually choose my workspace.

You have an option in the setup called 'auto load at startup'; Disable it if you want.

I will read the manual again but could you one by one answer these as breifly so as not to take to much of your time. That time when it loaded the wrong absynth patch after over and over again doing it right was bizarre. Does the patch need to be in one specific place. Give me some tips on cpu usage.
Thanks. This program makes electronic music interesting to me when in general it doesn't.

I don't know how are you wkp but with my dual core 2.0GHz 2 GB memory I'm never really limited because:
- generally I use a wkp per tune, if it's possible and If I have time to load them on stage.
- with VST I try to find compromise between quality and CPU; If I only need a sinus synth I take a small VSTi. I use FreeVerbToo as my main reverb for live (2%CPU). etc...

It's very important for us to have feedback. But don't forget that sensomusic is a very small team and we try to spend most of time in development!

[senso]

Hey would it speed things up much if certain files were on another drive? I am running xp home.

Put your files in the fasted drive?

[joojoo1234]

Thanks for answering.
Real briefly - what I was saying when you load a wkp from one usine install with another usine install and save it in the new usine install does it copy patches in the new usine folder or does it pull over waves and patches from the old install when you reload it.... this may be dumb but I am learning and pressed for time this week. Regardless - it is working good and I like this program alot.