Hi
I had also this problem and I discovered it was a jackd bug. I think
it's not a problem of anything else. I can reproduce it with a powerful
machine only playing a song with xmms connected to jack.
if you want to hear what I listen:
(maybe we've got different problems)
I wrote to the jackd devel list and they told me that I could solve it
switching to 48k (instead of the 44k I used).
I did it and the problem disappeared. But they were quite sceptical
about solving the problem with 44k...
First we though it was an audigy issue and they told me that even the
best drivers of the audigy for windows (I can't remember the name but it
starts with k...), have the 44k option as experimental...
However then sbdy reported the same problem with another card...
Talk to the guys of the jack devel list. I think we should try to solve
this issue or *at least warn the users* (maybe with a jackd comment)
that 44k won't work... don't you think?
En/na Kevin Ernste ha escrit:
I'm not sure this is just an Audigy issue.
I see/hear this issue all the time lately with my HDSP multiface and
on another machine at school with a Delta 1010. I would describe it
as more of a comb-filtered sound but as Julien mentioned it does not
show up in a recording. JACK itself seems to be feeding the audio
just fine internally, but the alsa outputs are monitoring these
artifacts/coloring. Reseting the server clears it.
It often happens when I connect or disconnect a client, but it can
also simply appear when connected for longer stretches. When this
happens the JACK session shows no xruns and it doesn't seem/sound
related to sampling rate or even system load. I can be playing a
stereo file with ecasound or feeding a complex mulitchannel Ardour
session though JAMin...and it happens on a PIII I have at home and the
Athlon 64 with 2GB RAM at school (both highly tuned PlanetCCRMA
boxen).
Kevin
On Fri, 25 Mar 2005 13:37:19 -0500, Lee Revell <rlrevell(a)joe-job.com> wrote:
On Fri, 2005-03-25 at 17:11 +0200, Esa Linna
wrote:
Any suggestions & tips worth to try? Thanks.
You are running at 48Khz and not 44.1, right?
Lee