JACK does not "grab" anything except *raw* MIDI ports and even then only if -Xraw is used, which is a bad idea to begin with.
On Sat, May 4, 2013 at 11:06 AM, Brent Busby <brent@xxxxxxxxxxxxx> wrote:
On Fri, 3 May 2013, Neil C Smith wrote:I checked into this, and unless I'm misunderstanding what the module does, it doesn't look like it will help. It seems to provide a virtual port for OSS apps to be able to access the Alsa sequencer ports. The problem is amidi is already a native Alsa program, but it can't access the hardware ports because Jack has already grabbed them. It's not an OSS versus Alsa issue, but just that the device is exclusively in use.
On 3 May 2013 19:44, "Brent Busby" <brent@xxxxxxxxxxxxx> wrote:
Is there any way to do this kind of raw Alsa access with jackd going?
You might be able to use the vir-midi module for this. I looked into this
to help someone get JACK MIDI into Praxis. Should work for output too.
Bit more about what I did here -
http://code.google.com/p/praxis/issues/detail?id=31
It almost seems like what we need is some kind of Jack-aware amidi command...
--
+ Brent A. Busby + "We've all heard that a million monkeys
+ Sr. UNIX Systems Admin + banging on a million typewriters will
+ University of Chicago + eventually reproduce the entire works of
+ James Franck Institute + Shakespeare. Now, thanks to the Internet,
+ Materials Research Ctr + we know this is not true." -Robert Wilensky
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
_______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
