borine
borine
I've just force-pushed a re-factored version which will be easier to add into the bluealsa pcm plugin, should that be desired, and hopefully is also more robust
> ALSA blocks for too long while executing snd_pcm_writei() That is because the clock used by the ALSA sink is the playback device clock (ie the soundcard clock), whereas the...
> Silent modification of command line arguments is not OK Yes, that makes sense. These "properties" are a mix of "configuration" (invariant, build-time or command-line selections) and "state" (variable runtime...
I've raised a new PR with just Version and Adapters. I've left this original branch here for reference - if you would like me to rework any of the properties...
I suspect this is an issue with the Bluez cache. I've seen similar issues when I changed the codec(s) used by `bluealsa` **after** I've already paired the headphones. This *may*...
I believe Bluez has now fixed this bug in bluez release 5.65
For AAC BlueALSA requires the Fraunhofer fdk-aac library, it does not work with libfaac. RaspberryPiOS does not include a pre-built version of libfdk-aac in its repository, so you will have...
``` git clone https://github.com/mstorsjo/fdk-aac.git cd fdk-aac ./autogen.sh ./configure make -j4 sudo make install ```
ALSA uses only 1 definition for a given pcm name, the **last** one it sees when parsing the config. So in your case the pcm "default" has the `bluealsa` definition,...
could this possibly be a shairport issue? see for example https://github.com/mikebrady/shairport-sync/issues/1179