Florian Schmidt <mista.tapas@email-addr-hidden> writes:
>> > 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?
>
> 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>
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
This archive was generated by hypermail 2.1.8 : Wed May 21 2008 - 04:15:03 EEST