200e

yahoo formatting is messing me up, i'm trying to respond inline but it could
be all wrong.


> Generally the severe lack of deeper information about the 200e/modules is
> something I am a little bit unhappy about!
>
>




sorry about that. it'd be great to have a wiki, or something, somewhere, i
don't mind starting one but not sure who would maintain it. meanwhile i
think we'll soon have digital copies of the manual on buchla.com

>
> E.G.:
> - the MIDI ports are unlabeled. With "trial and error" I "found" MIDI IN,
> the other one is...Ezra was so kind to answer my question.
> - if you upgrade the firmware version, the documentation (that I kindly got
> from JB) does not mention HOW LONG you have to press down the RE knob? 2
> sec, 2 min, 2 days...
>









you can let go as soon as the lights come on in the system. in paerticular,
the blue LED on the 292e should be going like crazy (it is an I2C bus
activity indicator.)

> - how many 210e can coexist in ONE system?
>




i can't see any reason not to have as many as you like. presets are actually
stored in each module, not in the 225e or any other centralized memory. the
225e simply sends a global message for all enabled modules to store or
recall preset X.

if your goal was to minimize the physical moving of cables, you could
certianly do that. but i think you would eventually wind up with one 210e
for each other module (the 291e has 10 cv inputs, for example!), or
something equally crazy.

that doesn't make the 210e useless... some people (like allessandro and
richard, i think) have a "core" patch with a few "variable" elements that
are rerouted using the 210e presets. this is kind of the intended purpose.

i've done extensive touring with a very small 200 system (4 panels) which
uses a 225e and 210e to reroute all my pedals and signal sources
(microphone, viola, synth, distortion, delay, stage feed, house feed,
etc.)... really really useful. hideous feedback on cue.


[Non-text portions of this message have been removed]