Doepfer

Hi

> doepfer say:
> [...] The "problem" for
> this module is, that you can do a lot of different
> functions with the same module core (AD ->
> microcontroller -> DA). We don't know if we should
> make a separate module for each function or make some
> modules with similar functions (and similar controls)
> or a "monster" module with all functions (will require
> a LC display in any case to know which function is
> selected).

I'd personally would prefer several modules which are separated by 
function. Beside all technical stuff, I see several aspects:

1st) I like to have clear functionality in the handling. If I have to 
use a module that is multi purpose, I first have to look, in what mode 
is it at the moment, what function do the buttons/pots have at the 
moment, does this pot work in this mode or is it deactivated. I like 
fast access to the synth. Negative example: A112

2nd) Multifunction gear takes much longer to get on the market; function 
1, 2 and 4 are ready, but function 3 has a problem. So either the 
producer decides not to publish the module (and we will have to wait 
endlessly) or he releases a version, that has known bugs, which will 
never fixed really...

3rd) A multipurpose module will cost a lot more: more hardware; all 
development costs have to be taken over by the price for one module; 
this price will be raised, because the (already quite costy) module will 
sold not that often because of the prize and because the people do not 
want all functions (e.g. I do not need a V/Hz-2-V/Oct-Converter).
Single function modules will be cheaper because the costs of development 
will be spread over all modules, more people share those costs. More 
modules will be sold, because of lower prize and people can by exactly 
what they need.


Florian