[sdiy] Re: Why MIDI?

[Paul Maddox]

Mr Cheater,

> I wish we could have digitized audio, digitized control voltages, control
messages,
> files, time sync, samples, service messages, all running through one
cable.
> It's a nice wish.

like I say, you can, but perhaps you chose to ignore my comments?

> turning a midi knob = step step step step crack step

not something I've experienced, but then most people I know who use Midi 2
CV converters use them for playing their modular from a keyboard. this
hardly needs 16bit resoloution.

> > OK, now MIDI over USB is appearing, but it is too little too late and
> > still has a number of things to address so it can be bundled on the same
> > sinking ship, OK? ;O)
> >
>
> It requires you to have a computer.

MLan doesn't....

> Making a 20-meter USB cable?
> Pre-installing a USB cable for later gig purposes?
> I'm feeling nauseous again.

MLan.

> > * Support for continous time signals
>
> What do you mean by that?

<ROFLMAO>

> Yes - for e.g. sending samples to a rig while playing. You don't want
swapping samples
> to crap up your performance.

MLan.

> Again, same goodies bag as CV.

Don't think MLan goes to 192Khz yet, but 48Khz is a pretty good start..
Far better than 31.25Kbaud.

> I'd go for arbitrary topologies - so you can just hook anything up to
anything
> and it *just works*. Don't want to end up using hubs or any crap like
that.

MLan.

> > * Support hot-swap integration of devices
>
> Yes!

MLan.

> > * Support for auto-investigation of new devices
>
> Yes!

yawn, I'm not typing it again.

> My thoughts -

My thoughts, go and and read up on MLan, it seems to address all your
concerns.

Paul