6 May
2017
6 May
'17
1:58 p.m.
Ralf Mardorf <ralf.mardorf(a)alice-dsl.net> writes:
On Sat, 06 May 2017 19:15:02 +0200, David Kastrup
wrote:
"at 3 bytes per note". I know that there are situations where 2 bytes
are sufficient but you cannot depend on it. But I'd expect chord
buttons to be able to use running status rather reliably.
But the cost for that at 3 bytes per note is just
1ms (more for
chords).
No, when using external gear running status reduces it to 2 bytes, as
long as just one MIDI channel is involved. Simply use one MIDI interface, for each MIDI channel
;).
The Roland FR-1b does not even bother to use two connectors for input
and output. They expect you to tell the Roland with a configuration
sequence when you want in- instead of output. When you do, they
keyboard is dead (it will only accept notes via Midi then) until you
reconfigure or a SysEx dump is sent. In the latter case, it will switch
the connector back to input, no questions asked.
I bought a single connector USB/Midi interface that will figure out
whether it is used for input/output on its own because I was not fond of
fiddling with plugs every time I want to work with SysEx.
1 ms as a fixed delay isn't an issue at all.
I'm very sensitive to
MIDI jitter, much more than it is expected from a "normal" human being
:D. You should use alsa-midi-latency-test to check how much MIDI
jitter you get. Very likely you get more than 1 ms of MIDI jitter.
So far I have not had any problems with the latency of sound production
using Aeolus. Problem is rather when it deadlocks and keeps producing
noise.
--
David Kastrup