5 Apr
2006
5 Apr
'06
5:01 p.m.
Hi,
I've just tried out linuxsampler (well, qsampler really) for the
first time, with some samples from Worra's Place.
Everything seems to work but the sound is very distorted
with every gig I've tried. Ugly nonlinear distortion, almost like
a ring modulator. Not at all subtle. It happens even if I play
a single note at low velocity. Doesn't sound like xrun choppiness,
and no other apps on this box make similar sounds.
I'm using ALSA output, no Jack.
Version info:
libgig 2.0.1
liblscp 0.3.0
qsampler 0.1.2
LinuxSampler 0.3.3
Anybody encountered this? Any clues?
--
Paul Winkler
http://www.slinkp.com
5 Apr
5 Apr
5:32 p.m.
On Wed, Apr 05, 2006 at 03:01:35PM -0400, Paul Winkler wrote:
Hi,
I've just tried out linuxsampler (well, qsampler really) for the
first time, with some samples from Worra's Place.
Everything seems to work but the sound is very distorted
with every gig I've tried. Ugly nonlinear distortion, almost like
a ring modulator. Not at all subtle. It happens even if I play
a single note at low velocity. Doesn't sound like xrun choppiness,
and no other apps on this box make similar sounds.
I'm using ALSA output, no Jack.
Version info:
libgig 2.0.1
liblscp 0.3.0
qsampler 0.1.2
LinuxSampler 0.3.3
I just tried again under jack, with realtime scheduling.
Responsiveness is very good and cpu load stays reasonable.
No xruns reported. The distortion comes and goes unpredictably;
things sound fine for a minute or so... then the distortion
appears and keeps happening for a minute or so... then it "fixes
itself".
Very weird.
--
Paul Winkler
http://www.slinkp.com
6:18 p.m.
On Wednesday 05 April 2006 21:01, Paul Winkler wrote:
Hi,
I've just tried out linuxsampler (well, qsampler really) for the
first time, with some samples from Worra's Place.
Everything seems to work but the sound is very distorted
with every gig I've tried. Ugly nonlinear distortion, almost like
a ring modulator. Not at all subtle. It happens even if I play
a single note at low velocity. Doesn't sound like xrun choppiness,
and no other apps on this box make similar sounds.
I'm using ALSA output, no Jack.
Version info:
libgig 2.0.1
liblscp 0.3.0
qsampler 0.1.2
LinuxSampler 0.3.3
Anybody encountered this? Any clues?
I too have just tried it out for the first time, thanks to the link to Worra's
place. Got the Honky Tonk Piano files. The difference I notice from playing
the usb midi keyboard compared to the demo .mp3 is that the .mp3 sounds a lot
brighter. I'd send you the .wav of C major to compare, but it's 3MB. I don't
think the list would like that. Of course it would help if there was some
help for Linuxsampler. I feel like I'm working in the dark. Nigel.
6:36 p.m.
On Wed, 2006-04-05 at 15:01 -0400, Paul Winkler wrote:
Hi,
I've just tried out linuxsampler (well, qsampler really) for the
first time, with some samples from Worra's Place.
Everything seems to work but the sound is very distorted
with every gig I've tried. Ugly nonlinear distortion, almost like
a ring modulator. Not at all subtle. It happens even if I play
a single note at low velocity. Doesn't sound like xrun choppiness,
and no other apps on this box make similar sounds.
I'm using ALSA output, no Jack.
i'd wager 90% chance its a bug in linuxsampler. i would keep running
into this many times whenever i wrote ALSA i/o code until i wrote JACK.
even early versions of JACK would do it too. once JACK was fixed, i
never wrote such code again.
--p
7:40 p.m.
On Wed, Apr 05, 2006 at 04:40:12PM -0400, Paul Davis wrote:
On Wed, 2006-04-05 at 15:01 -0400, Paul Winkler
wrote:
Hmmm, but sometimes I get it under JACK too, with realtime priority
and all... will try again later.
--
Paul Winkler
http://www.slinkp.com
Hi,
I've just tried out linuxsampler (well, qsampler really) for the
first time, with some samples from Worra's Place.
Everything seems to work but the sound is very distorted
with every gig I've tried. Ugly nonlinear distortion, almost like
a ring modulator. Not at all subtle. It happens even if I play
a single note at low velocity. Doesn't sound like xrun choppiness,
and no other apps on this box make similar sounds.
I'm using ALSA output, no Jack.
i'd wager 90% chance its a bug in linuxsampler. i would keep running
into this many times whenever i wrote ALSA i/o code until i wrote JACK.
even early versions of JACK would do it too. once JACK was fixed, i
never wrote such code again. 
8:06 p.m.
On Wed, 2006-04-05 at 17:40 -0400, Paul Winkler wrote:
Hmmm, but sometimes I get it under JACK too, with
realtime priority
and all... will try again later.
What soundcard, sample rate, ALSA driver version?
This sound similar to some problems people were having running emu10k1
devices at 44.1KHz, which disappeared when using 48KHz.
Lee
8:16 p.m.
On Wed, 2006-04-05 at 18:05 -0400, Lee Revell wrote:
On Wed, 2006-04-05 at 17:40 -0400, Paul Winkler
wrote:
Sorry - my mail client just gets buggier every time I upgrade.
Apparently it's possible to send two identical copies of a message by
hitting "Send/Receive", "Cancel", and "Send/Receive" again
:-P
Lee
Hmmm, but sometimes I get it under JACK too, with
realtime priority
and all... will try again later.
What soundcard, sample rate, ALSA driver version?
This sound similar to some problems people were having running emu10k1
devices at 44.1KHz, which disappeared when using 48KHz.
8:23 p.m.
On Wed, Apr 05, 2006 at 06:05:51PM -0400, Lee Revell wrote:
On Wed, 2006-04-05 at 17:40 -0400, Paul Winkler
wrote:
See, this is why we have mailing lists :-)
Problem solved. I was using my sb128 PCI card, which uses
snd_1371. And I was indeed using it at 44100. Alsa version 1.0.10.
Switched sampling rate to 48000 (it took me a while to realize that
field in the qsampler gui is editable! It doesn't look like it)...
and problem is solved.
Thanks Lee!!
--
Paul Winkler
http://www.slinkp.com
Hmmm, but sometimes I get it under JACK too, with
realtime priority
and all... will try again later.
What soundcard, sample rate, ALSA driver version?
This sound similar to some problems people were having running emu10k1
devices at 44.1KHz, which disappeared when using 48KHz. 
9:06 p.m.
On 4/5/06, Paul Winkler <pw_lists(a)slinkp.com> wrote:
Note that LinuxSamper does not resample the gig files to the 48K
sample rate so your samples are going to play about 1 note too high.
GigaStudio works the same way. Almost all gig files are recorded at
44.1K. Very few exceptions to that. (I have about 3000 gig files...)
If you want gig files in tune then you need to get a sound card that
works well at 44.1K or get the Alsa resampling stuff to work better.
CAVEAT: I haven't used LS in 6-8 months since they switched the
license to non-Open Source. Possibly they have added something that
addresses this, or attempts to, and was effecting the quality of the
audio you are getting.
Cheers,
Mark
This sound similar to some problems people were having running emu10k1
devices at 44.1KHz, which disappeared when using 48KHz.
See, this is why we have mailing lists :-)
Problem solved. I was using my sb128 PCI card, which uses
snd_1371. And I was indeed using it at 44100. Alsa version 1.0.10.
Switched sampling rate to 48000 (it took me a while to realize that
field in the qsampler gui is editable! It doesn't look like it)...
and problem is solved.
Thanks Lee!!
--
Paul Winkler 
14 Apr
14 Apr
12:44 a.m.
Mark Knecht wrote:
CAVEAT: I haven't used LS in 6-8 months since they
switched the
license to non-Open Source.
I know this is a pointless comment, but really, what is the point in
making an application with 'Linux' in the name that is not open source?
Seems rather backward to me.
"Just think of their offspring, if offspring there be,
They'll never receive any blessing from me." Flanders & Swann -
misalliance (probably misquoted too)
cheers,
tim hall
2:22 a.m.
On 4/13/06, tim hall <tech(a)glastonburymusic.org.uk> wrote:
Mark Knecht wrote:
Rather. I completely agree.
When people use the Open Source community to develop an application,
but then take it private in an apparentl attempt to use it for their
personal financial benefit, we get things like this happening. It's
not that it isn't available. I suppose it is. I just use GigaStudio
and Acid Pro for my sampling and loop playing needs and left LS
behind.
All of this is supposition and patently unfair, I'm sure, but the
developers wouldn't explain their actions in an open forum so that
we'd understand it so we were (I was) left with no option but to
guess.
Cheers,
Mark
CAVEAT: I haven't used LS in 6-8 months since
they switched the
license to non-Open Source.
I know this is a pointless comment, but really, what is the point in
making an application with 'Linux' in the name that is not open source?
Seems rather backward to me. 
9:55 a.m.
New subject: distorting Linuxsampler, was Re: [linux-audio-user] linuxsampler distortion?
Mark Knecht wrote:
When people use the Open Source community to develop an
application,
but then take it private in an apparentl attempt to use it for their
personal financial benefit, we get things like this happening. It's
not that it isn't available. I suppose it is. I just use GigaStudio
and Acid Pro for my sampling and loop playing needs and left LS
behind.
I'm not making much sense of this rationale, Mark. In the first place I
haven't yet seen proof that LS is being developed for someone's personal
financial benefit or that it's been "taken private". I just now
downloaded the latest CVS sources, no problem.
However, I do agree that the authors' stipulation re: commercial work is
in opposition to the GPL. I've heard RMS address this issue a few times,
he's been clear about it: The GPL doesn't interfere with deployment,
period. If someone wants to use LS in a commercial venture, they can do
so *as long as* they abide by all other terms of the license.
Or am I missing something else ?
And of course, with GS and AP we can have no such moral, ethical, or
ideological concerns because we accept from the point of purchase that
we can know absolutely *nothing* regarding their code base, whether
they've lifted code from anywhere, or even whether they use their
profits from our purchases to fund oppressive regimes. We just want the
tool, we want no involvement with it beyond its use. Which is good,
because most manufacturers seem to want little more from their customers
than the money anyway.
It starts to sound like prostitution, doesn't it ? ;-)
All of this is supposition and patently unfair, I'm
sure, but the
developers wouldn't explain their actions in an open forum so that
we'd understand it so we were (I was) left with no option but to
guess.
You stated specifically in an earlier message that the authors switched
the license to a "non-Open Source" license. What license is that ? The
only license I see advertised on the LS Web site is the GPL. Please
elucidate. :)
I'll write to Christian about this issue. I'd like to include LS in the
book project, and I've planned to profile it in my column for LJ, so I
want clarity re: the license. Of one thing I'm certain: The GPL does not
internally restrict deployment, and the LS authors would be prudent to
remove the stipulation.
Btw, the stipulation itself, however commendably motivated, flies in the
face of the GPL's intention to protect the rights of the *user*. This
alone should be reason enough to remove it.
Just my dos pesos.
Best,
dp
11:34 a.m.
New subject: distorting Linuxsampler, was Re: [linux-audio-user] linuxsampler distortion?
Hi Dave,
On 4/14/06, Dave Phillips <dlphillips(a)woh.rr.com> wrote:
Please read the license. At one time they changed the text. It says
GPL in the title but it was modified in this one area to prohibit
commercial use without the developer's permission. As I've also said,
I haven't touched the program for probably 8-12 months so what you
download today could be different, either fixed and better or worse.
Mark Knecht wrote:
By 'taken private' I did not mean people couldn't download it, even
though there was a period of time where the LS server didn't allow it.
By 'taken private' I meant that the license was changed to inhibit
fair & open competition by multiple for-profit vendors who might like
to use LS in a product that produced revenue because to even try to do
it they had to get the developers permission, which can be withheld.
My view is multiple vendors using LS in commercial products is a good
thing for the LS community overall. They would be doing fixes and
adding features that would be fed back into the Open Source code and
benefiting users of that code.
When people use the Open Source community to
develop an application,
but then take it private in an apparentl attempt to use it for their
personal financial benefit, we get things like this happening. It's
not that it isn't available. I suppose it is. I just use GigaStudio
and Acid Pro for my sampling and loop playing needs and left LS
behind.
I'm not making much sense of this rationale, Mark. In the first place I
haven't yet seen proof that LS is being developed for someone's personal
financial benefit or that it's been "taken private". I just now
downloaded the latest CVS sources, no problem.
However, I do agree that the authors' stipulation re: commercial work is
in opposition to the GPL. I've heard RMS address this issue a few times,
he's been clear about it: The GPL doesn't interfere with deployment,
period. If someone wants to use LS in a commercial venture, they can do
so *as long as* they abide by all other terms of the license.
Right. But the license, as it was modified, prohibits exactly that
from happening without the permission of the authors. The Debian guys
dropped, at one time, LS from their releases simply because the text
of the GPL was changed. It didn't seem to matter what he change was
since the GPL says no one can change it except for the people who
wrote it. (I.e - not the LS developers)
Or am I missing something else ?
I don't think so.
And of course, with GS and AP we can have no such moral, ethical, or
ideological concerns because we accept from the point of purchase that
we can know absolutely *nothing* regarding their code base, whether
they've lifted code from anywhere, or even whether they use their
profits from our purchases to fund oppressive regimes. We just want the
tool, we want no involvement with it beyond its use. Which is good,
because most manufacturers seem to want little more from their customers
than the money anyway.
When I first started using, and more importantly supporting the
development of Linux application I felt much the same way. Over time I
developed some of my own thoughts around the idea that very few Open
Source apps, while good apps, ever make it to the level that a
commercial app does in terms of features and support. My thought, as a
non-programmer, was that if I did whatever little bit I could to help
the Open Source app become better, and the app eventually became good
enough for a for-profit company to pick up and start running with it,
then maybe I'd finally get the features that the for-no-profit Open
Source development team never had the interest or manpower to
implement. The change that the guys made to the LS license created
barriers to this.
It starts to sound like prostitution, doesn't it ? ;-)
You said it not me, but if it feels good what harm is caused? ;-)
All of this is supposition and patently unfair,
I'm sure, but the
developers wouldn't explain their actions in an open forum so that
we'd understand it so we were (I was) left with no option but to
guess.
You stated specifically in an earlier message that the authors switched
the license to a "non-Open Source" license. What license is that ? The
only license I see advertised on the LS Web site is the GPL. Please
elucidate. :) From the start of the FAQ page on the LS.org website it
appears they
haven't changed and are modifying GPL, which itself is not allowed
by
GPL:
http://www.linuxsampler.org/faq.html
<SNIP?
Can I use LinuxSampler in commercial hardware or software products?
You are NOT ALLOWED to use LinuxSampler source code, libraries or
applications in COMMERCIAL hardware or software products without prior
written authorization by the authors. See here
<SNIP>
Pure GPL wouldn't prohibit this, therefore it follows that LS is not
using pure GPL.
I'll write to Christian about this issue. I'd like to include LS in the
book project, and I've planned to profile it in my column for LJ, so I
want clarity re: the license. Of one thing I'm certain: The GPL does not
internally restrict deployment, and the LS authors would be prudent to
remove the stipulation.
Btw, the stipulation itself, however commendably motivated, flies in the
face of the GPL's intention to protect the rights of the *user*. This
alone should be reason enough to remove it.
Just my dos pesos.
and my Dos Equis,
XX (aka Mark)
Best,
dp
5 Apr
5 Apr
9:08 p.m.
On Wed, 2006-04-05 at 18:23 -0400, Paul Winkler wrote:
See, this is why we have mailing lists :-)
Problem solved. I was using my sb128 PCI card, which uses
snd_1371. And I was indeed using it at 44100. Alsa version 1.0.10.
Switched sampling rate to 48000 (it took me a while to realize that
field in the qsampler gui is editable! It doesn't look like it)...
Pro audio apps should default to 48000 like JACK, as it's the most
widely suppored sample rate (not to mention the best available on
consumer hardware).
and problem is solved.
That's interesting, I did not know snd-ens1371 was affected. If
possible trst 1.0.11-rc4 and if it's also broken file an ALSA bug
report.
The Creative cards are known to suck at anything but 48KHz but I think
there's also a driver bug.
Lee
6 Apr
6 Apr
1:02 a.m.
On Wed, Apr 05, 2006 at 07:07:47PM -0400, Lee Revell wrote:
That's interesting, I did not know snd-ens1371 was
affected. If
possible trst 1.0.11-rc4 and if it's also broken file an ALSA bug
report.
building them now, will try tomorrow ...
The Creative cards are known to suck at anything but
48KHz but I think
there's also a driver bug.
*shrug* i know they do internal resampling of less than pristine
quality, but I've never before heard anything even remotely similar
at 44.1kHz with any app I use. Normally for "serious" stuff I use my
delta, but the sb 128 has never given me trouble like this.
--
Paul Winkler
http://www.slinkp.com
1:17 p.m.
On Wed, Apr 05, 2006 at 11:02:00PM -0400, Paul Winkler wrote:
On Wed, Apr 05, 2006 at 07:07:47PM -0400, Lee Revell
wrote:
1.0.11 drivers give me a kernel oops on boot :-(
Oh well, probably operator error but I don't have time to dig in
further.
--
Paul Winkler
http://www.slinkp.com
That's interesting, I did not know
snd-ens1371 was affected. If
possible trst 1.0.11-rc4 and if it's also broken file an ALSA bug
report.
building them now, will try tomorrow ... 
6:42 p.m.
Paul Winkler wrote:
1.0.11 drivers give me a kernel oops on boot :-(
Oh well, probably operator error but I don't have time to dig in
further.
YOu probably compiled the drivers with a different gcc version
to what the kernel was compiled with. This can cause major
screw-ups.
Check the kernelboot sequence for the gcc version used to compile
it and then try to match it.
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo
+-----------------------------------------------------------+
"I wouldn't want to create the impression that I wouldn't like the
government of the United States to be Islamic sometime in the future."
-- Ibrahim Hooper, spokesman for Council of American Islamic Relations.
12:09 a.m.
Lee Revell wrote:
On Wed, 2006-04-05 at 17:40 -0400, Paul Winkler
wrote:
Well, not for me I have to say... I still have this "distortion/phasing"
(depending on buffer size) problem also at 48KHz with my emu10k1 SBLive.
It also happened with the others soundcards I owned: a couple SBLive
emu10k1, ForteMedia fm801, various onboard intel8x0, even with no xruns
even with every device on its own IRQ, from kernel 2.4.20 (maybe) with
lowlat+preempt patches to 2.6.x vanilla & -rt patches from Ingo Molnar
with IRQ priorities set, along various versions of ALSA and JACK from 5
years now, all built from source...
I also posted the problem (and a silly workaround that I was using :) )
on this list, and it started a thread you can read at
http://lalists.stanford.edu/lau/2005/08/0096.html
Then I bought an M-Audio Delta44 and the difference is huge. I own it
since september 2005 and the distortion/phasing problem (more phasing
than distortion, as i run it at 2x128 48KHz all the time) has happened
only three-four times maybe.
Yes, it is certainly not often. BUT, it still happens, even on this good
ice1712 card. :(
With immutated hope for the future,
--
salvuz
POST FATA RESVRGO
Linux registered user #291700 | machine #174619
get counted on ---> http://counter.li.org/ <---
Hmmm, but sometimes I get it under JACK too, with
realtime priority
and all... will try again later.
What soundcard, sample rate, ALSA driver version?
This sound similar to some problems people were having running emu10k1
devices at 44.1KHz, which disappeared when using 48KHz.
12:13 a.m.
On Thu, 2006-04-06 at 04:09 +0200, Salvatore Di Pietro wrote:
Yes, it is certainly not often. BUT, it still happens,
even on this
good
ice1712 card. :(
With immutated hope for the future,
Try building JACK without --enable-optimize.
Have you tried a different machine? Or changing the PCI latency
settings?
Lee
12:35 a.m.
Lee Revell wrote:
[cut]
Hey! great reply time! :)
Try building JACK without --enable-optimize.
Hmmm... I don't remember having done that. Gotta try it. And in this
case I don't have to rebuild all the clients, do I?
Have you tried a different machine?
Yes, same results...
Or changing the PCI latency settings?
Same as above.
Maybe the PCI latency settings i made are not correct, here they are:
#enough bandwidth for all devices
setpci -d *:* latency_timer=b0
## max bandwidth for Delta44
setpci -s 00:0b.0 latency_timer=FF
I also remember an old thread
http://sourceforge.net/mailarchive/message.php?msg_id=8422439
on calculating the right values for PCI latency for each card in the MB.
I remember having ended up following
http://www-128.ibm.com/developerworks/library/l-hw2.html
ciao
--
salvuz
POST FATA RESVRGO
Linux registered user #291700 | machine #174619
get counted on ---> http://counter.li.org/ <---
12:47 a.m.
On Thu, 2006-04-06 at 04:34 +0200, Salvatore Di Pietro wrote:
Maybe the PCI latency settings i made are not correct,
here they are:
#enough bandwidth for all devices
setpci -d *:* latency_timer=b0
## max bandwidth for Delta44
setpci -s 00:0b.0 latency_timer=FF
Does leaving these out make any difference at all?
What ALSA version?
Lee
1 a.m.
Lee Revell wrote:
On Thu, 2006-04-06 at 04:34 +0200, Salvatore Di Pietro
wrote:
Now I am on 1.0.11rc4.
Tomorrow I'll try without the setpci commands (maybe it will make a
difference), and the JACK recompile
Thanks for the advice!
--
salvuz
POST FATA RESVRGO
Linux registered user #291700 | machine #174619
get counted on ---> http://counter.li.org/ <---
Maybe the PCI latency settings i made are not
correct, here they are:
#enough bandwidth for all devices
setpci -d *:* latency_timer=b0
## max bandwidth for Delta44
setpci -s 00:0b.0 latency_timer=FF
Does leaving these out make any difference at all?
What ALSA version?
8 Apr
8 Apr
12:10 a.m.
Lee Revell wrote:
I would first try compiling JACK with all default
settings
OK, I recompiled it with :
./configure --prefix=/usr --enable-stripped-jackd --disable-oss
--disable-portaudio --disable-coreaudio --enable-capabilities
--with-default-tmpdir=/mnt/ramfs
I think those options won't interfere with the test... Or do they?
What is the purpose of "--enable-timestamps" ? What difference does it
make enabling them?
--
salvuz
POST FATA RESVRGO
Linux registered user #291700 | machine #174619
get counted on ---> http://counter.li.org/ <---
12:18 a.m.
On Sat, 2006-04-08 at 04:09 +0200, Salvatore Di Pietro wrote:
Lee Revell wrote:
"allow clients to use the JACK timestamp API"
I would just leave the default settings alone unless you know what you
are doing.
Lee
I would first try compiling JACK with all default
settings
OK, I recompiled it with :
./configure --prefix=/usr --enable-stripped-jackd --disable-oss
--disable-portaudio --disable-coreaudio --enable-capabilities
--with-default-tmpdir=/mnt/ramfs
I think those options won't interfere with the test... Or do they?
What is the purpose of "--enable-timestamps" ? What difference does it
make enabling them?
1 a.m.
Lee Revell wrote:
On Sat, 2006-04-08 at 04:09 +0200, Salvatore Di Pietro
wrote:
Yes, I knew that from ./configure --help, I was just wondering what that
meant and what were its advantages...
Lee Revell wrote:
"allow clients to use the JACK timestamp API" I would first try compiling JACK with all default
settings
OK, I recompiled it with :
./configure --prefix=/usr --enable-stripped-jackd --disable-oss
--disable-portaudio --disable-coreaudio --enable-capabilities
--with-default-tmpdir=/mnt/ramfs
I think those options won't interfere with the test... Or do they?
What is the purpose of "--enable-timestamps" ? What difference does it
make enabling them?
I would just leave the default settings alone unless
you know what you
are doing.
I try to stay on the "unless..." part of the statement ;)
...sometimes by trial and wreckage :)
--
salvuz
POST FATA RESVRGO
Linux registered user #291700 | machine #174619
get counted on ---> http://counter.li.org/ <---
12:24 a.m.
On Sat, 2006-04-08 at 04:09 +0200, Salvatore Di Pietro wrote:
Lee Revell wrote:
Why are you using --enable-capabilities?
Lee
I would first try compiling JACK with all default
settings
OK, I recompiled it with :
./configure --prefix=/usr --enable-stripped-jackd --disable-oss
--disable-portaudio --disable-coreaudio --enable-capabilities
--with-default-tmpdir=/mnt/ramfs
I think those options won't interfere with the test... Or do they?
What is the purpose of "--enable-timestamps" ? What difference does it
make enabling them?
12:47 a.m.
Lee Revell wrote:
On Sat, 2006-04-08 at 04:09 +0200, Salvatore Di Pietro
wrote:
I didn't use it :) I made a "pasto" (eg a typo in pasting ;) ) from the
old commandline I wrote down when I used it with realtime-lsm. Sorry for
the noise...
I am starting jackd and audio apps as root with sudo now. I should start
using set_rtlimts, I know...
--
salvuz
POST FATA RESVRGO
Linux registered user #291700 | machine #174619
get counted on ---> http://counter.li.org/ <---
Lee Revell wrote:
Why are you using --enable-capabilities? I would first try compiling JACK with all default
settings
OK, I recompiled it with :
./configure --prefix=/usr --enable-stripped-jackd --disable-oss
--disable-portaudio --disable-coreaudio --enable-capabilities
--with-default-tmpdir=/mnt/ramfs
I think those options won't interfere with the test... Or do they?
What is the purpose of "--enable-timestamps" ? What difference does it
make enabling them?
6800
days inactive
6809
days old
linux-audio-user@lists.linuxaudio.org
27 comments
9 participants
participants (9)
-
Dave Phillips -
Erik de Castro Lopo -
Lee Revell -
Mark Knecht -
Nigel Henry -
Paul Davis -
Paul Winkler -
Salvatore Di Pietro -
tim hall