On Sat, 23 Feb 2013 19:15:16 -0800
"J. Liles" wrote:
OK, that makes sense. Porting existing sessions would be a good first
step, but still, it sounds cumbersome. I'm not sure if it would be much
easier than starting the apps by hand.
>If we add NSM support to
In what way? I don't know much about LASH and LADISH, but I'm looking
at the jack-session api docs  right now. From what I can see, it
does everything it needs to do. There is also a GUI available in
qjackctl which I use anyway. I think that I, as a user, would be happy
with jack-session, if only my favourite apps would support it!
>Continuing support for
True, but patching to what? NSM? I like NSM but I'm not convinced that
it is "the best" possible SM. Others may think similar. Some people may
still want to support jack-session, simply because they think it is the
way to go, even if you think it is inadequate or obsolete.
You won't win everyone over to use NSM. Or *any* particular SM, for that
matter. It's cat herding. For this reason, I still think an
interoperability layer would be a good thing. If it is technically
feasible I'm not sure.
Linux-audio-dev mailing list