Making some progress. I'm now in the maze of twisty little passages all alike.

I reverted to selecting PortAudio->pulse in fl;digi.

I found where I can connect a specific instance of fldigi to the specific audio codecs. Obvious really. Under the playback and recording tabs of pavucontrol, I can attach each app to a different code. Two problems:

1. The two apps are both called "ALSA  plug-in [fldigi]" and the two codecs are called "PCM2901 Audio Codec Analog Stereo". 
2. When I make the connections they don't survive restarting fldigi.

Yesterday I managed to rename the codecs (at least for displaying in pavucontrol). The names had reverted today. But just typing: 
pactl load-module module-device-manager 
in the terminal caused the names to reappear. Just need to be able to identify which instance of fldigi is which. But as I will usually only be using one at a time, it's no longer a big deal.

Hi Phil

Some info for your situation - I use a pulseaudio environment startup to distinguish between between an Icom and QDX. (The Exec command in a desktop file) eg

/bin/sh -c "PULSE_PROP_APPLICATION_NAME=FLDIG PULSE_SINK=alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo PULSE_SOURCE=alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo /usr/local/bin/fldigi"

/bin/sh -c "PULSE_PROP_APPLICATION_NAME=FLQDX PULSE_SINK=alsa_output.usb-QRP_Labs_QDX_Transceiver-02.analog-stereo PULSE_SOURCE=alsa_input.usb-QRP_Labs_QDX_Transceiver-02.analog-stereo /usr/local/bin/fldigiqdx --home-dir /home/bcameron/.fldigi.qdx"

One would assume that for two Icom radios with the same codec hardware would be numbered CODEC-00 and CODEC-01. The above then removes the need to use pactl or pavucontrol to link app<>port

Pulseaudio is suppose to remember each applications volume etc settings based on (I think) an application name provided by the application itself. I haven't delved into why but that doesn't seem to happen with fldigi. I don't think the PULSE_PROP_APPLICATION_NAME=FLDIG works either.

load-module module-device-manager probably has to be done in /etc/pulse/system.pa or the equivalent user location

Cheers Bob VK2YQA

Making some progress. I'm now in the maze of twisty little passages all alike.

I reverted to selecting PortAudio->pulse in fl;digi.

I found where I can connect a specific instance of fldigi to the specific audio codecs. Obvious really. Under the playback and recording tabs of pavucontrol, I can attach each app to a different code. Two problems:

1. The two apps are both called "ALSA  plug-in [fldigi]" and the two codecs are called "PCM2901 Audio Codec Analog Stereo". 
2. When I make the connections they don't survive restarting fldigi.

Yesterday I managed to rename the codecs (at least for displaying in pavucontrol). The names had reverted today. But just typing: 
pactl load-module module-device-manager 
in the terminal caused the names to reappear. Just need to be able to identify which instance of fldigi is which. But as I will usually only be using one at a time, it's no longer a big deal.

Thanks Bob,

The two icoms get enumerated ok, but the enumeration changed after a reboot. Probably as a result of adding the IC705 after the previous reboot. It seems to be stable since.

The two FLdigi instances identify themselves to pulseaudio as the same.

It's the understanding how to enscript this that I lack.

Phil GM3ZZA

Hi Phil

Enumeration depends on the polling order of the PC and whether the rig(s) are on at the time. If both rigs are on every time you reset the PC's USB bus and the plugs remain in the same sockets they will get the same "number" "order". In most cases then cycling a single rig's power off/on will bring back the same "number", but it kind of depends on how it dies. Sometimes you'll get an entirely new "number".

I hope I made that clear hihi. I think being aware of the reason is important.

If one wanted full automation and perfect response every time the next step IMO would be to interrogate each of the USB serial ports created using the CI-V. ie to differentiate between Icom rig models. Then use that info to name the relevant hardware. My USB serial port on the Icom is /dev/icom9100a for example, but I do that through udev, not manual naming.

I'd suggest though that it is simpler to just leave both rigs on, or hot unplug/plug them in the same order if things get messed up. That will also enumerate the same audio/codec port number. Additionally I'd suggest only adjust pavucontrol as a last resort.

At some stage with both rigs connected issue the terminal command "pactl list" to verify the sound port names I have used below.

The fldigi start commands (which can be entered in a terminal window) might then be;

PULSE_SINK=alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo PULSE_SOURCE=alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo /usr/local/bin/fldigi --home-dir /home/<user>/.fldigi.ic705

and

PULSE_SINK=alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-01.analog-stereo PULSE_SOURCE=alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-01.analog-stereo /usr/local/bin/fldigi --home-dir /home/<user>/.fldigi.ic7300

Somewhere before there you might also need to create a device link for the serial ports so that fldigi "sees" a name like /dev/ic7300a and /dev/ic705a. Not a problem though if both rigs always powered and plugged in at the same ports.

Sorry its getting kind of complex, but happy to elaborate or take off list.

Cheers Bob VK2YQA

On 18/4/24 04:48, Philip Rose, GM3ZZA via groups.io wrote:

Thanks Bob,

The two icoms get enumerated ok, but the enumeration changed after a reboot. Probably as a result of adding the IC705 after the previous reboot. It seems to be stable since.

The two FLdigi instances identify themselves to pulseaudio as the same.

It's the understanding how to enscript this that I lack.

Phil GM3ZZA