I was noticing that I was having to go into the preset list to pick the choice I wanted for SpaceF's FATCS4 Valve Insert Modules, this caused concern as I also use PsyQ, and SpaceF's bb-Synth FX, and bb-AUX FX.
All of these FX are used in multiple instances, such as the AUX buss on a mixer, an insert effect in ProWaves FX rack, etc.
Can the multiple instances share the same preset list, or should I have seperate presets lists to use with multple instances of the chosen effect.
It seems as though it works, but only one instance gets the correct choice, and others, must be chosen manually. I just want to alleviate the extra moves as I won't have time to go staring @ the LCD's @ my gig.
Inquiring Minds Wish To Know,
Preset Storage For Multiple Instances
Thanks Alfonso,
I have discovered a similar work around where I store a new name and list w/ the newly named presets.
For example, when trying to rename FATCS4 to FATCS4 ASIO 1/2, it would not accept that name due to the " ASIO " word ( Lord Forbid ) being attached to it. So I named it FATCS4 II, and FATCS4 III, etc. Now that instance searches for the newly named preset list that matched when I " saved as " in the project storage feature.
Most people here probably have no use for this, but playing live, it is important to load once, and jam away, w/o having to worry about the little tweaks that make things sound so good in Scope.
Creamware did an awesome job designing this platform, there is no equal. We are always whining about little bugs here and there, but I for one find this the most complete software / hardware package we will probably ever see.
I had a trouble free rig up until the VST format was introduced, and since find myself fixing more and more things, when I should be playing or composing.
No other application I ever used had so much finess, and attention payed to details. They don't make them like that anymore, anywhere.
Be Free, Be Modular,...............Oxyde has become a new lead axe w/ so much motion, and FATNESS.
Thanks Again,
I have discovered a similar work around where I store a new name and list w/ the newly named presets.
For example, when trying to rename FATCS4 to FATCS4 ASIO 1/2, it would not accept that name due to the " ASIO " word ( Lord Forbid ) being attached to it. So I named it FATCS4 II, and FATCS4 III, etc. Now that instance searches for the newly named preset list that matched when I " saved as " in the project storage feature.
Most people here probably have no use for this, but playing live, it is important to load once, and jam away, w/o having to worry about the little tweaks that make things sound so good in Scope.
Creamware did an awesome job designing this platform, there is no equal. We are always whining about little bugs here and there, but I for one find this the most complete software / hardware package we will probably ever see.
I had a trouble free rig up until the VST format was introduced, and since find myself fixing more and more things, when I should be playing or composing.
No other application I ever used had so much finess, and attention payed to details. They don't make them like that anymore, anywhere.
Be Free, Be Modular,...............Oxyde has become a new lead axe w/ so much motion, and FATNESS.
Thanks Again,