<br><br><div class="gmail_quote">On Wed, May 12, 2010 at 11:54 AM, Pedro Lopez-Cabanillas <span dir="ltr"><<a href="mailto:pedro.lopez.cabanillas@gmail.com">pedro.lopez.cabanillas@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><div class="im">
<br>
</div>The ALSA sequencer API may be implemented in user space, offering a way to<br>
existing applications to be used with the new sequencer in a transparent way.<br>
That would be nice and consistent with our (Linux audio users) priced freedom<br>
of choice. I know that it is not the easy path, but would be consistent with<br>
the efforts of the ALSA people providing an OSSv3 compatibility API.<br></blockquote><div><br>which probably fucked up linux audio more than anything else for the last 10 years. <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Not only that, but Jack MIDI forces to the MIDI applications to always be used<br>
subordinated to an audio stream. Even when you don't want to use digital<br>
audio at all, because your MIDI sources and receivers are all external<br>
musical instruments.<br></blockquote><div><br>that's an artifact. for now, just run jackd -d dummy and fire up a2jmidid -e. no audio is flowing anywhere at all. <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Another drawback is that if you want to succeed replacing an existing API, you<br>
need to provide at least every functionality provided by the old one, and do<br>
it in a nice way that can be adopted easily by the developers. I understand<br>
that the ALSA sequencer API is huge and cumbersome, but the minimalist<br>
approach of Jack MIDI may be just another mistake in the opposite direction.<br></blockquote><div><br>if you can expand on what that direction might be, it could be useful.<br><br>there are issues that i have with the JACK MIDI concept, but they are clear and simple (and the diametric opposite of those with ALSA sequencer). specifically:<br>
<br> * ALSA sequencer is bad for synthesis because data arrives in the wrong thread at the wrong time; its good for MIDI control because the data does not arrive<br> in the RT process() thread<br> * JACK MIDI is good for synthesis because data arrives in the right thread at the right time; its bad for MIDI control because the data arrives in the<br>
RT process() thread<br><br><br></div></div>