Doesn't work for me with Intel 7260 Bluetooth 4.0 and RealForce OverDrive D1.
When I connect headphones and change Pulseaudio profile from "Off" to "High
Fidelity SBC playback (a2dp sink)", everything works as expected with SBC.
Profile does not switch if I choose "High Fidelity aptX playback
I applied the patch to stable Pulseaudio 12.2. The patch successfully applies
with some fuzzing. Should it be compatible with 12.2 or should I check it with
master?
On 03.08.2018 16:22, ValdikSS wrote:
> Doesn't work for me with Intel 7260 Bluetooth 4.0 and RealForce OverDrive D1.
>
&g
On 03.08.2018 16:32, Pali Rohár wrote:
> On Friday 03 August 2018 16:22:05 ValdikSS wrote:
>> Doesn't work for me with Intel 7260 Bluetooth 4.0 and RealForce OverDrive D1.
>>
>> When I connect headphones and change Pulseaudio profile from "Off" to "High
On 22.07.2018 14:37, Pali Rohár wrote:
>
> Information which I have about FastStream: It is just SBC codec with
> following parameters: frequency rate 44.1 kHz or 48.0 kHz, Blocks 16,
> Sub-bands 8, Joint Stereo, Loudness and Bitpool = 29. So data rate = 212
> kbps, packet size = 72*3+4 = 220 =
On 30.07.2018 10:30, Pali Rohár wrote:
> On Monday 30 July 2018 10:24:10 ValdikSS wrote:
>>> ACL Data RX: Handle 256 flags 0x02 dlen 20 #109 [hci0]
>>> 5.421906
>> Channel: 66 len 16 [PSM 25 mode 0] {chan 2}
>> AVDTP: Get Capabilities (
On 30.07.2018 10:17, Pali Rohár wrote:
> On Monday 30 July 2018 06:30:14 valdikss wrote:
>> On 22.07.2018 14:37, Pali Rohár wrote:
>>
>>> Information which I have about FastStream: It is just SBC codec with
>>> following parameters: frequency rate 44.1 kHz or 48.
On 10.08.2018 13:31, ValdikSS wrote:
> On 10.08.2018 10:57, Pali Rohár wrote:
>> On Thursday 09 August 2018 16:39:09 ValdikSS wrote:
>>> On 06.07.2018 13:25, Pali Rohár wrote:
>>>> I did some investigation and basically this is the list of all known
>>>>
On 06.07.2018 13:25, Pali Rohár wrote:
> I did some investigation and basically this is the list of all known
> codecs used in A2DP:
>
> Mandatory:
> 0x00 - SBC
>
> Optional:
> 0x01 - MPEG-1,2 (aka MP3)
> 0x02 - MPEG-2,4 (aka AAC)
> 0x04 - ATRAC
>
> Vendor specific:
> 0xFF 0x004F 0x01 - aptX
>
On 09.08.2018 16:39, ValdikSS wrote:
> On 06.07.2018 13:25, Pali Rohár wrote:
>> I did some investigation and basically this is the list of all known
>> codecs used in A2DP:
>>
>> Mandatory:
>> 0x00 - SBC
>>
>> Optional:
>> 0x01 - MPEG-1,2 (ak
On 10.08.2018 10:57, Pali Rohár wrote:
> On Thursday 09 August 2018 16:39:09 ValdikSS wrote:
>> On 06.07.2018 13:25, Pali Rohár wrote:
>>> I did some investigation and basically this is the list of all known
>>> codecs used in A2DP:
>>>
>>> Mandato
On 09.08.2018 16:39, ValdikSS wrote:
> On 06.07.2018 13:25, Pali Rohár wrote:
>> I did some investigation and basically this is the list of all known
>> codecs used in A2DP:
>>
>> Mandatory:
>> 0x00 - SBC
>>
>> Optional:
>> 0x01 - MPEG-1,2 (ak
Can you please integrate exceptions from the Android database?
https://android.googlesource.com/platform/system/bt/+/master/device/include/interop_database.h
Ones with INTEROP_DISABLE_ABSOLUTE_VOLUME
On 03/10/2018 16:12, EHfive wrote:
> On 10/3/18 8:37 PM, EHfive wrote:
>> Require
for broken devices for Android, which I have linked.
Please add these exceptions if possible.
On 14.10.2018 21:54, ValdikSS wrote:
> Can you please integrate exceptions from the Android database?
> https://android.googlesource.com/platform/system/bt/+/master/device/include/interop_database.h
On 10.08.2018 20:35, ValdikSS wrote:
>
> On 10.08.2018 13:31, ValdikSS wrote:
>> On 10.08.2018 10:57, Pali Rohár wrote:
>>> On Thursday 09 August 2018 16:39:09 ValdikSS wrote:
>>>> On 06.07.2018 13:25, Pali Rohár wrote:
>>>>> I did some investiga
I can't find any information regarding CSR True Wireless Stereo v3. What's
that? Can you share documentation where you got information about these IDs?
On 19.12.2018 20:59, Pali Rohár wrote:
> On Thursday 09 August 2018 16:39:09 ValdikSS wrote:
>> 0xFF 0x000A 0x0103 — Unknown codec foun
Are you sure the problem is in Pulseaudio or Bluez? From my tests, some
Bluetooth devices (especially receivers) have audio post-processing pipeline
and mute the output if audio signal is too low.
Try to play a very quiet sound (set PA volume to the minimum and use softvolume
in your audio
On 14/09/2018 16:42, Luiz Augusto von Dentz wrote:
>> I propose to use 76 bitpool as a default maximum (454.8 kbps for Joint
>> Stereo, 44.1 kHz, 8 subbands, 16 blocks). This bitpool is optimal for both
>> EDR 2 mbit/s and EDR 3 mbit/s modes, since it packs audio frames with least
>> wasted
On 12/09/2018 13:42, Pali Rohár wrote:
> Hello!
>
> I would like to let you know that Serge from soundexpert.org did in last
> month some research on aptX and its quality. Detailed article is on the
> following website, specially see parts added around "August 2018":
>
>
On 12/09/2018 19:03, Luiz Augusto von Dentz wrote:
>> 2) Should we rather look at increasing quality of SBC codec in
>> pulseaudio? And if yes, how should be quality of SBC configured? Via
>> profiles? Or to invent some new protocol options? Can we increase
>> default SBC bitpool allocation?
>
>
On 13/09/2018 11:23, Tanu Kaskinen wrote:
>
> How is the bitrate calculated? I'd like to write a section on the
> Bluetooth wiki page[1] that explains the SBC codec with a table showing
> how the different parameters affect the bitrate.
>
> [1]
>
On 02.06.2019 18:25, Pali Rohár wrote:
> Specify configuration for Low, Middle, High and Ultra High Quality of SBC
> codec. SBC codec in Ultra High Quality has higher quality than aptX.
>
> Automatic Quality mode matches configuration of SBC codec which was used
> before this change. Which means
On 10.06.2019 17:53, Pali Rohár wrote:
> On Wednesday 05 June 2019 22:42:49 ValdikSS wrote:
>> On 02.06.2019 18:25, Pali Rohár wrote:
>>> Specify configuration for Low, Middle, High and Ultra High Quality of SBC
>>> codec. SBC codec in Ultra High Quality h
On 10.06.2019 23:20, Pali Rohár wrote:
> On Monday 10 June 2019 20:37:43 ValdikSS wrote:
>> On 10.06.2019 17:53, Pali Rohár wrote:
>>> On Wednesday 05 June 2019 22:42:49 ValdikSS wrote:
>>>> On 02.06.2019 18:25, Pali Rohár wrote:
>>>>> Specify confi
23 matches
Mail list logo
