• Ephera@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    6 days ago

    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-profile

    If you don’t mind losing your profile selection for other devices, you can just do:

    mv ~/.local/state/wireplumber/default-profile ~/.local/state/wireplumber/default-profile.old
    

    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.

    • Zidane@lemmy.ca
      link
      fedilink
      arrow-up
      0
      ·
      6 days ago

      that worked, thank you very much!
      I have another audio question that I will probably make a post later in a help community but on the off chance you may know… I want to connect my headset mic and desktop mic to a combined input jack/device/whatever that I can use for discord etc so when I walk away from my computer I can flip down my mic on my headset and still yap… I’ve tried searching and youtube but haven’t had much luck… qpwgraph also shows my headset is mono which could be an issue? /shrug