17 Feb
2013
17 Feb
'13
12:55 a.m.
On Fri, Feb 15, 2013 at 01:46:03PM -0800, J. Liles wrote:
On Fri, Feb 15, 2013 at 12:22 PM, Paul Davis
<paul(a)linuxaudiosystems.com>wrote;wrote:
<snip>
I think that would be a great idea...
One step further, one could even have an extra layer on top of
jack that would allow alsa sequencer clients to run on top of
jack (alsa sequencer emulation).
If I remember well, Paul said something in a paper about push models
on top of pull models being a lot more viable than the other way round.
Maybe it's a silly idea, and I don't know how huge the technical
challenge would be. And maybe it defeats the purpose of jack (to educate
us !!!), and breeds a whole new generation of lazy programmers, that
just want to throw lots of midi events at jack.
But it would be really nice to get rid of the jack and alsa midi distinction.
Greets,
lieven
nobody has ever stepped up to write a library based on JACK MIDI that
would do "MIDI sequencing" in the sense of your "deliver this event at
time
T where T is arbitrary". nothing is stopping anyone from doing that.
FWIW I have the embryo of such a library in Non-Sequencer and eventually
plan to have it separate enough to be used as an engine for other
sequencers. Others have also talked about doing something similar--but in
Python. I believe there's a workingish prototype.