I’m guessing, the recording device doesn’t like that profile and just crashes right away. And when it has crashed, it won’t show up in the list of available devices.
Now, how is that profile remembered even when the device disconnects? Apparently, a component called “WirePlumber” is responsible for that.
And it stores this information in: ~/.local/state/wireplumber/default-profile
If you don’t mind losing your profile selection for other devices, you can just do:
and then do a reboot.
After the reboot, your recording device should be back.
If you do mind losing the other profiles, then make a backup of that file and try to remove lines related to your recording device, and again do a reboot to test it.
For me, it was a device which had both input and output, and I had to remove both lines before it recognized it as unconfigured.
So, I’m actually able to reproduce that and then had to fix it myself. 😅
The “Pro Audio” profile seems to be a PipeWire thing: https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/FAQ#what-is-the-pro-audio-profile
I’m guessing, the recording device doesn’t like that profile and just crashes right away. And when it has crashed, it won’t show up in the list of available devices.
Now, how is that profile remembered even when the device disconnects? Apparently, a component called “WirePlumber” is responsible for that.
And it stores this information in:
~/.local/state/wireplumber/default-profileIf you don’t mind losing your profile selection for other devices, you can just do:
and then do a reboot.
After the reboot, your recording device should be back.
If you do mind losing the other profiles, then make a backup of that file and try to remove lines related to your recording device, and again do a reboot to test it.
For me, it was a device which had both input and output, and I had to remove both lines before it recognized it as unconfigured.