From: Wilfried Weissmann <Wilfried.Weissmann@gmx.at>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: "Eloy A. Paris" <peloy@chapus.net>, alsa-devel@lists.sourceforge.net
Subject: Re: Occasional metallic sound when recording (cs46xx)
Date: Thu, 23 Oct 2003 20:37:39 +0200 [thread overview]
Message-ID: <3F981FF3.4040902@gmx.at> (raw)
In-Reply-To: 200310221739.h9MHd0m1024945@oud.linuxaudiosystems.com
Paul Davis wrote:
>>This problem happens randomly but is very annoying, specially if I
>>program my PVR (MythTV) to automatically record a show - the show can
>>get recorded with metallic sound, which makes it very hard to understand
>>during playback.
>>
>>This is not MythTV-specific since I have been able to reproduce the
>>problem using other applications, like the Gnome sound recorder. It is
>>unrelated to full-duplex operation since when recording a show MythTV
>>doesn't open /dev/dsp for writing.
>>
>>I really have no idea about how to troubleshoot this. I don't think
>>the problem is hardware, but is driver-related instead.
>
>
> its almost certainly a software problem in mythTV and gnome sound
> recorder. i've written code that does this several times - every time
> it takes me ages to figure out why, and then i can never remember when
> i do it the next time. its related to off-by-1 errors in processing
> incoming audio.
i also have the same problem with speakfreely with my cs46xx. it does
not look like the metallic sound is triggered by any specific event
(load, I/O,...). out of the sudden somethings goes wrong. i think i also
experienced it with the kde sound recorder. but i have not updated the
alsa driver for a while (still 0.9.5 or so). toggleing the ADC sounds
like a good idea. i have not tried that yet but reloading the modules
works too.
>
> not necessarily, of course, just a point of view.
hmm, what makes something sound metallic anyway? echo?
bye,
wilfried
-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community? Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
next prev parent reply other threads:[~2003-10-23 18:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 16:22 Occasional metallic sound when recording (cs46xx) Eloy A. Paris
2003-10-22 17:39 ` Paul Davis
2003-10-23 14:49 ` Eloy A. Paris
2003-10-23 18:37 ` Wilfried Weissmann [this message]
2003-10-23 19:01 ` Eloy A. Paris
2003-10-23 19:56 ` Joe
2003-10-23 20:51 ` Manuel Jander
2003-10-24 13:18 ` Takashi Iwai
2003-11-05 15:08 ` Eloy A. Paris
2003-11-05 15:49 ` Florian Schmidt
[not found] ` <3FAAC709.8050509@cucumelo.org>
2003-11-07 17:05 ` Takashi Iwai
2003-11-07 23:19 ` Eloy A. Paris
2003-11-08 1:33 ` Paul Davis
2003-11-23 23:27 ` Christian Esken
2003-10-23 20:12 ` Ray Heasman
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=3F981FF3.4040902@gmx.at \
--to=wilfried.weissmann@gmx.at \
--cc=alsa-devel@lists.sourceforge.net \
--cc=paul@linuxaudiosystems.com \
--cc=peloy@chapus.net \
/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