I ran Fldigi from the terminal and noticed this happening when I changed modes.? ?Funny thing is it only happened after I keyed up once to tune.? Prior to tuning it wouldn't freeze.??

?

Here is the debug output.??

?

Expression 'ValidateParameters( inputParameters, hostApi, StreamDirection_In )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1838
Expression 'ret' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1736
Expression 'AlsaOpen( hostApi, parameters, streamDir, &pcm )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1768

?

I don't know if this is any insight but again any direction would be appreciated.? Thanks

Hi Greg

I don't know Ubuntu's default sound system, but the error message suggests fldigi is trying to run pulseaudio? My first thought was that pulseaudio was going to into idle too fast. I had that problem with another app so I commented out;

load-module module-suspend-on-idle

from the relevant ca files in /etc/pulse

The "ret" expression failure might also suggest you have an errant server string in the fldigi config soundcard devices pulseaudio setup. Just leave it blank if you are using pulse.

I suggest first however that it would be best to ensure that your Ubuntu has whatever sound system you want to use, then make sure fldigi matches that. Current Linux OS's are generally migrating towards pipewire.

Cheers Bob VK2YQA

On 26/8/24 13:49, Greg Cheng - KC3SMW wrote:

I ran Fldigi from the terminal and noticed this happening when I changed modes.? ?Funny thing is it only happened after I keyed up once to tune.? Prior to tuning it wouldn't freeze.??

?

Here is the debug output.??

?

Expression 'ValidateParameters( inputParameters, hostApi, StreamDirection_In )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1838
Expression 'ret' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1736
Expression 'AlsaOpen( hostApi, parameters, streamDir, &pcm )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1768

?

I don't know if this is any insight but again any direction would be appreciated.? Thanks

Thank you Bob and Ron.

?

I'll have to look into pipe wire.??

?

Currently I am using the portaudio to select my FT710's soundcard.? ?And I adjust my volumes with AlsaMixer.? Never been a fan of pulseaudio.??

?

Last night I purged alsa-base and also-utils and reinstalled them.? Rebooted and no change.??

?

On a whim I tried the pulseaudio selection and adjusted my settings thru pavucontrol. And no issues with pausing between mode changes or error messages in the terminal....? So it must be an alsa thing....??

?

Okay thanks guys!? ?I'll be looking into pipewire?

?

?

Just for reference Greg, Pulseaudio does in fact run "on top" of ALSA and generally the user no longer accesses ALSA directly (if that makes sense) If one (for example) grants the user, audio group membership all types of strange things happen as it tries to seize control and blocks Pulseaudio from using the hardware. ie the daemon user "pulseaudio" is a member of "audio", not the console user.

This is why your ALSA reinstall didn't help. The logical step to change to ALSA only is actually to remove Pulseaudio itself, but that has often been embedded as a basic setup on some distros. Best read up on how to do that safely with yours.

IMO Pulseaudio's main claim to fame is the ability to share the sound devices across multiple user applications, whilst retaining individual volume settings and other choices. Basic ALSA doesn't do that. I believe Pipewire does.

Bob VK2YQA

On 26/8/24 22:32, Greg Cheng - KC3SMW wrote:

Thank you Bob and Ron.

?

I'll have to look into pipe wire.??

?

Currently I am using the portaudio to select my FT710's soundcard.? ?And I adjust my volumes with AlsaMixer.? Never been a fan of pulseaudio.??

?

Last night I purged alsa-base and also-utils and reinstalled them.? Rebooted and no change.??

?

On a whim I tried the pulseaudio selection and adjusted my settings thru pavucontrol. And no issues with pausing between mode changes or error messages in the terminal....? So it must be an alsa thing....??

?

Okay thanks guys!? ?I'll be looking into pipewire?

?

?

Just for reference Greg, Pulseaudio does in fact run "on top" of ALSA and generally the user no longer accesses ALSA directly (if that makes sense) If one (for example) grants the user, audio group membership all types of strange things happen as it tries to seize control and blocks Pulseaudio from using the hardware. ie the daemon user "pulseaudio" is a member of "audio", not the console user.

This is why your ALSA reinstall didn't help. The logical step to change to ALSA only is actually to remove Pulseaudio itself, but that has often been embedded as a basic setup on some distros. Best read up on how to do that safely with yours.

IMO Pulseaudio's main claim to fame is the ability to share the sound devices across multiple user applications, whilst retaining individual volume settings and other choices. Basic ALSA doesn't do that. I believe Pipewire does.

Bob VK2YQA

On 26/8/24 22:32, Greg Cheng - KC3SMW wrote:

Thank you Bob and Ron.

?

I'll have to look into pipe wire.??

?

Currently I am using the portaudio to select my FT710's soundcard.? ?And I adjust my volumes with AlsaMixer.? Never been a fan of pulseaudio.??

?

Last night I purged alsa-base and also-utils and reinstalled them.? Rebooted and no change.??

?

On a whim I tried the pulseaudio selection and adjusted my settings thru pavucontrol. And no issues with pausing between mode changes or error messages in the terminal....? So it must be an alsa thing....??

?

Okay thanks guys!? ?I'll be looking into pipewire?

?

?