开云体育

See ;

73

vk4tux

On 2/8/24 06:58, Philip Rose, GM3ZZA via wrote:

Thanks David,

I've had a scan through that document but it does seem to rely on the system being able to differentiate between the two codec devices. I'll look at it closer in the calm light of day.

It's how I differentiate between the two devices that I need help with. I am using pulseaudio. I had managed to rename them with the rig name, but after a reboot the codec I had called IC705 was now apparently in the IC7300. So how do I tell pulseaudio that this particular physical device is the IC705 and that one the IC7300? And that this survives a reboot - even if one is not connected at the time?

Phil GM3ZZA

On 1 August 2024, at 21:31, "David Ranch, KI6ZHD via " <linuxham-fld@...> wrote:


There are lots of ways to address this depending on what Linux sound system your application trying to use.? At the lowest ALSA level, you can read up on ALSA sound device enumeration at .? Then moving up the stack, there us PortAudio (mostly deprecated now), PulseAudio (getting deprecated) and now Pipewire is the new kid on the block.? All of those systems should remember what application used which sound device automatically.

--David
KI6ZHD

I have an IC-705 and an IC-7300 and they both use the same TI Audio Codec chip. This chip does not seem to have a serial number and ICOM do not provide the serial number of the rig for the audio codec. I have been unable to find a way to distinguish them when trying to create a fool-proof means of identifying them that will survive a re-boot of my debian 12 computer.

All I can see is the physical port number in the form:
/dev/snd/by-path/pci-0000:00:14.0-usb-0:1.4:1.0 and ..../pci-0000:00:14.0-usb-0:3.4:1.0

Unless I move the USB connectors around will these always remain the same after a reboot? 
Is there any other means of distinguishing between the two devices?

Phil GM3ZZA