-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] plain arecord issue found when testing RT711 headset recording on TGLU_SKU0A3E_SDW #3804
Comments
@shumingfan , could you please take a look at this issue? We have a similar issue on RT714:#3766 and we changed the |
@keqiaozhang I can't reproduce this issue on SKU_0A5D which installed Ubuntu 22.04. |
@shumingfan, I still can reproduce the issue with above steps.
|
@bardliao can you chime in out this one reported by @keqiaozhang and @shumingfan? it's my understanding that if we have an issue with the loopback, then the problem is NOT the codec settings. The loopback will discard the data from the codec . Am I right? |
@keqiaozhang Thanks for the testing. |
@plbossart @shumingfan @keqiaozhang Sure, I will look into it. |
@shumingfan I have checked with Bard. First we need to set the PGA* capture volume to 0dB:
Then even with the default value of For the loopback mode. I did the wrong steps before, I need to keep the playback running when doing the capture.
|
Why is this needed @keqiaozhang ? All the PGA volumes should be set to 0dB already, If this is not the case, then something or someone changed those settings in the past. We should NEVER have any PGA gains set to anything other than 0dB |
@plbossart 50 is 0dB, and it was 80 which is 30dB while we met the issue. |
@bardliao why was it set to 80, that's what I don't understand. |
It seems that |
@keqiaozhang all PGA volumes should be set to 0dB or 100%. We should do this with a script so that any changes in names or topology are supported. So far I only found this hack but I am sure it can be improved:
|
I have submitted thesofproject/sof-test#953. Please help to review. |
can we close this issue @keqiaozhang ? |
This issue is fixed by thesofproject/sof-test#953. Closing this issue. |
Describe the bug
We observed this issue after upgrading Ubuntu from 20.04 to 22.04. The issue is that when testing plain arecord on headset, the Max peak will be reached to 100% in verbose logs, it should be 0%.
Checked the amixer setting, this issue is related to control 'rt711 ADC 08 Capture Volume'. The default value set in UCM2 is
63
.please refer to https://github.com/alsa-project/alsa-ucm-conf/blob/master/ucm2/codecs/rt711/init.conf.
The issue will disappear if I change the volume to 0:
amixer -c sofsoundwire cset name='rt711 ADC 08 Capture Volume' 0
The text was updated successfully, but these errors were encountered: