On Sat, 15 May 2004, Robert Jordens wrote:
> Hello!
>
> [Thu, 13 May 2004] guenter geiger wrote:
> > On 13 May 2004, Jack O'Quin wrote:
> > > My feeling is that we should leave this as an obscure feature for
> > > expert users to experiment with at this point. Eventually, full
> > > support will e
Hello!
[Sat, 15 May 2004] Jack O'Quin wrote:
> Robert Jordens <[EMAIL PROTECTED]> writes:
>
> > I'd like to know where and why "jackd -dalsa" doesn't startup something
> > usefull. We should work on that.
>
> It does, doesn't it? ("jackd -dalsa -dhw:0")
Guenter said that it "doesn't start reli
Robert Jordens <[EMAIL PROTECTED]> writes:
> I'd like to know where and why "jackd -dalsa" doesn't startup something
> usefull. We should work on that.
It does, doesn't it? ("jackd -dalsa -dhw:0")
Now that we have the concept of a "default driver", we may make
`jackd' by itself start up somethi
Hello!
[Thu, 13 May 2004] guenter geiger wrote:
> On 13 May 2004, Jack O'Quin wrote:
> > My feeling is that we should leave this as an obscure feature for
> > expert users to experiment with at this point. Eventually, full
> > support will evolve, but that will take a while.
>
> Agreed. Its a re
On 13 May 2004, Jack O'Quin wrote:
> My feeling is that we should leave this as an obscure feature for
> expert users to experiment with at this point. Eventually, full
> support will evolve, but that will take a while.
Agreed. Its a really cool and nice feature for the experienced user,
it wil
guenter geiger <[EMAIL PROTECTED]> writes:
> Hmm, to make it more visible, what we could do is asking a debconf
> question. The problem is that the current solution of setting a
> environment variable is not very "Debian-friendly", which means
> that I don't know of an easy way to enable the featu
On 12 May 2004, Jack O'Quin wrote:
> Robert Joerdens <[EMAIL PROTECTED]> writes:
>
> > I wonder if we should change the default to starting the daemon even if
> > upstream doesn't do that yet.
>
> I would not recommend that. We decided to release it dependent on
> JACK_START_SERVER because some c
On Wed, 12 May 2004, Robert Joerdens wrote:
> On Tue, 11 May 2004, guenter geiger wrote:
> > On alpha it compiles fine, I have some problems running it though,
> > have to take a look the next days. I get:
> > jack(1): cannot open jack FIFO directory (No such file or directory)
>
> You need to
Robert Joerdens <[EMAIL PROTECTED]> writes:
> I wonder if we should change the default to starting the daemon even if
> upstream doesn't do that yet.
I would not recommend that. We decided to release it dependent on
JACK_START_SERVER because some clients use jack_client_new() to decide
whether t
Hi guenter!
On Tue, 11 May 2004, guenter geiger wrote:
> On alpha it compiles fine, I have some problems running it though,
> have to take a look the next days. I get:
> jack(1): cannot open jack FIFO directory (No such file or directory)
You need to be running a recent glibc package that mo
On Tue, 11 May 2004, Robert Jordens wrote:
> Hi all.
>
> JACK 0.98.1 is in experimental. It should not break binary
> compatibility but adds the nice feature of automatically starting jackd
> based on ~/.jackdrc or /etc/jackdrc if $JACK_START_SERVER is set.
> That plays really nicely with the rece
Hi all.
JACK 0.98.1 is in experimental. It should not break binary
compatibility but adds the nice feature of automatically starting jackd
based on ~/.jackdrc or /etc/jackdrc if $JACK_START_SERVER is set.
That plays really nicely with the recent addition of the
realtime-module (thanks to Guenter!)
12 matches
Mail list logo
