Re: [pulseaudio-discuss] [PATCH v13 10/10] bluetooth: policy: Treat bi-directional A2DP profiles as suitable for VOIP

2019-10-08 Thread Hyperion
I disagree. As an engineer you should know that an implementation should not be based on broken devices , but rarher on good standard specifications. Rare broken devices, and rare very old devices that don't follow A2DP specifications shouldn't be the main design target for Pulseaudio.Jp18:29, 8

Re: [pulseaudio-discuss] [PATCH v13 05/10] bluetooth: Add A2DP aptX and aptX HD codecs support

2019-10-08 Thread Pali Rohár
On Monday 07 October 2019 10:32:10 Hyperion wrote: > Not sure it's expired worlwide. In case it is, it's good news. Fine for > me.10:28, 7 octobre 2019, "Pali Rohár" > pali.ro...@gmail.com: class="b4fd5cf2ec92bc68cb898700bb81355fwmi-quote">If you mean EP

Re: [pulseaudio-discuss] [PATCH v13 07/10] bluetooth: Add more variants of SBC codec

2019-10-08 Thread Pali Rohár
Explained in other email. We cannot change Automatic SBC profile to not break some existing devices (with broken A2DP implementation). One of the main objections against SBC codec is that user does not "what version of SBC quality is in use" and therefore other proprietary codecs with fixed

Re: [pulseaudio-discuss] [PATCH v13 10/10] bluetooth: policy: Treat bi-directional A2DP profiles as suitable for VOIP

2019-10-08 Thread Pali Rohár
Automatic SBC profile is not going to be changed. It is there to support all devices without any tweaks. ValdikSS already did more tests and there are devices which do not work with higher SBC bitpool. So increasing max value of bitpool in Automatic SBC profile would lead to broken support for