26 Oct
2003
26 Oct
'03
7:35 p.m.
Hi,
please excuse my stupidity, but:
Why can't ladccad daemon start up without jack server being running?
From my point of view it would be right for ladccad to
bring jack up.
So allowing for example multiple jack sessions with different jack
settings.
horsh
26 Oct
26 Oct
8:11 p.m.
On Sun, 2003-10-26 at 23:41, "?rshТoi8-r?Q?" wrote:
Taking down and bringing up jackd is outside the scope of LADCCA but
fortunately, it won't be necessary to take down and bring up jackd in
order to change its settings once on-the-fly driver switching, and later
a general on-the-fly settings modification system is in place in jack.
Bob
--
Bob Ham <rah(a)bash.sh>
"At some point, keystroke recorders got installed on several machines at
Valve. Our speculation is that these were done via a buffer overflow in
Outlook's preview pane." -- Gabe Newell on the Half-Life 2 source leak
Why can't ladccad daemon start up without jack
server being running?
LADCCA was written with the assumption that jack is a system service,
along the lines of ALSA, X, syslog, etc. LADCCA is a session manager
for clients of jack; not jack itself. To compare it with X, LADCCA
managing jack would be like gnome-session managing the X server. There
are other tools to do that; with X there is xdm, gdm or kdm and with
jack there is qjackctl.
From my point
of view it would be right for ladccad to bring jack up.
So allowing for example
multiple jack sessions with different jack settings.
8:35 p.m.
New subject: Re[2]: [linux-audio-dev] LADCCA without JACK ?
From: Bob Ham <rah(a)bash.sh>
well, ladccad does not refuse to sturt up without X or syslog being running.
Why can't ladccad daemon start up without
jack server being running?
LADCCA was written with the assumption that jack is a system service,
along the lines of ALSA, X, syslog, etc. LADCCA is a session manager
for clients of jack; not jack itself.
A thought it is a session manager for Linux Audio (as in LAdcca)
not exclisively for jackified applications.
Sigh...
Are there plans for laddcca to support jack-less operation?
To compare it with X, LADCCA
managing jack would be like gnome-session managing the X server. There
are other tools to do that; with X there is xdm, gdm or kdm and with
jack there is qjackctl.
Taking down and bringing up jackd is outside the scope of LADCCA but
fortunately, it won't be necessary to take down and bring up jackd in
order to change its settings once on-the-fly driver switching, and later
a general on-the-fly settings modification system is in place in jack.
From my
point of view it would be right for ladccad to bring jack up.
So allowing for
example multiple jack sessions with different jack settings.
27 Oct
27 Oct
6:57 a.m.
New subject: Re[2]: [linux-audio-dev] LADCCA without JACK ?
On Mon, 2003-10-27 at 00:35, "?rshТoi8-r?Q?" wrote:
Those are just examples of system services, rather than system services
that LADCCA uses.
Let me rephrase: LADCCA is a session manager for jack and alsa sequencer
*clients*; not the services themselves.
From: Bob Ham
<rah(a)bash.sh>
well, ladccad does not refuse to sturt up without X or syslog being running. Why can't ladccad daemon start up without
jack server being running?
LADCCA was written with the assumption that jack is a system service,
along the lines of ALSA, X, syslog, etc. LADCCA is a
session manager
for clients of jack; not jack itself.
A thought it is a session manager for Linux Audio (as in LAdcca)
not exclisively for jackified applications.
Sigh... Are there plans for laddcca to support jack-less
operation?
Yes.
Bob
--
Bob Ham <rah(a)bash.sh>
"At some point, keystroke recorders got installed on several machines at
Valve. Our speculation is that these were done via a buffer overflow in
Outlook's preview pane." -- Gabe Newell on the Half-Life 2 source leak
7693
days inactive
7694
days old
linux-audio-dev@lists.linuxaudio.org
3 comments
2 participants
participants (2)
-
"horsh -
Bob Ham