--- In Doepfer_a100@yahoogroups.com , Florian Anwander <fanwander@...> wrote:

>
> Hello
>
> > From the Manual: "The Midi input of MTV16 is not suitable for large
> > amounts of Midi data ... as the Midi in buffer is only 48 bytes."
> > What does this mean in practise I don't have a faintest idea how
> > much 48 bytes is in this context.
>
> Unfortunately it is not really very meaningful.
>
> Basically a MIDI-Event (e.g. one controller change, one note) consists
> of three bytes.
> The three bytes tell you
> byte 1) "what kind of data": note, controller,pitchbend...,
> byte 2) "which channel and which data", e.g.: for a note channel+C5, for
> a controller channel+Volume,
> byte 3) "which value" e.g. for note velocity=96, for control volume=122
>
>
> So you see, that the inputbuffer is able to contain the information for
> 16 controller values [*]. So if on your MIDI-cable there is not only the
> Controllerinfo for this MTV16, but also many other informations (e.g.
> Notes from your Sequencer), then the input buffer will have an overflow
> - data will be lost.
>
> So, if the MTV16 is controlled by a computer, it should be controlled
> via a dedicated MIDI-Port, which does not transfer anything else but the
> Controllers for the MTV16.
>
>
> Florian
>
>
>
> [*]If the sending device uses the so called active mode (which I won't
> explain for now), it may be up to 23 events. But still this is not very
> much.
>

Thank you Florian for your informative answer!

Based on this information I'd say that 48 bit is awfully low value.

Although I'm sure it's (barely) enough for me because I was going to use it on a separate midi port anyway.

Have to check out if it's possible in Renoise to filter out "basic" midi messages such as start/stop, bpm etc. just on one port.

- Markus