11 Feb
2013
11 Feb
'13
4 p.m.
Hi,
I write to ask about session manager solutions. I use ladish for 1 year
and these days I'm trying jack-session (using qjackctl) to see how differs.
I hear about non-session but never used.
Which is, in your opinion, the best solution actually?
Here my newbie considerations:
ladish
------
pro:
- I can execute also unsupported applications (level 0)
- integrated patch UI (gladish)
- extra-features like rooms (state?)
cons:
- I need to write manually app name (command) when create a new studio
- I need to "remember" options to my applications to save presets or similar
jack-session
------------
pro:
- save the state of current jack applications, without write a single
command
cons:
- unsupported application are not executed when session is opened
- lacks of features as rooms or grouping
I know may be some of cons are about the actual UI instead of session
manager itself.
Because I use occasionally music production software, my first
requirement is to save the session in terms of connections and opened
applications, and then reopen with 1-click.
And, finally, I often like to include non-audio applications in the
session (let's say editor to annotate).
At the moment, since few applications support jack-session, I think to
continue to use ladish. But I found really boring write each time
commands application when creating a new session.
Any tips? Thanks!
Ivan
PS
I would like to use current qjackctl session-manager + a DE session
manager, but I haven't found a tool to save and open named session with
a list of current application... I'm thinking about writing myself
11 Feb
11 Feb
4:23 p.m.
On 02/11/2013 04:00 PM, Ivan Tarozzi wrote:
- unsupported application are not executed when
session is opened
Hi Ivan, this might be interesting for you:
https://github.com/fps/js_wrap
Have fun,
Flo
--
Florian Paul Schmidt
http://fps.io
4:44 p.m.
On Mon, 2013-02-11 at 16:00 +0100, Ivan Tarozzi wrote:
Hi,
I write to ask about session manager solutions. I use ladish for 1 year
and these days I'm trying jack-session (using qjackctl) to see how differs.
I hear about non-session but never used.
Which is, in your opinion, the best solution actually?
Here my newbie considerations:
ladish
------
pro:
- I can execute also unsupported applications (level 0)
- integrated patch UI (gladish)
- extra-features like rooms (state?)
cons:
- I need to write manually app name (command) when create a new studio
- I need to "remember" options to my applications to save presets or similar
jack-session
------------
pro:
- save the state of current jack applications, without write a single
command
cons:
- unsupported application are not executed when session is opened
- lacks of features as rooms or grouping
I know may be some of cons are about the actual UI instead of session
manager itself.
Because I use occasionally music production software, my first
requirement is to save the session in terms of connections and opened
applications, and then reopen with 1-click.
And, finally, I often like to include non-audio applications in the
session (let's say editor to annotate).
At the moment, since few applications support jack-session, I think to
continue to use ladish. But I found really boring write each time
commands application when creating a new session.
Any tips? Thanks!
Ivan
PS
I would like to use current qjackctl session-manager + a DE session
manager, but I haven't found a tool to save and open named session with
a list of current application... I'm thinking about writing myself
I'm still using a script to start a session, the only drawback are
settings in /home, IMO the best thing to do, is simply to copy /home to
restore a session.
A script can stop and start services, unbind devices, switch CPU
frequency scaling etc. pp. and if you start the script with killing all
apps, you easily can restore the session, once a session should hang-up
and if you like, you can add GIMP, Firefox and Leafpad to the audio
apps ;).
Regards,
Ralf
7:36 p.m.
On Mon, 11 Feb 2013 16:00:05 +0100
Ivan Tarozzi <itarozzi(a)gmail.com> wrote:
Any tips? Thanks!
Hi, I must admit I only tried briefly, long ago, ladish and
jack-session, and for one reason or another I dropped them...
recently though I've been trying out non session manager, and I must say
I really really like it:
pros:
+ it's dead simple but functional, I'd say it follows the KISS principle
+ nsm-proxy, which lets you use *any* application in a session
+ fast session switching for supported apps
+ supports session management over network
The only "cons" I could think of is that ATM *very* few apps support
it, but that isn't it's fault right?
I actually don't understand this situation, why so many support
jack-session but so little nsm (just look at [1] vs [2])? There
was a big discussion last year [3] and all the devs that took part in
the discussion, except Rui, agreed that it was the best session manager
for a variety of reasons... so why so little support for it?
cheers,
renato
[1] http://wiki.linuxaudio.org/apps/categories/jack_session
[2] http://wiki.linuxaudio.org/apps/categories/nsm
[3] http://www.linuxaudio.org/mailarchive/lad/2012/3/22/189119
8:21 p.m.
On Mon, Feb 11, 2013 at 10:36 AM, renato <rennabh(a)gmail.com> wrote:
On Mon, 11 Feb 2013 16:00:05 +0100
Ivan Tarozzi <itarozzi(a)gmail.com> wrote:
The list of programs supporting NSM is a bit longer than the linuxaudio
wiki would suggest. Still... As to the question of why so little support:
Although NSM was invented before jack-session, it was not released until
jack-session had been in the wild for some time. So jack-session got a bit
of a head start on patching. This was simply due to the complications of
life. LASH also had very few programs supporting it in its first years. To
date, NSM support was implemented by yours truly in all but one of the NSM
capable clients... I have a lot of projects and not a lot of time, so
patching other people's software has to be on the back burner. The real
issue is that session management is more of a users' problem than it is a
developers' problem, so there's historically been very limited interest
from developers in supporting any kind of SM, especially from developers of
monolithic applications. That being said, NSM is fairly well documented and
easy to implement support for, so the ball is in your court.
Even the few applications that are NSM-enabled comprise a complete studio.
Any tips? Thanks!
Hi, I must admit I only tried briefly, long ago, ladish and
jack-session, and for one reason or another I dropped them...
recently though I've been trying out non session manager, and I must say
I really really like it:
pros:
+ it's dead simple but functional, I'd say it follows the KISS principle
+ nsm-proxy, which lets you use *any* application in a session
+ fast session switching for supported apps
+ supports session management over network
The only "cons" I could think of is that ATM *very* few apps support
it, but that isn't it's fault right?
I actually don't understand this situation, why so many support
jack-session but so little nsm (just look at [1] vs [2])? There
was a big discussion last year [3] and all the devs that took part in
the discussion, except Rui, agreed that it was the best session manager
for a variety of reasons... so why so little support for it?
cheers,
renato
[1] http://wiki.linuxaudio.org/apps/categories/jack_session
[2] http://wiki.linuxaudio.org/apps/categories/nsm
[3] http://www.linuxaudio.org/mailarchive/lad/2012/3/22/189119
8:37 p.m.
I simply didn't support it, because i never see a release of NSM.
Hermann
--
Diese Nachricht wurde von meinem Android Mobiltelefon mit WEB.DE Mail gesendet.
"J. Liles" <malnourite(a)gmail.com> schrieb:
On Mon, Feb 11, 2013 at 10:36 AM, renato <rennabh(a)gmail.com> wrote:
On Mon, 11 Feb 2013 16:00:05 +0100
Ivan Tarozzi <itarozzi(a)gmail.com> wrote:
Any tips? Thanks!
Hi, I must admit I only tried briefly, long ago, ladish and
jack-session, and for one reason or another I dropped them...
recently though I've been trying out non session manager, and I must say
I really really like it:
pros:
+ it's dead simple but functional, I'd say it follows the KISS principle
+ nsm-proxy, which lets you use *any* application in a session
+ fast session switching for supported apps
+ supports session management over network
The only "cons" I could think of is that ATM *very* few apps support
it, but that isn't it's fault right?
I actually don't understand this situation, why so many support
jack-session but so little nsm (just look at [1] vs [2])? There
was a big discussion last year [3] and all the devs that took part in
the discussion, except Rui, agreed that it was the best session manager
for a variety of reasons... so why so little support for it?
cheers,
renato
[1] http://wiki.linuxaudio.org/apps/categories/jack_session
[2] http://wiki.linuxaudio.org/apps/categories/nsm
[3] http://www.linuxaudio.org/mailarchive/lad/2012/3/22/189119
The list of programs supporting NSM is a bit longer than the linuxaudio wiki would
suggest. Still... As to the question of why so little support: Although NSM was invented
before jack-session, it was not released until jack-session had been in the wild for some
time. So jack-session got a bit of a head start on patching. This was simply due to the
complications of life. LASH also had very few programs supporting it in its first years.
To date, NSM support was implemented by yours truly in all but one of the NSM capable
clients... I have a lot of projects and not a lot of time, so patching other people's
software has to be on the back burner. The real issue is that session management is more
of a users' problem than it is a developers' problem, so there's historically
been very limited interest from developers in supporting any kind of SM, especially from
developers of monolithic applications. That being said, NSM is fairly well documented and
easy to implement support for, so the ball is in your court.
Even the few applications that are NSM-enabled comprise a complete studio.
9:12 p.m.
No, just a release as NSM, without all the other NON stuff.
Sorry for been such short, didn't like to type so much on my mobile :-)
--
Diese Nachricht wurde von meinem Android Mobiltelefon mit WEB.DE Mail gesendet.
"J. Liles" <malnourite(a)gmail.com> schrieb:
On Mon, Feb 11, 2013 at 11:37 AM, brummer- <brummer-(a)web.de> wrote:
I simply didn't support it, because i never see a release of NSM.
Hermann
Can you clairify this statement? I'm not sure what you mean. Are you referring to NSM
being packaged in distributions, or...?
10:22 p.m.
On Mon, 11 Feb 2013 21:12:35 +0100
brummer- <brummer-(a)web.de> wrote:
No, just a release as NSM, without all the other NON
stuff.
Sorry for been such short, didn't like to type so much on my
mobile :-)
you mean there being a single git repository for all NON stuff? That is
rather annoying I must admit, unless there's a way to checkout only
single directories of a git repo (but I seem to recall reading on
StackOverflow this is not possible/discouraged)
renato
7:55 p.m.
On 02/11/2013 10:00 AM, Ivan Tarozzi wrote:
I write to ask about session manager solutions.
Hi Ivan,
You might be interested in this article:
http://lwn.net/Articles/533594/
It's a brief survey of Linux audio session managers, not detailed but
you might find something of interest there.
Best,
dp
11:21 p.m.
Il 11/02/2013 19:55, Dave Phillips ha scritto:
On 02/11/2013 10:00 AM, Ivan Tarozzi wrote:
Thanks a lot, Dave! Seems really interesting, and I will read with
attention.
This is exactly what I was looking for, but I was not able to found a
fresh article.
Thanks you very much :)
Ivan
I write to ask about session manager solutions.
Hi Ivan,
You might be interested in this article:
http://lwn.net/Articles/533594/
It's a brief survey of Linux audio session managers, not detailed but
you might find something of interest there.
Best,
dp
4238
days inactive
4238
days old
linux-audio-user@lists.linuxaudio.org
10 comments
7 participants
participants (7)
-
brummer- -
Dave Phillips -
Florian Paul Schmidt -
Ivan Tarozzi -
J. Liles -
Ralf Mardorf -
renato