4 May
2013
4 May
'13
6:04 p.m.
Hi,
On 4 May 2013 16:06, Brent Busby <brent(a)keycorner.org> wrote:
On Fri, 3 May 2013, Neil C Smith wrote:
I was replying more in the context of JSynthLib / JavaSound as Praxis
LIVE's MIDI support is Java based. Should be the same with amidi
though if it only works with raw MIDI devices. vir-midi creates
virtual hardware devices that can be selected as outputs from programs
that only support raw MIDI, and makes them appear as ALSA devices that
you can connect via QJackCtl, etc.. If you've read the linked bug
report, you'll also notice I suggest to use a2jmidid which then makes
the virtual hardware devices appear as JACK MIDI devices.
You can try setting JSynthLib or amidi to play to one of the virtual
hardware outputs. IIRC this then loops back to the input device which
you can connect to whatever you want.
Hope that makes sense.
Best wishes,
Neil
--
Neil C Smith
Artist : Technologist : Adviser
http://neilcsmith.net
Praxis LIVE - open-source, graphical environment for rapid development
of intermedia performance tools, projections and interactive spaces -
http://code.google.com/p/praxis
OpenEye - specialist web solutions for the cultural, education,
charitable and local government sectors - http://openeye.info
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
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.