search

saivert / pwvucontrol

Pipewire Volume Control
GNU General Public License v3.0
262 stars 8 forks source link

Reporting incorrect profile for Bluetooth headphones #9

Closed poperigby closed 4 months ago

poperigby commented 5 months ago

I've noticed a discrepancy between pwvucontrol and Blueman and wpctl.

Both Blueman and wpctl inspect <DEVICE-ID> are showing a2dp-sink for my Shure 50 headphone's profile, but pwvucontrol is reporting None. I keep changing it in pwvu control but it switches back when I close and open it again.

pwvucontrol version: 0.1.0

Output of wpctl inspect <DEVICE-ID>:

id 218, type PipeWire:Interface:Node
    api.bluez5.address = "00:0E:DD:0C:47:E5"
    api.bluez5.codec = "ldac"
    api.bluez5.profile = "a2dp-sink"
    api.bluez5.transport = ""
    audio.adapt.follower = ""
    bluez5.loopback = "false"
    card.profile.device = "1"
  * client.id = "42"
    clock.quantum-limit = "8192"
    device.api = "bluez5"
  * device.id = "168"
    device.routes = "1"
  * factory.id = "11"
    factory.mode = "merge"
    factory.name = "api.bluez5.a2dp.sink"
    library.name = "audioconvert/libspa-audioconvert"
  * media.class = "Audio/Sink"
    media.name = "Shure 50"
  * node.description = "Shure 50"
    node.driver = "true"
  * node.name = "bluez_output.00_0E_DD_0C_47_E5.1"
    node.pause-on-idle = "false"
  * object.serial = "2305"
  * priority.driver = "1010"
  * priority.session = "1010"

pwvucontrol Cards page: 20240602_19h00m48s_grim

saivert commented 4 months ago

Is this still an issue if you try version 0.4.1 or a build from main branch?

poperigby commented 4 months ago

I just realized I reported the wrong version of pwvucontrol. I am actually using 0.4.1, and the GUI was giving the wrong version for some reason.

It does seem to be fixed on the main branch though.