Content-Type: text/plain; charset=ISO-8859-1
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 wrote:
> On Fri, 3 May 2013, Neil C Smith wrote:
Content-Type: text/html; charset=ISO-8859-1
JACK does not "grab" anything except *raw* MIDI =
ports and even then only if -Xraw is used, which is a bad idea to begin wit=
n Sat, May 4, 2013 at 11:06 AM, Brent Busby <email@example.com&g=
On Fri, 3 May 2013, Neil C=
On 3 May 2013 19:44, "Brent Busby" <firstname.lastname@example.org> 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 -
I checked into this, and unless I'm misunderstanding what the module do=
es, it doesn't look like it will help. =A0It seems to provide a virtual=
port for OSS apps to be able to access the Alsa sequencer ports. =A0The pr=
oblem is amidi is already a native Alsa program, but it can't access th=
e hardware ports because Jack has already grabbed them. =A0It's not an =
OSS versus Alsa issue, but just that the device is exclusively in use.
It almost seems like what we need is some kind of Jack-aware amidi command.=
+ Brent A. Busby =A0 =A0 =A0 =A0 + "We've all heard that a million=
+ Sr. UNIX Systems Admin + =A0banging on a million typewriters will
+ University of Chicago =A0+ =A0eventually reproduce the entire works of
+ James Franck Institute + =A0Shakespeare. =A0Now, thanks to the Internet,<=
+ Materials Research Ctr + =A0we know this is not true." -Robert Wilen=
Linux-audio-user mailing list