Mic issues on later versions of 3.3

[G8VLR]

Hi all,

I have run my QO100 setup for nearly a year now. The heart of the unit is a Pluto+ which works very nicely on v3.3 (2993) with my Jabra evolve usb headset. I decided to try an update to the latest version (Feb 2024) and sound from the microphone is intermittent at sdrc start up but the footswitch ptt is working correctly. I have played with shared or exclusive use of the mic without success. Everything else works fine but with the mic issues I have reverted back to last year's version.

I don't need to update but I would like to understand the issue and correct if possible.

Regards,

Roger (G8VLR).

[Simon G4ELI]

Probably VOX kicking in? Attach a screenshot so I can see your settings.

[G8VLR]

Are these the settings you need to see Simon? https://photos.app.goo.gl/Ft2m9o5CykPdYQGu9

[Max]

Are these the settings you need to see Simon? https://photos.google.com/photo/AF1QipN ... lWdUdp9SIz

Link not working Roger, for me anyway. Maybe needs the sharing set to "everyone"?

Max

[G8VLR]

Thanks Max. Does it work now?

[Max]

Thanks Max. Does it work now?

All good now.

73

Max

[Max]

The heart of the unit is a Pluto+ which works very nicely on v3.3 (2993) with my Jabra evolve usb headset. I decided to try an update to the latest version (Feb 2024) and sound from the microphone is intermittent at sdrc start up but the footswitch ptt is working correctly. I have played with shared or exclusive use of the mic without success. Everything else works fine but with the mic issues I have reverted back to last year's version.

Hi Roger. I seem to recall from a previous post some time ago that many of the Jabra headsets do not support 48kHz sample rate? Maybe have a look at the sample rate anyway and see what it offers. Simon has said that it's essential that the sample rate of the input device is 48kHz as it's fundamental for the clocks in the audio input chain. Of course this does not explain why it was working fine in a previous build, unless it can do 48 and it's been reset to 44.1 for some reason?

Max

[G8VLR]

Hi Max, the win 10 sound settings show the Microphone as 16 bit 48kHz.

[Max]

Hi Max, the win 10 sound settings show the Microphone as 16 bit 48kHz.

Sorry Roger. I don't see anything else obvious. Maybe try with another audio source and see if it has the same issue? Frustrating.

Max

[jdow]

Just for giggles make sure 48,000 16 bit samples is set for all ins and outs. And make sure that any virtual audio devices are 48k 16 bits. There may be something in the system that has preemptively opened some ports with some other sample rate.

Ah the status bar is obscured and might have gold on it. That's mostly for future. What I am seeing here is an overloaded microphone. For a clean signal you MUST barely tickle the ALC. Anything else can lead to loud bursts or ticks every time the ALC bounces up to full scale. You also have the 20 dB boost on the microphone kicked in. What happens when you turn it off? When you overdrive transmitters all you get is more wide band noise transmitted and a distorted signal. If you overdrive hard enough your A/D converter will produce highly objectionable results, either instant flat topping or, worse, a wrap-around effect. Gentleness with the microphone can sound much better. It also cuts down on background noise transmission.

{o.o}