From: Bent Bisballe Nyeng <deva@aasimon.org>
To: alsa-devel@alsa-project.org
Subject: Re: Intel HD: ALC662 noise-bug on FitPC2i
Date: Wed, 12 Dec 2012 19:30:58 +0100 [thread overview]
Message-ID: <50C8CD62.3080303@aasimon.org> (raw)
In-Reply-To: <s5hfw3bfhn8.wl%tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 2286 bytes --]
On 12/12/12 15:51, Takashi Iwai wrote:
> At Wed, 12 Dec 2012 15:45:46 +0100,
> Bent Bisballe Nyeng wrote:
>>
>> On 12/12/12 15:25, Takashi Iwai wrote:
>>> At Wed, 12 Dec 2012 14:14:57 +0100,
>>> Bent Bisballe Nyeng wrote:
>>>>
>>>> On 12/12/12 14:05, Clemens Ladisch wrote:
>>>>> Bent Bisballe Nyeng wrote:
>>>>>> When recording, audible clicking sounds are present in the resulting
>>>>>> audio data.
>>>>>>
>>>>>> The corruption are composed of approximately 10 samples, and the
>>>>>> nature of the corrupted values are such that they could come from an
>>>>>> earlier buffer (the corrupted data resemble wav forms).
>>>>>
>>>>> This looks like a problem with your HDA controller; either the memory
>>>>> bus is overloaded so that some writes are dropped, or the hardware is
>>>>> just buggy.
>>>>>
>>>>>
>>>>> Regards,
>>>>> Clemens
>>>>
>>>> I tried to record some audio using windows 7 and here the noise was not
>>>> present indicating that it is not buggy hardware.
>>>>
>>>> Also, the system was not under load when the arecord call was made so if
>>>> the memory bus was overloaded I need another way to verify this.
>>>>
>>>> Are there any additional (useful) debugging info I can subtract from the
>>>> system that will help aiding the debugging process?
>>>
>>> Which sound backend are you using at all? Does the problem appear if
>>> you run with -Dhw for arecord?
>>>
>>> If it's using dsnoop or PulseAudio, the accuracy of DMA position
>>> reporting plays a big role. In that case, changing position_fix
>>> option cures often.
>>>
>>> Takashi
>>
>> There are no sound servers installed on the pc in question (it is a
>> 'lean' pc) so arecord should be using the hardware directly already.
>
> If you are using alsa-lib as is, it must be using dsnoop as default,
> which is pretty different from hw.
>
>
> Takashi
Running arecord with -Dhw did not solve the issue.
I played around with the buffer-size and have concluded that even with a
very large buffer the ticks are still present, precisely one tick per
buffer. This results in fever ticks with greater buffer sizes, but ticks
non-the-less.
Are there any special kernel parameters that I should set in order to
make audio smooth?
I attached my kernel config just in case.
Kind regards
Bent Bisballe Nyeng
[-- Attachment #2: config.gz --]
[-- Type: application/x-gzip, Size: 15708 bytes --]
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-12-12 18:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 14:16 [PATCH v2 1/1] ALSA: hda - use usleep_range in link reset and change timeout check mengdong.lin
2012-12-12 7:26 ` Intel HD: ALC662 noise-bug on FitPC2i Bent Bisballe Nyeng
2012-12-12 13:05 ` Clemens Ladisch
2012-12-12 13:14 ` Bent Bisballe Nyeng
2012-12-12 14:25 ` Takashi Iwai
2012-12-12 14:45 ` Bent Bisballe Nyeng
2012-12-12 14:51 ` Takashi Iwai
2012-12-12 18:30 ` Bent Bisballe Nyeng [this message]
2012-12-12 19:11 ` Takashi Iwai
2012-12-13 7:58 ` Bent Bisballe Nyeng
2012-12-13 8:08 ` Takashi Iwai
2012-12-13 9:32 ` [PATCH v2 1/1] ALSA: hda - use usleep_range in link reset and change timeout check Lin, Mengdong
2012-12-13 9:38 ` Takashi Iwai
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=50C8CD62.3080303@aasimon.org \
--to=deva@aasimon.org \
--cc=alsa-devel@alsa-project.org \
/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