11 Aug
2011
11 Aug
'11
3:42 p.m.
In the tradition of releasing (or at least announcing)buggy, mostly
untested software, here's:
js_wrap - a simple wrapper for non Jack-Session aware apps whose state
can be fully specified by their commandline
Use
js_wrap -- gnome-terminal
if you want to get a gnome terminal in your jack_session.. Or
js_wrap -- a2jmidid
if you want to have the alsa to midi bridge in your jack_session..
Get the software via copy and paste of the following commands:
git clone https://github.com/fps/js_wrap
cd js_wrap
mkdir bld
cd bld
cmake ..
cd ..
make -C bld
sudo make install
and get to fixing bugs ;D
In my experiments it worked just fine with gnome-terminal though there
are some errors and the code is pretty much copy-pasta'd from
lash_wrap... So expect breakage and panic and hilarity which will ensue..
Always use condoms,
Flo
11 Aug
11 Aug
3:49 p.m.
On 08/11/2011 05:42 PM, Florian Paul Schmidt wrote:
In the tradition of releasing (or at least announcing)buggy, mostly
untested software, here's:
js_wrap - a simple wrapper for non Jack-Session aware apps whose state
can be fully specified by their commandline
Use
js_wrap -- gnome-terminal
if you want to get a gnome terminal in your jack_session.. Or
js_wrap -- a2jmidid
if you want to have the alsa to midi bridge in your jack_session..
Get the software via copy and paste of the following commands:
git clone https://github.com/fps/js_wrap
cd js_wrap
mkdir bld
cd bld
cmake ..
cd ..
make -C bld
sudo make install
sudo make -C bld install
Sorry
and get to fixing bugs ;D
In my experiments it worked just fine with gnome-terminal though there
are some errors and the code is pretty much copy-pasta'd from
lash_wrap... So expect breakage and panic and hilarity which will ensue..
Always use condoms,
Flo
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
12 Aug
12 Aug
9:29 a.m.
New subject: [LAD] [ANN] WIP - JS-Wrap
> js_wrap - a simple wrapper for non Jack-Session
aware
Cool. lash_wrap has been a very useful tool, I'm glad to see a jack session
wrapper.
As far as naming, too bad js usually stands for javascript (maybe
jsession_wrap or something like that would have been a clearer choice). I
almost skipped the announcement because of this :)
-- Dan
9:56 a.m.
On 08/11/2011 05:49 PM, Florian Paul Schmidt wrote:
On 08/11/2011 05:42 PM, Florian Paul Schmidt wrote:
Thanks for your work. If Qjackctl will support JackSessions infra
clients, it will provide the same functionality I think. Qjackctl can be
used without condoms, so that's an obvious advantage.
Regards,
\r
In the tradition of releasing (or at least announcing)buggy, mostly
untested software, here's:
js_wrap - a simple wrapper for non Jack-Session aware apps whose
state can be fully specified by their commandline
Use
js_wrap -- gnome-terminal
if you want to get a gnome terminal in your jack_session.. Or
js_wrap -- a2jmidid
if you want to have the alsa to midi bridge in your jack_session..
Get the software via copy and paste of the following commands:
git clone https://github.com/fps/js_wrap
cd js_wrap
mkdir bld
cd bld
cmake ..
cd ..
make -C bld
sudo make install
sudo make -C bld install
Sorry
>
> and get to fixing bugs ;D
>
> In my experiments it worked just fine with gnome-terminal though
> there are some errors and the code is pretty much copy-pasta'd from
> lash_wrap... So expect breakage and panic and hilarity which will ensue..
13 Aug
13 Aug
6:46 p.m.
On 08/12/2011 11:55 AM, rosea grammostola wrote:
On 08/11/2011 05:49 PM, Florian Paul Schmidt wrote:
Makes me wondering, is this tool doing anything 'nasty' in the view of
JackSession developers, for either apps with or without state? All
though the tool seems to be useful, it shouldn't slow down the
implementation of JackSession in the applications of course ... An app
with JackSession is by far more preferable then this kind of 'hacks'.
\r
On 08/11/2011 05:42 PM, Florian Paul Schmidt
wrote:
Thanks for your work. If Qjackctl will support JackSessions infra
clients, it will provide the same functionality I think. Qjackctl can
be used without condoms, so that's an obvious advantage.
In the tradition of releasing (or at least announcing)buggy, mostly
untested software, here's:
js_wrap - a simple wrapper for non Jack-Session aware apps whose
state can be fully specified by their commandline
Use
js_wrap -- gnome-terminal
if you want to get a gnome terminal in your jack_session.. Or
js_wrap -- a2jmidid
if you want to have the alsa to midi bridge in your jack_session..
Get the software via copy and paste of the following commands:
git clone https://github.com/fps/js_wrap
cd js_wrap
mkdir bld
cd bld
cmake ..
cd ..
make -C bld
sudo make install
sudo make -C bld install
Sorry
>
> and get to fixing bugs ;D
>
> In my experiments it worked just fine with gnome-terminal though
> there are some errors and the code is pretty much copy-pasta'd from
> lash_wrap... So expect breakage and panic and hilarity which will
> ensue.. 
6:54 p.m.
On Sat, Aug 13, 2011 at 2:46 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
Makes me wondering, is this tool doing anything
'nasty' in the view of
JackSession developers, for either apps with or without state?
its only useful for clients with no state. clients with state will not
work correctly with it and are not intended to be used with it.
All though
the tool seems to be useful, it shouldn't slow down the implementation of
JackSession in the applications of course ... An app with JackSession is by
far more preferable then this kind of 'hacks'.
there is that, yes.
6:56 p.m.
On 08/13/2011 08:54 PM, Paul Davis wrote:
On Sat, Aug 13, 2011 at 2:46 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
Thanks. Could you
explain a bit more e.g. why doesn't it work correctly
with clients with state and what's going wrong in practice?
\r
Makes me wondering, is this tool doing anything
'nasty' in the view of
JackSession developers, for either apps with or without state?
its only useful for
clients with no state. clients with state will not
work correctly with it and are not intended to be used with it.
7:03 p.m.
On Sat, Aug 13, 2011 at 2:56 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
On 08/13/2011 08:54 PM, Paul Davis wrote:
all it does is to record the command that it started, and when told to
restart, it uses that same command again. so, if the command involved
a client that really did have state, the client would not get to save
its state or restore it. this is why you can use it, for example, to
include a non-JACK application in a jack session.
On Sat, Aug 13, 2011 at 2:46 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
Thanks. Could you explain a bit more e.g. why doesn't it work correctly with
clients with state and what's going wrong in practice? Makes me wondering, is this tool doing anything
'nasty' in the view of
JackSession developers, for either apps with or without state?
its only useful for clients with no state. clients with state will not
work correctly with it and are not intended to be used with it.
7:09 p.m.
On 08/13/2011 09:03 PM, Paul Davis wrote:
On Sat, Aug 13, 2011 at 2:56 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
Ok, so the problem is that
JackSession starts and stops the 'wrapped'
JACK app, but doesn't save the state of it (and doesn't give you a warning).
\r
On 08/13/2011 08:54 PM, Paul Davis wrote:
all it does is to
record the command that it started, and when told to
restart, it uses that same command again. so, if the command involved
a client that really did have state, the client would not get to save
its state or restore it. this is why you can use it, for example, to
include a non-JACK application in a jack session. On Sat, Aug 13, 2011 at 2:46 PM, rosea
grammostola
<rosea.grammostola(a)gmail.com> wrote:
Thanks. Could you
explain a bit more e.g. why doesn't it work correctly with
clients with state and what's going wrong in practice? Makes me wondering, is this tool doing anything
'nasty' in the view of
JackSession developers, for either apps with or without state?
its only useful for
clients with no state. clients with state will not
work correctly with it and are not intended to be used with it.
7:12 p.m.
On Sat, Aug 13, 2011 at 3:09 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
Ok, so the problem is that JackSession starts and
stops the 'wrapped' JACK
app, but doesn't save the state of it (and doesn't give you a warning).
its not a problem. if the app is going to get state saved/restored,
then it has to participate in some kind of "exchange" with something
else. that participation is called "JACK Session" and the something
else is the session manager (via the jack server). adding a *new*
method to get the state saved/restored would be ... uh ... pointless.
the whole point of js_wrap is to handle apps that have no state, and
thus there is minimal motivation to add JACK Session support to them.
7:15 p.m.
On 08/13/2011 09:12 PM, Paul Davis wrote:
On Sat, Aug 13, 2011 at 3:09 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
Ok not ideal
maybe, but you can save the wrapped apps (with state) by
hand (press save in wrapped app), right?
Ok, so the problem is that JackSession starts and
stops the 'wrapped' JACK
app, but doesn't save the state of it (and doesn't give you a warning).
its not a problem. if the app is going to get state saved/restored,
then it has to participate in some kind of "exchange" with something
else. that participation is called "JACK Session" and the something
else is the session manager (via the jack server). adding a *new*
method to get the state saved/restored would be ... uh ... pointless.
the whole point of js_wrap is to handle apps that have no state, and
thus there is minimal motivation to add JACK Session support to them.
11:24 p.m.
On Sat, Aug 13, 2011 at 3:15 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
On 08/13/2011 09:12 PM, Paul Davis wrote:
you can do that without JACK Session too.
On Sat, Aug 13, 2011 at 3:09 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
Ok not ideal maybe, but you can save the wrapped apps (with state) by hand
(press save in wrapped app), right? Ok, so the problem is that JackSession starts and
stops the 'wrapped'
JACK
app, but doesn't save the state of it (and doesn't give you a warning).
its not a problem. if the app is going to get state saved/restored,
then it has to participate in some kind of "exchange" with something
else. that participation is called "JACK Session" and the something
else is the session manager (via the jack server). adding a *new*
method to get the state saved/restored would be ... uh ... pointless.
14 Aug
14 Aug
9:55 a.m.
On 08/14/2011 01:24 AM, Paul Davis wrote:
On Sat, Aug 13, 2011 at 3:15 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
But the advantage of using js_wrap is that the application is started in
a session, with the Jack connections restored.
On 08/13/2011 09:12 PM, Paul Davis wrote:
you can do that without JACK Session too.
On Sat, Aug 13, 2011 at 3:09 PM, rosea
grammostola
<rosea.grammostola(a)gmail.com> wrote:
Ok not ideal
maybe, but you can save the wrapped apps (with state) by hand
(press save in wrapped app), right? Ok, so the problem is that JackSession starts and
stops the 'wrapped'
JACK
app, but doesn't save the state of it (and doesn't give you a warning).
its not a problem. if the app is going to get state saved/restored,
then it has to participate in some kind of "exchange" with something
else. that participation is called "JACK Session" and the something
else is the session manager (via the jack server). adding a *new*
method to get the state saved/restored would be ... uh ... pointless.
4645
days inactive
4648
days old
linux-audio-user@lists.linuxaudio.org
12 comments
4 participants
participants (4)
-
Dan Muresan -
Florian Paul Schmidt -
Paul Davis -
rosea grammostola