(I hate saying this, but) I’m on arch, and using pretty up-to-date versions of pulse and wireplumber, but no dice. I’ve tried the LTS kernel, still no dice. I think it’s a regression that has somehow largely gone unnoticed, because I cannot find any bug reports about it, despite the headphones being quite popular
That could be a combination of something only you have or really just a bug unreported. I would recommend trying to open a bug report and maybe more people can chime in and help.
I’ve personally had a bunch of regressions and problems with some versions, but it’s been fixed for my specific devices. Got 2 codecs for input/mic I can choose and the others for sound output including ldac working nicely.
It’s hard to make a bug report, since I can’t find the specific version that caused the regression, and it’s hard to downgrade that single package to do a binary search to find the regression without altering all the system packages. It’s a kind of “damned-if-you-do” catch-11 situation
(I hate saying this, but) I’m on arch, and using pretty up-to-date versions of pulse and wireplumber, but no dice. I’ve tried the LTS kernel, still no dice. I think it’s a regression that has somehow largely gone unnoticed, because I cannot find any bug reports about it, despite the headphones being quite popular
That could be a combination of something only you have or really just a bug unreported. I would recommend trying to open a bug report and maybe more people can chime in and help.
I’ve personally had a bunch of regressions and problems with some versions, but it’s been fixed for my specific devices. Got 2 codecs for input/mic I can choose and the others for sound output including ldac working nicely.
It’s hard to make a bug report, since I can’t find the specific version that caused the regression, and it’s hard to downgrade that single package to do a binary search to find the regression without altering all the system packages. It’s a kind of “damned-if-you-do” catch-11 situation