20 May
2008
20 May
'08
8:33 p.m.
Florian Schmidt <mista.tapas(a)gmx.net> writes:
Zero added latency for one. jackd only makes sense for inter-process delivery
of MIDI signals. For inter-machine sending of midi where the other machine
might be a hardware synth, it doesn't make sense at all to send the signal
through another daemon..
AFAIK this is just wrong, JACK ALSA MIDI backends are normal ALSA MIDI
clients, there is nowhere you get additional latency.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
I like the idea of jack midi for internal
routing between applications, especially between Sequencers and
Softsynths. It lightens the burden on softsynth and sequencer
implementers which would otherwise have to take into account all kinds of
scheduling and priorityu issues. But MIDI also has more purposes than
that..
Sure it does. But what makes ALSA MIDI more suitable for that purpose?