[pulseaudio-discuss] speech synthesizers and Pulseaudio

2019-10-07 Thread Mgr. Janusz Chmiel
Dear users and Pulseaudio sound server developers, I have worked with Linux from The time, when Ubuntu 7.04 has been released. In this times, Gnome have contained Pulseaudio sound server. I have started to be sad, that this excellent sound server, which has so many qualities, had issues with

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

2019-10-07 Thread Hyperion
I'm not talking about old Bluez versions : only about the current stable 5.51, and not talking about codec switchin either. Just talking about improvement of MAX negociated values for SBC. Please take a look at my latest patch. 07.10.2019, 16:22, "Pali Rohár" : > Old bluez versions have bugs

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

2019-10-07 Thread Pali Rohár
Old bluez versions have bugs and different behavior. So not break anything else and still have working audio playback, it is better to not touch it and use what is currently supported / provided. New features like additional codec support, codec switching, etc... needs new bluez API and new

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

2019-10-07 Thread Hyperion
I disagree with "Also there would not be any feature/functional changes in pulseaudio when older bluez version is in use". Tests prove that there's no reason for this, if only one mode/profile is used. JP 07.10.2019, 15:36, "Pali Rohár" : > I will try to look what is the problem without

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

2019-10-07 Thread Pali Rohár
I will try to look what is the problem without --experimental. This should work correctly prior merging this PR. Need to --experimental is just temporary until support in bluez is not fully stable. I guess it would be non-experimental in next bluez version. Also there would not be any

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

2019-10-07 Thread Hyperion
Without the --experimental flag : negociation stops (see hcidump below) and device falls back to "Off" status. btw : if you implement my (simple) negociation algorithm for the "Automatic Quality" mode ; AND make it to work without --experimental Bluez flag : it woiuld be close to perfect. See

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

2019-10-07 Thread Pali Rohár
And what happened without --experimental? Aim is to support all bluez versions also with and without --experimental flag. Just for older versions (or without experimental) it should behave like before this patch series -- only SBC codec in automatic mode and no codec switching. On Monday 07

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

2019-10-07 Thread Hyperion
Thanks, I forgot the "--experimental" param. Works as expected, like the previous v12 serie of patches JP 07.10.2019, 15:15, "Pali Rohár" : > Can you check if you have Bluez 5.51 and bluetoothd daemon is running with > --experimental param? > > And is not it possible to change profile from Off

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

2019-10-07 Thread Pali Rohár
Can you check if you have Bluez 5.51 and bluetoothd daemon is running with --experimental param? And is not it possible to change profile from Off to Automatic Quality? On Monday 07 October 2019 15:08:59 Hyperion wrote: > The 10 patches compile OK on PA master without warnings. > > But doesn't

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

2019-10-07 Thread Hyperion
The 10 patches compile OK on PA master without warnings. But doesn't work (device is Off with "Automatic Quality unavailable" status). Tested on 2 devices. hcidump avdtp HCI sniffer - Bluetooth packet analyzer ver 5.51 device: hci0 snap_len: 1500 filter: 0x400 < AVDTP(s): Discover cmd:

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

2019-10-07 Thread Hyperion
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" :If you mean EP0398973B1 then it is already expired. I'm not aware ofother patents covering aptX. So I think libopenaptx should be safe here.But I'm not lawyer and do not understand

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

2019-10-07 Thread Pali Rohár
If you mean EP0398973B1 then it is already expired. I'm not aware of other patents covering aptX. So I think libopenaptx should be safe here. But I'm not lawyer and do not understand jurisdiction across whole world, but I guess it is same problem as with expired patents for MP3. Why should be

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

2019-10-07 Thread Pasi Kärkkäinen
On Mon, Oct 07, 2019 at 10:11:39AM +0200, Hyperion wrote: > both libraries are comming from the same reverse-engineering of a PROPRIETARY > PATENTED codec, and BOTH are subject to lawsuit in case it is widely > distributed as binary. > Afaik AptX patents expired already. That's why AptX codecs

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

2019-10-07 Thread Hyperion
both libraries are comming from the same reverse-engineering of a PROPRIETARY PATENTED codec, and BOTH are subject to lawsuit in case it is widely distributed as binary. JP 07.10.2019, 10:06, "Pali Rohár" : > But that is something different. Look at commit message where is link to > correct

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

2019-10-07 Thread Hyperion
Sorry, I should have provided the link to the source GIT https://github.com/Arkq/openaptx JP 07.10.2019, 09:51, "Pali Rohár" : > On Monday 07 October 2019 09:47:21 Hyperion wrote: >>  Quotig OpenAPTX Github README : >>  "This project is for research purposes only. Without a proper license >>

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

2019-10-07 Thread Pali Rohár
But that is something different. Look at commit message where is link to correct library for building. On Monday 07 October 2019 10:05:52 Hyperion wrote: > Sorry, I should have provided the link to the source GIT > https://github.com/Arkq/openaptx > > JP > > > 07.10.2019, 09:51, "Pali Rohár"

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

2019-10-07 Thread Hyperion
Hi Pali, I believe that the average user SHOULD be provided a high quality sound by default. And legacy low quality bitrates SHOULD be a workaround. IMHO, an "AUTOMATIC mode with max XQ bitrates and DUAL CHANNEL mode prefered" (aka : max negociated bitpool = 38 per channel) : SHOULD be the

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

2019-10-07 Thread Pali Rohár
On Monday 07 October 2019 09:47:21 Hyperion wrote: > Quotig OpenAPTX Github README : > "This project is for research purposes only. Without a proper license private > and commercial usage might be a case of a patent infringement. If you are > looking for a library, which can be installed and

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

2019-10-07 Thread Hyperion
Quotig OpenAPTX Github README : "This project is for research purposes only. Without a proper license private and commercial usage might be a case of a patent infringement. If you are looking for a library, which can be installed and used legally (commercial, private and educational usage), go