12 Jun
2005
12 Jun
'05
1:50 a.m.
My apologies for cross-posting. This message is intended for jack-rack
maintainers:
First off, I think jack-rack is awesome app and I have been using it quite
regularly. As a result, I've come up with a small suggestion/wish-list for
this wonderful app:
1) it would be awesome if jack-rack, once it gets bounced by jackd (for
whatever reason), would have an option to restart with the same, already
open settings file, while recreating existing connections. I am simply
saying this as it has been quite stressful to have to close the app, reopen
it, open the settings file, and then re-hook everything in jack right before
the performance (and nearly impossible during one) when the clock is ticking
and audience getting restless. :-) Ultimately, it would be awesome if it
could automatically reconnect even if that would cause a nasty pop (perhaps
as an option in the preferences menu), which, after seeing cool additions
made to the jackd at LAC3, most likely soon we won't have to worry about any
more, if not already (btw, apropos the "pop"-less connecting of clients
while jackd is running that was demoed on the OSX version, does anyone know
whether it has been ported to Linux as of yet?).
Many thanks for taking the time to read and consider this suggestion!
Best wishes,
Ivica Ico Bukvic, composer & multimedia sculptor
http://meowing.ccm.uc.edu/~ico/
12 Jun
12 Jun
6:15 a.m.
Hi,
My apologies for cross-posting. This message is
intended
for jack-rack maintainers:
I just filed the ideas as RFEs on the sourceforge project
page. ([1] & [2])
First off, I think jack-rack is awesome app and I have
been
using it quite regularly.
Seconded. It made me unpack my acoustic guitar which I haven't
played for years. Great fun, except for my neighbours :) .
As a result, I've come up with a
small suggestion/wish-list for this wonderful app:
1) it would be awesome if jack-rack, once it gets bounced
by jackd (for whatever reason), would have an option to
restart with the same, already open settings file, while
recreating existing connections.
Seconded again. This would not only be useful for jack-rack
but for many other applications as well.
I am simply saying this as
it has been quite stressful to have to close the app,
reopen it, open the settings file, and then re-hook
everything in jack right before the performance (and nearly
impossible during one) when the clock is ticking and
audience getting restless. :-)
The situation is getting worse if you use more than one app
and you have to restart JACK itself. Then you have to reload
a lot of files into all applications and to redo a lot of
MIDI and JACK connections. If each particular application
could (maybe optionally) remember
* the last loaded file
* the last used MIDI connections
* the last used JACK connections
this could simplify the usage a lot.
Because applications can even crash, the settings mentioned
above could be written to the configuration file immediately
when changing them ("crash saveness" as Ardour provides).
Furthermore, from a users POV I wonder if it would be possible
to redesign the JACK-thread of an application so it doesn't
need to be restarted as soon the JACK connection gets lost.
Wouldn't it be possible to make an application automatically
reconnecting to JACK as soon as it got kicked, and as soon as
JACK gets stopped or restarted to display an alert box "It
seems that JACK has been stopped. Waiting for JACK to
reappear.".
It may sound like nitpicking, but for users, especially new
users, the points above could really be one little more step
to improve linux audio usage.
Thanks & best regards
ce
[1]
http://sourceforge.net/tracker/index.php?func=detail&aid=1219068&gr…
[2]
http://sourceforge.net/tracker/index.php?func=detail&aid=1219067&gr…
11:28 a.m.
New subject: [linux-audio-user] jack-rack wish-list]
First off, I
think jack-rack is awesome app and I have been
using it quite regularly.
Seconded. It made me unpack my acoustic guitar which I haven't
played for years. Great fun, except for my neighbours :) .
As a result, I've come up with a
small suggestion/wish-list for this wonderful app:
1) it would be awesome if jack-rack, once it gets bounced
by jackd (for whatever reason), would have an option to
restart with the same, already open settings file, while
recreating existing connections.
Seconded again. This would not only be useful for jack-rack
but for many other applications as well.
I am simply saying this as
it has been quite stressful to have to close the app,
reopen it, open the settings file, and then re-hook
everything in jack right before the performance (and nearly
impossible during one) when the clock is ticking and
audience getting restless. :-)
The situation is getting worse if you use more than one app
and you have to restart JACK itself. Then you have to reload
a lot of files into all applications and to redo a lot of
MIDI and JACK connections. If each particular application
could (maybe optionally) remember
* the last loaded file
* the last used MIDI connections
* the last used JACK connections
this could simplify the usage a lot.
Because applications can even crash, the settings mentioned
above could be written to the configuration file immediately
when changing them ("crash saveness" as Ardour provides).
Furthermore, from a users POV I wonder if it would be
possible
to redesign the JACK-thread of an application so it doesn't
need to be restarted as soon the JACK connection gets lost.
Wouldn't it be possible to make an application automatically
reconnecting to JACK as soon as it got kicked, and as soon as
JACK gets stopped or restarted to display an alert box "It
seems that JACK has been stopped. Waiting for JACK to
reappear.".
It may sound like nitpicking, but for users, especially new
users, the points above could really be one little more step
to improve linux audio usage.
I think that this is not a problem of jack but a problem of the
applications which use it. Actually ardour already has a mechanism to
reconnect to jack when it loses its connection. Now it doesn't work
(beta29) ;( but it seems that in the future will do so.
I don't know... Any jack expert could help to see what should be done to
fix this?
regards,
MarC
1:20 p.m.
New subject: [linux-audio-user] jack-rack wish-list]
>The situation is getting worse if you use more
than one app
>and you have to restart JACK itself. Then you have to reload
>a lot of files into all applications and to redo a lot of
>MIDI and JACK connections. If each particular application
>could (maybe optionally) remember
Although there is LADCCA (or now known as LASH), but I haven't heard
anything its progress for some time now... Anyone knows what's going on with
it?
I think interoperability with qjackctl would be awesome as qjackctl has,
imho, pretty much become synonymous with jackd and on top of that offers
MIDI interconnectivity GUI as well.
Best wishes,
Ico
2:19 p.m.
New subject: [linux-audio-user] jack-rack wish-list]
On Sun, 2005-06-12 at 13:20 -0400, Ivica Ico Bukvic wrote:
Although there is LADCCA (or now known as LASH), but I
haven't heard
anything its progress for some time now... Anyone knows what's going on with
it?
I think interoperability with qjackctl would be awesome as qjackctl has,
imho, pretty much become synonymous with jackd and on top of that offers
MIDI interconnectivity GUI as well.
Yes, a simple LADCCA control window in qjackctl for saving and restoring
LADCCA projects would be very nice.
--
Lars Luthman
PGP key: http://www.d.kth.se/~d00-llu/pgp_key.php
Fingerprint: FCA7 C790 19B9 322D EB7A E1B3 4371 4650 04C7 7E2E
2:03 p.m.
On Sun, 2005-06-12 at 12:16 +0200, Christoph Eckert wrote:
The situation is getting worse if you use more than
one app
and you have to restart JACK itself. Then you have to reload
a lot of files into all applications and to redo a lot of
MIDI and JACK connections. If each particular application
could (maybe optionally) remember
* the last loaded file
* the last used MIDI connections
* the last used JACK connections
This is what LADCCA (LASH) is for. You start your programs, do your
connections, and tell LADCCA to save the project. Later, when you ask
LADCCA to restore the project, it will start the same programs, make the
connections, and tell the programs to load their states from the
project. There haven't been any new LADCCA releases in a while, but
0.4.0 works quite well for things like this.
The problem is that only a handful of programs support LADCCA - which is
strange, because for a typical program that already has functions to
write and restore its state from a file you only need a few dozen lines
of code to make it work. Call the initialisation function and tell
LADCCA your JACK name and ALSA ID when you start the program, and write
a timeout callback that checks for new LADCCA events a few times every
second (Save, Restore, and Quit should be sufficient for most programs)
- and that's it.
http://lash-audio-session-handler.org
--
Lars Luthman
PGP key: http://www.d.kth.se/~d00-llu/pgp_key.php
Fingerprint: FCA7 C790 19B9 322D EB7A E1B3 4371 4650 04C7 7E2E
26 Jun
26 Jun
5:16 p.m.
Several days ago (20050612) Lars Luthman wrote:
Yeah, it's cool. But I still think that my ideas could improve
users' impression when dealing with free audio software for
the following reasons:
* Audio applications can crash, and if - at this time - LASH
didn't already save the configuration it's lost
* Maybe someone simply installs jack-rack and some LADSPAS to
use the box as an effects rack. What happens if LASH doesn't
get installed? An audio application shouldn't depend
necessarily on LASH, but use it as soon as it is available
* Others may prefer to not install LASH because there's no
package for the distro or even the user has no (root) access
on the machine, so the above is still valid.
The situation
is getting worse if you use more than one
app and you have to restart JACK itself. Then you have to
reload a lot of files into all applications and to redo a
lot of MIDI and JACK connections. If each particular
application could (maybe optionally) remember
* the last loaded file
* the last used MIDI connections
* the last used JACK connections
This is what LADCCA (LASH) is for. You start your programs,
do your connections, and tell LADCCA to save the project.
Later, when you ask LADCCA to restore the project, it will
start the same programs, make the connections, and tell the
programs to load their states from the project. There
haven't been any new LADCCA releases in a while, but 0.4.0
works quite well for things like this. The problem is that only a handful of programs
support
LADCCA - which is strange, because for a typical program
that already has functions to write and restore its state
from a file you only need a few dozen lines of code to make
it work. Call the initialisation function and tell LADCCA
your JACK name and ALSA ID when you start the program, and
write a timeout callback that checks for new LADCCA events
a few times every second (Save, Restore, and Quit should be
sufficient for most programs) - and that's it.
http://lash-audio-session-handler.org
OK, but then users can write feature requests for the
particular applications.
I think the following could be a flexible solution:
* As soon as an application starts it checks for a running
LASH server
* If there is one it behaves as told by LASH
* If there is no LASH, it could read the last used document
and the last used MIDI and audio connections from the config
file
* As soon as the document file or any connection changes, an
application could immediately write it back to the
configuration file so even a crash will cause it to reload
the settings when it gest restarted
Even at the Linuxtag show this was sometimes a show stopper.
Zyn crashed and after restarting it you have to redo all
connections manually and to reload the last used patch while
the 'customer' is watching ;-) .
Best regards
ce
12 Jun
12 Jun
1:20 p.m.
"Ivica Ico Bukvic" <ico(a)fuse.net> writes:
it would be awesome if jack-rack, once it gets bounced
by jackd (for
whatever reason), would have an option to restart with the same, already
open settings file, while recreating existing connections.
This should be the job of lash, http://lash-audio-session-handler.org
and Dave Robillard is working on this.
it would be awesome if it could automatically
reconnect even if that
would cause a nasty pop (perhaps as an option in the preferences
menu),
I think maybe the app should have a run/stop process function. As long
as it's in run it will always try to silently connect. When jack
restarts after a failure, it accepts the connections. There should
also be a way in jack to refuse connections.
apropos the "pop"-less connecting of clients
while jackd is running
that was demoed on the OSX version, does anyone know whether it has
been ported to Linux as of yet?).
No, this is a post 1.0 jack issue, but it's definitely something
required.
--
Esben Stien is b0ef@e s a
http://www. s t n m
irc://irc. b - i . e/%23contact
[sip|iax]: e e
jid:b0ef@ n n
6913
days inactive
6927
days old
linux-audio-user@lists.linuxaudio.org
7 comments
5 participants
participants (5)
-
Christoph Eckert -
Esben Stien -
Ivica Ico Bukvic -
Lars Luthman -
MarC