Am Freitag, dem 04.02.2022 um 10:43 +0100 schrieb Martin Kepplinger:
> Am Donnerstag, dem 03.02.2022 um 11:05 +0000 schrieb Charles Keepax:
> > On Thu, Feb 03, 2022 at 10:57:44AM +0100, Martin Kepplinger wrote:
> > > Am Mittwoch, dem 02.02.2022 um 13:35 +0000 schrieb Charles
> > > Keepax:
> > > > On Wed, Feb 02, 2022 at 12:55:04PM +0100, Martin Kepplinger
> > > > wrote:
> > > > > Am Mittwoch, dem 02.02.2022 um 10:46 +0000 schrieb Charles
> > > > > Keepax:
> > > > > > On Wed, Feb 02, 2022 at 11:17:34AM +0100, Martin Kepplinger
> > > > > > wrote:
> > > > > > > Am Mittwoch, dem 02.02.2022 um 09:53 +0000 schrieb
> > > > > > > Charles
> > > > > > > Keepax:
> > > > > > > > On Tue, Feb 01, 2022 at 04:01:13PM +0100, Martin
> > > > > > > > Kepplinger
> > > > > > > > wrote:
> > > > > Volume / sensitivity of Analog input is too low, I saw that
> > > > > before.
> > > > > What would you try to change that?
> > > > >
> > > >
> > > > Hmm... you say you saw this before? I assume the input volume
> > > > is always low, not just low sometimes? I would probably start
> > > > by
> > > > checking the voltage you have on the micbias, make sure that is
> > > > as expected. Does the signal coming into the IN3R pin look low
> > > > on
> > > > a scope or is it just the level after it has been through the
> > > > ADC
> > > > on the chip that seems low?
> > >
> > > Literally *no* effort went into this yet :) All I see is when I
> > > set
> > > the
> > > "headset mic" volume to max in gnome settings, the recorded
> > > volume
> > > is
> > > something like "almost usable", so that's off a bit.
> > >
> > > I can't easily measure, but different headset mics produce
> > > similar
> > > volume.
> > >
> >
> > No problem keep me posted any additional tests/info you guys get
> > might help out here. Looking through your routing I think you are
> > sending the mic directly to the speaker, I would definitely test
> > capturing the signal over the I2S as well to confirm it is
> > consistently a low volume on both paths.
> >
> > > :) thank you very much so far. You already really helped. We can
> > > even
> > > make the mic available now (to enable manually by the user) while
> > > we
> > > look into the volume and detection.
> > >
> >
> > Happy to help, please feel free to keep the questions/debug info
> > coming.
>
> yes my bad :) If I may, just let me describe my situation again and
> see
> whether anything else comes to your mind.
>
> It's weird but I when I set "Capture Volume" to 60 instead of 29, I
> didn't hear a difference.
>
> So far I don't hear a difference when setting "INPGAR IN1R Switch"
> on.
>
> Does "Value" in this ucm description make any sense to you?
>
> EnableSequence [
> cset "name='Digital Capture Volume' 127,127"
> cset "name='Capture Volume' 63,63"
> cset "name='MIXINR IN3R Switch' on"
> cset "name='MIXINR IN3R Volume' 7"
> cset "name='INPGAR IN1R Switch' on"
> cset "name='Input Mode' Analog"
> ]
>
> DisableSequence [
> cset "name='INPGAR IN1R Switch' off"
> cset "name='MIXINR IN3R Switch' off"
> cset "name='MIXINR IN3R Volume' 0"
> cset "name='Input Mode' Digital"
> ]
>
> Value {
> CapturePriority "100"
> CaptureChannels "2"
> CaptureSwitch "name='MIXINR IN3R Volume'"
sorry, of course this is a typo I've fixed: CaptureVolume
>
> CaptureSwitch "name='MIXINR IN3R Switch'"
> CapturePCM "hw:${CardId},0"
> JackControl "Headphones Jack"
I know this is a workaround until I have mic detection.
>
> }
>
>
> Let me just append the correct amixer contents where I hear my usual
> "quiet and bad signal" recording:
>
>
