This is probably because the Jacksession version would need to
maintained in a seperate branch, and so we'd have 3 versions of jack
to deal with.
I tested jacksession, and it works well. (Using the experimental branch)
As Torben says, there's minimal intrusion in apps, and importantly
minimal change to the jack API.
I'm sorry to see it stop, but Torben's been driving this forward, as a
practical opportunity for users, and not just a lot of discussion, and
if he feels the politics (and i think that is what's at the heart of
this) of doing this outweighs the positive benefits, then i can hardly
blame him for freezing it indefinitely or otherwise. Why keep bashing
your head against the wall?
If he decides to pick this up again, and take it further, then i'm
willing to continue testing, as i see jacksession as the simplest,
most elegant, and least intrusive session management system i've seen
to date. That's i guess, the best we can do for now.
The users will have to wait, find another way, or just accept it's not
going to happen.
On Mon, Dec 21, 2009 at 8:54 AM, Patrick Shirkey
Linux-audio-dev mailing list