Date: Mon, 16 Nov 2015 08:38:49 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 203745] A2DP Support for Bluetooth Headphone Audio Message-ID: <bug-203745-21060-Vml90Hzm5o@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-203745-21060@https.bugs.freebsd.org/bugzilla/> References: <bug-203745-21060@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203745 --- Comment #23 from Hans Petter Selasky <hselasky@FreeBSD.org> --- Forwarding message from Nathanial Sloss: > AFAICT the only reason as to why auto config would fail would be if the max > bitpool value that is calculated is smaller than the minimum bit pool value. > > This is possibile on some headphones/speakers bta2dpd has the -B switch so the > user can set the max bitpool value. Is there hci dump on freebsd as seeing > the output of getConfiguration will confirm this. Otherwize increasing > DEFAULT_MAXBITPOOL from 80 to say 160 in sbc_encode.h might work for his > headphones but I am at a loss as to whether this will effect others. The > problem stems from the fact that different manufacturers specify different > encoding ranges and I've made it use the highest possible value as this will > give the best quality but in some cases the headphones will report a bitpool > range of 2-253 but if you encode the audio at 253 you wont get any playback > and most android/linux will just use 36 and this wont work with some > headphones or sound bad. Tony: Could you try to change the definition of DEFAULT_MAXBITPOOL? --HPS -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-203745-21060-Vml90Hzm5o>