On Sat, Feb 23, 2013 at 9:26 PM, Devin Anderson <surfacepatterns@xxxxxxxxx> wrote:
right. this is jack2 only though, am i right?
> i do know that the coreaudio version of his new drivers *appears* to have
> some bugs too, but have not had time to investigate further.
devin, sorry, i should not have bought this up here. i don't have a solid bug report yet. just some a3 testers on OS X reporting that they appear to get double delivery of all/most incoming events from coremidi. i haven't had time to investigate it enough to consider it clearly a bug.
On Sat, Feb 23, 2013 at 12:11 PM, Paul Davis <paul@xxxxxxxxxxxxxxxxxxxxx> wrote:The '-X seq' argument does not load the 'alsarawmidi' driver. IIRC,
> devin anderson reimplemented the drivers for jack2 *only*.
>
> i am not clear on whether -X seq gets his new implementation or not.
to load the 'alsarawmidi' driver, you add '-X alsarawmidi' to the
command line *before* the audio driver arguments.
right. this is jack2 only though, am i right?
> i do know that the coreaudio version of his new drivers *appears* to have
> some bugs too, but have not had time to investigate further.
*Too*? I'm sure the software I write has a bug here and there, but
what exactly are you referring to?
devin, sorry, i should not have bought this up here. i don't have a solid bug report yet. just some a3 testers on OS X reporting that they appear to get double delivery of all/most incoming events from coremidi. i haven't had time to investigate it enough to consider it clearly a bug.
_______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
