35
10Dev
4y

What I was supposed to do today:

Finish up some homework and code for a bit

What I actually did today:

1. Boot up my laptop to get started on homework

2. Open Spotify and try to connect my headphones

3. Reinstall Bluetooth and pulseaudio to connect to headphones

4. Connected! But the sound quality is shit

5. Spend an hour or so learning about codec sinks and how Bluetooth is the definition of an overengineered clusterfuck

6. Install some package from the aur to get AAC codec support

7. Now we have high fidelity audio, but the headphones still connect to the crappy SBC sink, so I spend another 45 minutes writing a shell script to automatically switch to the AAC sink when a Bluetooth headset connects

8. It’s finally working! But now I have no motivation to do my actual work. Fml

Comments
  • 1
    Same with me:
    "Distraction"
  • 0
    First step of coding cleared with flying colours.
  • 0
    @theKarlisK Jabra 75t. And holy fuck I'm an idiot, I didn't even think of that
  • 3
    Could have just used good non Bluetooth over ear Headphones that actually sound good
  • 2
    Classic Procrastination
  • 0
    We now have PipeWire, it's Pulse but faster combined with Jack and exposes both APIs.
    Also you can either set the codec in the bluez config file which will set it for all devices and might bite you when you want to connect a different speaker, or you can create an explicit ALSA sink for the device and set the codec there, which may make things like automatically switching the default output more complicated since pulse won't recognize that bluez owns your custom sink.
  • 0
    Linux problems.

    Windows :

    Add device => headphones. Working. Now go to your homework
  • 1
    @NoToJavaScript And when it isn't like that and Windows fails to interface with a peripheral (which is actually quite common in my experience) you suck it up and learn to live with bad quality service, instability or outright incompatibility.
Add Comment