From: Daniel Bankmann <daniel_bankmann@arcor.de>
To: alsa-devel@alsa-project.org
Cc: Takashi Iwai <tiwai@suse.de>
Subject: Problems with X-Fi driver
Date: Mon, 01 Jun 2009 14:10:37 +0200 [thread overview]
Message-ID: <4A23C53D.8070201@arcor.de> (raw)
In-Reply-To: <mailman.1.1243850401.8236.alsa-devel@alsa-project.org>
Takashi Iwai schrieb:
> At Fri, 22 May 2009 11:54:47 +0200,
> Daniel Bankmann wrote:
>> Takashi Iwai schrieb:
>>> At Thu, 21 May 2009 09:53:23 +0200,
>>> Daniel Bankmann wrote:
>>>> Hi!
>>>>
>>>> I just tested the newest driver version with Open Suse 11.1 and
>>>> pae-kernel. I seems not to work probably, although the latest
"official"
>>>> driver by Creative worked more or less good.
>>>>
>>>> The problem is, that always, when hearing some music or any other
sound,
>>>> the signal gets interrupted every few seconds. At the other side, the
>>>> startup jingle for example is accompanied by a knock every few seconds.
>>>>
>>>> Any idea, or what information do you need to fix this?
>>> If you are using pulseaudio, try to upgrade to the one in Factory.
>>> PA on 11.1 is really a crappy version, unfortunately.
>>>
>>>
>>> Takashi
>>>
>> Hi,
>>
>> are you sure, that this is a problem with PA?
>
> Depends on your system setup. As default, PA is used on KDE and GNOME,
> regardless of h/w multi-stream functions.
>
>> Upgrading to the newest
>> version or the one in Factory seems to be a bit tricky (because auf
>> missing dependencies).
>
> You can upgrade the packages on OBS multimedia:libs repo.
>
>> Shouldn't the driver just work without PA and ESD installed? I tried
>> that out, but the problem still resists.
>
> It's not the driver to decide whether to use PA or not. It's the
> upper part.
>
> If the problem still occurs without PA (and you make sure that you
> don't use it), the issue is likely the hwptr update timing of the
> ctxfi driver. The recent PCM core has a more strict check, and
> possibly ctxfi might not provide the correct DMA position.
>
> Anyway, please check the problem occurs with which apps more exactly.
> At best, try to reproduce with aplay and speaker-test programs, i.e.
> with less complexity. And, please report back to alsa-devel ML.
> (Note that your post may appear later after manual approvals if you
> aren't subscribed yet).
>
>
> thanks,
>
> Takashi
>
Hi,
so I tried reproducing this problem. Here's a link to a wav-file which
includes tests with aplay and the starting/shutdown -jingle.
I hope this can give you a better idea of my problem;)
Daniel
http://rapidshare.com/files/239574432/output_test.wav
next parent reply other threads:[~2009-06-01 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1243850401.8236.alsa-devel@alsa-project.org>
2009-06-01 12:10 ` Daniel Bankmann [this message]
2009-06-08 19:34 ` Problems with X-Fi driver Takashi Iwai
2009-06-08 20:48 ` Daniel Bankmann
2009-06-09 1:48 ` Takashi Iwai
2009-06-09 17:01 ` Daniel Bankmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A23C53D.8070201@arcor.de \
--to=daniel_bankmann@arcor.de \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox