Re: [alsa-devel] [Alsa-user] Metallic recording in cs46xx on Thinkpad T22
On 11-03-08 08:24, Gadi Oron wrote:
I am trying to record sound on an old Thinkpad T22 that uses the cs46xx sound driver.
Each time you start to record you have a 10% chance of having the recording completely distorted and having a metallic sound. When you look at the waveform it looks as though there are small segments with sharp transitions between them, a little like if these segments were moved a little from their correct place.
No insights, but I confirm the bug with a TerraTec DMX XFire 1024 (CS4624).
Rene.
At Tue, 11 Mar 2008 23:01:39 +0100, Rene Herman wrote:
On 11-03-08 08:24, Gadi Oron wrote:
I am trying to record sound on an old Thinkpad T22 that uses the cs46xx sound driver.
Each time you start to record you have a 10% chance of having the recording completely distorted and having a metallic sound. When you look at the waveform it looks as though there are small segments with sharp transitions between them, a little like if these segments were moved a little from their correct place.
No insights, but I confirm the bug with a TerraTec DMX XFire 1024 (CS4624).
Hm, cs46xx driver hasn't been much changes since long time ago (around year 2005). The only big change was about some PM fixes, and I don't think it's relevant... Could you run als-info.sh to get the status?
Takashi
On 12-03-08 15:43, Takashi Iwai wrote:
At Tue, 11 Mar 2008 23:01:39 +0100, Rene Herman wrote:
On 11-03-08 08:24, Gadi Oron wrote:
I am trying to record sound on an old Thinkpad T22 that uses the cs46xx sound driver.
Each time you start to record you have a 10% chance of having the recording completely distorted and having a metallic sound. When you look at the waveform it looks as though there are small segments with sharp transitions between them, a little like if these segments were moved a little from their correct place.
No insights, but I confirm the bug with a TerraTec DMX XFire 1024 (CS4624).
Hm, cs46xx driver hasn't been much changes since long time ago (around year 2005). The only big change was about some PM fixes, and I don't think it's relevant... Could you run als-info.sh to get the status?
At:
Script was run just after repeating the problem. I have two of these same cards (TerraTec DMX XFire 1024) by the way and the same thing happens on both. If desperately need be, I can also test a CS4630 in the form of a TerraTec SiXPack 5.1+.
This may indeed have been broken for a long time. I (sometimes) use this card in a little P1-133 machine in my living room to feed music to my regular amp and, seldomly, use it to record from for example LP.
Last time that I did was some 2 months ago and I experienced the problem and at the time I remembered seeing that problem before, which may well have been 2005. As said, it doesn't happen each time and I use recording on that card seldomly...
I expect this is going to be difficult to debug. It's no doubt a timing problem and yes, Gadi's description matches. This is what a bad capture sounds like:
http://members.home.nl/rene.herman/cs4624-bad-capture.wav
(a good capture is just, well, good)
Didn't report it before since when I'm recording on that thing I'm recording for someone else and when I'm busy trying to do something _with_ a computer instead of _to_ a computer, all those pesky little linux problems just get on my nerves so incredibly bad at times...
Rene.
At Wed, 12 Mar 2008 17:39:48 +0100, Rene Herman wrote:
On 12-03-08 15:43, Takashi Iwai wrote:
At Tue, 11 Mar 2008 23:01:39 +0100, Rene Herman wrote:
On 11-03-08 08:24, Gadi Oron wrote:
I am trying to record sound on an old Thinkpad T22 that uses the cs46xx sound driver.
Each time you start to record you have a 10% chance of having the recording completely distorted and having a metallic sound. When you look at the waveform it looks as though there are small segments with sharp transitions between them, a little like if these segments were moved a little from their correct place.
No insights, but I confirm the bug with a TerraTec DMX XFire 1024 (CS4624).
Hm, cs46xx driver hasn't been much changes since long time ago (around year 2005). The only big change was about some PM fixes, and I don't think it's relevant... Could you run als-info.sh to get the status?
At:
The output seems truncated. Could you give the generated file via "alsactl -f somefile store", just to be sure ?
Takashi
On 12-03-08 17:59, Takashi Iwai wrote:
At Wed, 12 Mar 2008 17:39:48 +0100, Rene Herman wrote:
On 12-03-08 15:43, Takashi Iwai wrote:
At Tue, 11 Mar 2008 23:01:39 +0100, Rene Herman wrote:
On 11-03-08 08:24, Gadi Oron wrote:
I am trying to record sound on an old Thinkpad T22 that uses the cs46xx sound driver.
Each time you start to record you have a 10% chance of having the recording completely distorted and having a metallic sound. When you look at the waveform it looks as though there are small segments with sharp transitions between them, a little like if these segments were moved a little from their correct place.
No insights, but I confirm the bug with a TerraTec DMX XFire 1024 (CS4624).
Hm, cs46xx driver hasn't been much changes since long time ago (around year 2005). The only big change was about some PM fixes, and I don't think it's relevant... Could you run als-info.sh to get the status?
At:
The output seems truncated. Could you give the generated file via "alsactl -f somefile store", just to be sure ?
Hmm, alsa-info.sh freshly downloaded from current hg. Anyways:
Rene.
state.CS46xx { control.1 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'Master Playback Switch' value true } control.2 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 63' iface MIXER name 'Master Playback Volume' value.0 63 value.1 63 } control.3 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'Headphone Playback Switch' value true } control.4 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 63' iface MIXER name 'Headphone Playback Volume' value.0 0 value.1 0 } control.5 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'Mic Playback Switch' value false } control.6 { comment.access 'read write' comment.type INTEGER comment.count 1 comment.range '0 - 31' iface MIXER name 'Mic Playback Volume' value 0 } control.7 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'Mic Boost (+20dB)' value false } control.8 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'Line Playback Switch' value false } control.9 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 31' iface MIXER name 'Line Playback Volume' value.0 23 value.1 23 } control.10 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'CD Playback Switch' value false } control.11 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 31' iface MIXER name 'CD Playback Volume' value.0 0 value.1 0 } control.12 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'Aux Playback Switch' value false } control.13 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 31' iface MIXER name 'Aux Playback Volume' value.0 0 value.1 0 } control.14 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'PCM Playback Switch' value true } control.15 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 31' iface MIXER name 'PCM Playback Volume' value.0 23 value.1 23 } control.16 { comment.access 'read write' comment.type ENUMERATED comment.count 2 comment.item.0 Mic comment.item.1 CD comment.item.2 Video comment.item.3 Aux comment.item.4 Line comment.item.5 Mix comment.item.6 'Mix Mono' comment.item.7 Phone iface MIXER name 'Capture Source' value.0 Line value.1 Line } control.17 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'Capture Switch' value true } control.18 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 15' iface MIXER name 'Capture Volume' value.0 0 value.1 0 } control.19 { comment.access 'read write' comment.type ENUMERATED comment.count 1 comment.item.0 'pre 3D' comment.item.1 'post 3D' iface MIXER name 'PCM Out Path & Mute' value 'pre 3D' } control.20 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name '3D Control - Switch' value false } control.21 { comment.access 'read write' comment.type INTEGER comment.count 1 comment.range '0 - 15' iface MIXER name '3D Control - Center' value 0 } control.22 { comment.access 'read write' comment.type INTEGER comment.count 1 comment.range '0 - 15' iface MIXER name '3D Control - Depth' value 0 } control.23 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'Off-hook Switch' value false } control.24 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'Caller ID Switch' value false } control.25 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 32767' iface MIXER name 'DAC Volume' value.0 29493 value.1 29493 } control.26 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 32767' iface MIXER name 'ADC Volume' value.0 29492 value.1 29492 } control.27 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'ADC Capture Switch' value true } control.28 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'DAC Capture Switch' value false } control.29 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'IEC958 Output Switch' value false } control.30 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'IEC958 Input Switch' value false } control.31 { comment.access 'read write' comment.type IEC958 comment.count 1 iface PCM device 2 name 'IEC958 Playback Default' value '0082000200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000' } control.32 { comment.access read comment.type IEC958 comment.count 1 iface PCM device 2 name 'IEC958 Playback Mask' value ffff00ff00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 } control.33 { comment.access 'read write' comment.type IEC958 comment.count 1 iface PCM device 2 name 'IEC958 Playback PCM Stream' value '0082000200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000' } control.34 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER name 'Duplicate Front' value false } }
At Wed, 12 Mar 2008 18:17:43 +0100, Rene Herman wrote:
On 12-03-08 17:59, Takashi Iwai wrote:
At Wed, 12 Mar 2008 17:39:48 +0100, Rene Herman wrote:
On 12-03-08 15:43, Takashi Iwai wrote:
At Tue, 11 Mar 2008 23:01:39 +0100, Rene Herman wrote:
On 11-03-08 08:24, Gadi Oron wrote:
I am trying to record sound on an old Thinkpad T22 that uses the cs46xx sound driver.
Each time you start to record you have a 10% chance of having the recording completely distorted and having a metallic sound. When you look at the waveform it looks as though there are small segments with sharp transitions between them, a little like if these segments were moved a little from their correct place.
No insights, but I confirm the bug with a TerraTec DMX XFire 1024 (CS4624).
Hm, cs46xx driver hasn't been much changes since long time ago (around year 2005). The only big change was about some PM fixes, and I don't think it's relevant... Could you run als-info.sh to get the status?
At:
The output seems truncated. Could you give the generated file via "alsactl -f somefile store", just to be sure ?
Hmm, alsa-info.sh freshly downloaded from current hg.
Is the original data also truncated at the middle or is it a paste.bin problem?
control.26 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 32767' iface MIXER name 'ADC Volume' value.0 29492 value.1 29492 }
Try to put this to full once.
Takashi
Hopefully it is full now.
On Thu, Mar 13, 2008 at 12:48 PM, Takashi Iwai tiwai@suse.de wrote:
At Wed, 12 Mar 2008 18:17:43 +0100, Rene Herman wrote:
On 12-03-08 17:59, Takashi Iwai wrote:
At Wed, 12 Mar 2008 17:39:48 +0100, Rene Herman wrote:
On 12-03-08 15:43, Takashi Iwai wrote:
At Tue, 11 Mar 2008 23:01:39 +0100, Rene Herman wrote:
On 11-03-08 08:24, Gadi Oron wrote:
> I am trying to record sound on an old Thinkpad T22 that uses the
cs46xx
> sound driver. > > Each time you start to record you have a 10% chance of having the > recording completely distorted and having a metallic sound. When
you
> look at the waveform it looks as though there are small segments
with
> sharp transitions between them, a little like if these segments
were
> moved a little from their correct place. No insights, but I confirm the bug with a TerraTec DMX XFire 1024
(CS4624).
Hm, cs46xx driver hasn't been much changes since long time ago
(around
year 2005). The only big change was about some PM fixes, and I
don't
think it's relevant... Could you run als-info.sh to get the status?
At:
The output seems truncated. Could you give the generated file via "alsactl -f somefile store", just to be sure ?
Hmm, alsa-info.sh freshly downloaded from current hg.
Is the original data also truncated at the middle or is it a paste.bin problem?
control.26 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 32767' iface MIXER name 'ADC Volume' value.0 29492 value.1 29492 }Try to put this to full once.
Takashi
At Thu, 13 Mar 2008 14:11:30 +0200, Gadi Oron wrote:
Hopefully it is full now.
Well, the content is now full but I mean to adjust "ADC Volume" to the full value, 32767... :)
thanks,
Takashi
On Thu, Mar 13, 2008 at 12:48 PM, Takashi Iwai tiwai@suse.de wrote:
At Wed, 12 Mar 2008 18:17:43 +0100, Rene Herman wrote: > > On 12-03-08 17:59, Takashi Iwai wrote: > > > At Wed, 12 Mar 2008 17:39:48 +0100, > > Rene Herman wrote: > >> On 12-03-08 15:43, Takashi Iwai wrote: > >> > >>> At Tue, 11 Mar 2008 23:01:39 +0100, > >>> Rene Herman wrote: > >>>> On 11-03-08 08:24, Gadi Oron wrote: > >>>> > >>>>> I am trying to record sound on an old Thinkpad T22 that uses the cs46xx > >>>>> sound driver. > >>>>> > >>>>> Each time you start to record you have a 10% chance of having the > >>>>> recording completely distorted and having a metallic sound. When you > >>>>> look at the waveform it looks as though there are small segments with > >>>>> sharp transitions between them, a little like if these segments were > >>>>> moved a little from their correct place. > >>>> No insights, but I confirm the bug with a TerraTec DMX XFire 1024 (CS4624). > >>> Hm, cs46xx driver hasn't been much changes since long time ago (around > >>> year 2005). The only big change was about some PM fixes, and I don't > >>> think it's relevant... Could you run als-info.sh to get the status? > >> At: > >> > >> http://pastebin.ca/939784 > > > > The output seems truncated. Could you give the generated file via > > "alsactl -f somefile store", just to be sure ? > > Hmm, alsa-info.sh freshly downloaded from current hg. Is the original data also truncated at the middle or is it a paste.bin problem? > control.26 { > comment.access 'read write' > comment.type INTEGER > comment.count 2 > comment.range '0 - 32767' > iface MIXER > name 'ADC Volume' > value.0 29492 > value.1 29492 > } Try to put this to full once. Takashi
On 13-03-08 11:48, Takashi Iwai wrote:
Hmm, alsa-info.sh freshly downloaded from current hg.
Is the original data also truncated at the middle or is it a paste.bin problem?
The script only uploaded it. When I intervene and look at /tmp/alsa-info.txt manually it's complete but when I just now retried the output on pastebin.ca is again truncated:
control.26 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 32767' iface MIXER name 'ADC Volume' value.0 29492 value.1 29492 }
Try to put this to full once.
No change. Also no change with capturing at 48000/16/2 (previous 44100/16/2) nor 44100/8/2, nor 44100/16/1.
Rene.
participants (3)
-
Gadi Oron -
Rene Herman -
Takashi Iwai