JMTCW.
Obviously we need to hear from Mr Bowen about what is possible, but multitimberality is a massive dsp power leap!
AFAIK you are talking about duplicating the entire engine by X parts! (or at least sub dividing the dsp dynamically).
And the Creamware card Solaris version already has more oscillator and filter types "simultaneously" than anything else on the planet imho, and the keyboard will have even MORE!
I don't see much use for the cz101 style 1 midi channel per note, either
From my simplistic view, one of the things that makes the Solaris exciting and different is that you can mix and match and blend and merge from several different classes of synthesis, all within the same box. i.e. what happens if you put a prophet oscillator through a moog filter...
(Oversimplifying and being inaccurate just for clarity,) it's like layering keyboards from different brands, all from within one single box.
I'm also confused why you need multitimberality. AFAIK this isn't meant to be a workstation with drums or piano or rompler? There are several of those on the market.
For studio use, surely you can track (record) the parts?
For live use, I see it needing
"zoning" more than multitimberality. i.e. 4 zones (i.e. 2 splits with 2 layers each, or 4 splits, etc.). You only have two hands right ?
Obviously it isn't! But for comparison if you look at the power inside an Creamware ASB or Klang box (ie a single prophet 5 - also not multitimberal either btw, with 12 note poly, probably effectively a 4 chip dsp?
The Noah, I believe a 6 dsp device, could have different instruments loaded, but how many simultaneously? What was its polyphony? How multitimberal was it?
Now we have a device that takes up 6 dsps for 3~4 notes of a single dsp card! Erm... multitimberal and with what polyphony?
I don't see it as being multitimberal out of cost practicality. I doubt this will be a huge production run and AFAIK there's no large corporate to cover the production costs as it is.
What I'm keen to see though, is a practical zoning solution and I feel this needs to go in from day 1, as tacking it on afterwards would be a mare.
So the question is what you guys "need"?
AYK there are several types of oscillator in the Solaris.
What I see as useful and practical and easy (ish) to implement in v1 is a way to zone each of those oscillator types.
Naturally there is whatever sharing of the post oscillator circuits (envelopes, filters, effects, outputs, etc.) but at least with zoning, we can play a bass sound with a left hand split, layer two tones in the middle and have a lead sound on the right split.
For sequencing, effectively you have several textures available within the 1 patch. Certainly enough to compose, and then go to a dedicated mode for full patch power per phrase!?
AYPK making hardware these days is getting pretty risky. When an "independent" developer does it, (albeit with the help of a small manufacturing company) you should appreciate what's going on here.
In commercial/business terms, it's pretty amazing AFAIC
I hope what we're all agreed on is quality not quantity and also the uniqueness of the John Bowen architecture.
I pray for zoning, but I think multitimberality is pushing the boat too far.
So I'm keen that the "zoning" is built-in if that works for you guys too?
So the only point of my post, how would you like to see the zoning work (if even that is possible)?
JMTCW.
Proud owner of Scope Solaris, Orion and RD Drums.
