Re: audio interface stability for wsjtx/fldigi

[Drew Arnett <arnett.drew@gmail.com>]

I hadn't bothered using that, yet, as it was easy enough to remember
to set the mix to 0 for RX and -30 for TX.  :-)  Actually jotted on a
cheat sheet.  Several transceiver settings changes between normal
operation, soundcard modes, and transverters, so notes was starting to
be useful.  :-)  But yeah, I'll definitely look at using that feature
to save/restore settings; sounds like a nice process simplification.

Thanks!

On Fri, Nov 10, 2023 at 10:50 AM Alan Crosswell <n2ygk@weca.org> wrote:
>
> Did you try `alsactl store` to save your changed alsamixer settings?
>
> On Fri, Nov 10, 2023 at 5:26 AM Christoph Berg <myon@debian.org> wrote:
>>
>> Re: Drew Arnett
>> > The name of the stream in puavcontrol isn't very useful:
>> > 'QtPulseAudio:10932: QtmPUlseStream-10923-140632395886544 from'.  I
>> > wonder if wsjtx can have the Qt library identify this stream with a
>> > more useful label?
>>
>> I was looking into this some time ago. It looks like Qt simply has no
>> way to set the name of the output stream.
>>
>> > I think pulseaudio is installed by default for most debian desktops?
>>
>> It should have been replaced by pipewire in the default setup now.
>> Afaict things just continue to work normally, including using
>> pavucontrol to configure which app plays on which device.
>>
>> > Without installing/removing packages, can I just ignore pulseaudio to
>> > setup and use wsjtx/fldigi/quisk et al?
>>
>> It just works for me, and I do have a lot of audio devices on the
>> shack computer.
>>
>> Christoph
>>