5 Mar
2010
5 Mar
'10
6:48 a.m.
Hi, this is a part of a previous mail,but with catchier Subject
I think LASH should be integrated into Jack, to make it mandatory for
linux audio apps. The missing LASH support is one of the main issues
disturbing me, when working with linux audio. Now I've said it, ha.
I'm thinking of having Jack require a Load/Save callback, prior to
activating the client. How feasible is that?
What do you think?
Gerald
5 Mar
5 Mar
7:06 a.m.
On Fri, Mar 05, 2010 at 11:48:11AM +0100, Gerald Mwangi wrote:
Hi, this is a part of a previous mail,but with
catchier Subject
I think LASH should be integrated into Jack, to make it mandatory for
linux audio apps. The missing LASH support is one of the main issues
disturbing me, when working with linux audio. Now I've said it, ha.
I'm thinking of having Jack require a Load/Save callback, prior to
activating the client. How feasible is that?
What do you think?
Gerald
i think this:
http://hochstrom.endofinternet.org/cgit/jack.git/tree/jack/session.h?h=jack…
--
torben Hohn
7:56 a.m.
Ah cool, is it already in the current jack release? Too lazy to look.
Gerald
On Fri, 2010-03-05 at 12:06 +0100, torbenh wrote:
On Fri, Mar 05, 2010 at 11:48:11AM +0100, Gerald
Mwangi wrote:
Hi, this is a part of a previous mail,but with
catchier Subject
I think LASH should be integrated into Jack, to make it mandatory for
linux audio apps. The missing LASH support is one of the main issues
disturbing me, when working with linux audio. Now I've said it, ha.
I'm thinking of having Jack require a Load/Save callback, prior to
activating the client. How feasible is that?
What do you think?
Gerald
i think this:
http://hochstrom.endofinternet.org/cgit/jack.git/tree/jack/session.h?h=jack…
7:52 a.m.
On Friday 05 March 2010 11:48:11 Gerald Mwangi wrote:
Hi, this is a part of a previous mail,but with
catchier Subject
I think LASH should be integrated into Jack, to make it mandatory for
linux audio apps. The missing LASH support is one of the main issues
disturbing me, when working with linux audio. Now I've said it, ha.
I'm thinking of having Jack require a Load/Save callback, prior to
activating the client. How feasible is that?
I also think that Qt should be linked into jack because most audio apps are
missing a nice gui...
<irony off>
LASH is dead. Session-handling in jack is the future. Thats why there is
currently a big discussion going on about using jacks own ipc for the session
handling of clients.
You might want to read the archives of the last days of this list and the jack
developers list...
Have fun,
Arnold
8:05 a.m.
Ok ok, I'm not always on track. Making music+ Family+ TerminatorX+ PhD
application, there's hardly time to follow the list.
By 'Integrating LASH into jack', I really ment session handling into
jack. Sorry
On Fri, 2010-03-05 at 12:51 +0100, Arnold Krille wrote:
On Friday 05 March 2010 11:48:11 Gerald Mwangi wrote:
Hi, this is a part of a previous mail,but with
catchier Subject
I think LASH should be integrated into Jack, to make it mandatory for
linux audio apps. The missing LASH support is one of the main issues
disturbing me, when working with linux audio. Now I've said it, ha.
I'm thinking of having Jack require a Load/Save callback, prior to
activating the client. How feasible is that?
I also think that Qt should be linked into jack because most audio apps are
missing a nice gui...
<irony off>
LASH is dead. Session-handling in jack is the future. Thats why there is
currently a big discussion going on about using jacks own ipc for the session
handling of clients.
You might want to read the archives of the last days of this list and the jack
developers list...
Have fun,
Arnold
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev 
8:45 a.m.
On Fri, Mar 5, 2010 at 11:51 AM, Arnold Krille <arnold(a)arnoldarts.de> wrote:
LASH is dead. Session-handling in jack is the future.
Thats why there is
currently a big discussion going on about using jacks own ipc for the session
handling of clients.
You might want to read the archives of the last days of this list and the jack
developers list...
Does any substantive Linux audio development discussion actually
happen on LAD any more?
I've only just discovered (because of your email and another pointer
to the list from LAU) that any of this session management stuff was
being discussed on jack-devel.
I don't think I've ever been subscribed to that list, at least since
it moved from SourceForge -- after all, I'm not a JACK developer. But
I am interested in session management. I've just subscribed to it,
and it looks like I have rather a lot to catch up on.
Hm.
Chris
9:43 a.m.
Hi Chris,
On Fri, 5 Mar 2010, Chris Cannam wrote:
Does any substantive Linux audio development
discussion actually
happen on LAD any more?
Yes. :-)
I've only just discovered (because of your email
and another pointer
to the list from LAU) that any of this session management stuff was
being discussed on jack-devel.
Well, when you're talking about changes to the JACK API,
that discussion belongs on Jack-Devel, doesn't it?
I don't think I've ever been subscribed to
that list, at least since
it moved from SourceForge -- after all, I'm not a JACK developer. But
I am interested in session management. I've just subscribed to it,
and it looks like I have rather a lot to catch up on.
The JACK site[1] says, "If you're doing anything with jack,
you need to be on this list."
-gabriel
[1] http://jackaudio.org/email
9:53 a.m.
On Fri, Mar 5, 2010 at 1:43 PM, Gabriel M. Beddingfield
<gabrbedd(a)gmail.com> wrote:
Yes. But the subject really is "session management for Linux audio
applications". The fact that JACK is involved is (waves hand
dismissively in manner of a Paris waiter) an implementation detail.
I've only
just discovered (because of your email and another pointer
to the list from LAU) that any of this session management stuff was
being discussed on jack-devel.
Well, when you're talking about changes to the JACK API, that discussion
belongs on Jack-Devel, doesn't it? The JACK site[1] says, "If you're doing
anything with jack, you need to be
on this list."
True enough. Though I've been doing things with JACK for many years
without ever having read that page before. And -devel lists are
usually for developers of whatever it is they're about, not users of
it.
Anyway -- really I'm just cross about missing things through my own
inertia. I suspect the real reason I'm not on that list is that I
never got around to moving my subscription there, having previously
been subscribed to the now defunct jackit-devel(a)lists.sourceforge.net.
This is the first time I've really been aware that the "new" list was
any more active than the old!
Chris
5410
days inactive
5410
days old
linux-audio-dev@lists.linuxaudio.org
7 comments
5 participants
participants (5)
-
Arnold Krille -
Chris Cannam -
Gabriel M. Beddingfield -
Gerald Mwangi -
torbenh