A2DP on PulseAudio - terrible choppy/skipping audio
I have paired my Bluetooth headset with my Ubuntu 12.04 laptop with a Bluetooth chip inside:
lsusb | grep Bluetooth
Bus 003 Device 003: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
The device has been paired, and with the help of blueman, I've connected it to PulseAudio as a sink. Audio does come across in A2DP mode, but is terribly choppy and skips to the point of being not much better than nothing.
I read around and saw that there was a fix involving adjusting the nice priority of the PulseAudio server. Since by default, PulseAudio runs on a per-user basis, I added the following to my /etc/security/limits.conf:
* hard rtpio 0
* soft rtpio 0
@audio hard rtpio 20
@audio soft rtpio 20
pulse hard rtpio 20
pulse soft rtpio 20
I then added myself to the audio group to be able to schedule priority for the pulseaudio process. It seems that pulseaudio is now running with a priority of -11:
ps -eo pri,ni,cmd | grep [p]ulse
30 -11 /usr/bin/pulseaudio --start --log-target=syslog
This should mean that PulseAudio is running with a priority of -11, which is good.
However, even after restarting, I still get the terrible choppy audio.
How should I proceed? I'm trying to make this Bluetooth headset I purchased usable.
Note: I've tried pairing this device with an Android tablet right next to my laptop and it works fine, so it's not wireless congestion, it seems to be directly correlated to Linux somehow.
sound pulseaudio bluetooth realtime
asked Jun 3 '14 at 0:21
Naftuli KayNaftuli Kay
1,39842441
add a comment |
I have paired my Bluetooth headset with my Ubuntu 12.04 laptop with a Bluetooth chip inside:
lsusb | grep Bluetooth
Bus 003 Device 003: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
The device has been paired, and with the help of blueman, I've connected it to PulseAudio as a sink. Audio does come across in A2DP mode, but is terribly choppy and skips to the point of being not much better than nothing.
I read around and saw that there was a fix involving adjusting the nice priority of the PulseAudio server. Since by default, PulseAudio runs on a per-user basis, I added the following to my /etc/security/limits.conf:
* hard rtpio 0
* soft rtpio 0
@audio hard rtpio 20
@audio soft rtpio 20
pulse hard rtpio 20
pulse soft rtpio 20
I then added myself to the audio group to be able to schedule priority for the pulseaudio process. It seems that pulseaudio is now running with a priority of -11:
ps -eo pri,ni,cmd | grep [p]ulse
30 -11 /usr/bin/pulseaudio --start --log-target=syslog
This should mean that PulseAudio is running with a priority of -11, which is good.
However, even after restarting, I still get the terrible choppy audio.
How should I proceed? I'm trying to make this Bluetooth headset I purchased usable.
Note: I've tried pairing this device with an Android tablet right next to my laptop and it works fine, so it's not wireless congestion, it seems to be directly correlated to Linux somehow.
sound pulseaudio bluetooth realtime
asked Jun 3 '14 at 0:21
Naftuli KayNaftuli Kay
1,39842441
add a comment |
I have paired my Bluetooth headset with my Ubuntu 12.04 laptop with a Bluetooth chip inside:
lsusb | grep Bluetooth
Bus 003 Device 003: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
The device has been paired, and with the help of blueman, I've connected it to PulseAudio as a sink. Audio does come across in A2DP mode, but is terribly choppy and skips to the point of being not much better than nothing.
I read around and saw that there was a fix involving adjusting the nice priority of the PulseAudio server. Since by default, PulseAudio runs on a per-user basis, I added the following to my /etc/security/limits.conf:
* hard rtpio 0
* soft rtpio 0
@audio hard rtpio 20
@audio soft rtpio 20
pulse hard rtpio 20
pulse soft rtpio 20
I then added myself to the audio group to be able to schedule priority for the pulseaudio process. It seems that pulseaudio is now running with a priority of -11:
ps -eo pri,ni,cmd | grep [p]ulse
30 -11 /usr/bin/pulseaudio --start --log-target=syslog
This should mean that PulseAudio is running with a priority of -11, which is good.
However, even after restarting, I still get the terrible choppy audio.
How should I proceed? I'm trying to make this Bluetooth headset I purchased usable.
Note: I've tried pairing this device with an Android tablet right next to my laptop and it works fine, so it's not wireless congestion, it seems to be directly correlated to Linux somehow.
sound pulseaudio bluetooth realtime
asked Jun 3 '14 at 0:21
Naftuli KayNaftuli Kay
1,39842441
I have paired my Bluetooth headset with my Ubuntu 12.04 laptop with a Bluetooth chip inside:
lsusb | grep Bluetooth
Bus 003 Device 003: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
The device has been paired, and with the help of blueman, I've connected it to PulseAudio as a sink. Audio does come across in A2DP mode, but is terribly choppy and skips to the point of being not much better than nothing.
I read around and saw that there was a fix involving adjusting the nice priority of the PulseAudio server. Since by default, PulseAudio runs on a per-user basis, I added the following to my /etc/security/limits.conf:
* hard rtpio 0
* soft rtpio 0
@audio hard rtpio 20
@audio soft rtpio 20
pulse hard rtpio 20
pulse soft rtpio 20
I then added myself to the audio group to be able to schedule priority for the pulseaudio process. It seems that pulseaudio is now running with a priority of -11:
ps -eo pri,ni,cmd | grep [p]ulse
30 -11 /usr/bin/pulseaudio --start --log-target=syslog
This should mean that PulseAudio is running with a priority of -11, which is good.
However, even after restarting, I still get the terrible choppy audio.
How should I proceed? I'm trying to make this Bluetooth headset I purchased usable.
Note: I've tried pairing this device with an Android tablet right next to my laptop and it works fine, so it's not wireless congestion, it seems to be directly correlated to Linux somehow.
sound pulseaudio bluetooth realtime
sound pulseaudio bluetooth realtime
asked Jun 3 '14 at 0:21
Naftuli KayNaftuli Kay
1,39842441
asked Jun 3 '14 at 0:21
Naftuli KayNaftuli Kay
1,39842441
asked Jun 3 '14 at 0:21
Naftuli KayNaftuli Kay
1,39842441
asked Jun 3 '14 at 0:21
Naftuli KayNaftuli Kay
1,39842441
asked Jun 3 '14 at 0:21
Naftuli KayNaftuli Kay
1,39842441
1,39842441
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Edit the ALSA configuration file
sudo gedit /etc/modprobe.d/alsa-base.conf
Add the line
options snd-hda-intel model=generic
to the end of the file, and reboot.
answered Mar 7 '15 at 14:58
ConfirmAndCreateThisAccountConfirmAndCreateThisAccount
8112
This worked wonderfully for my BOSE quiet comfort 35 II speakers (ubuntu 18.04)
– Victor Parmar
Jun 26 '18 at 12:39
This simple fix also worked for me after a lot of searching. Ubuntu 18.10, bluetooth earphones (promate trueBlue).
– Francesco Napolitano
Nov 20 '18 at 14:15
Created an account to mention that this solved my problems too (QC35II). An explanation would be helpful; but either way, you are a life saver
– Sam
Jan 3 at 10:34
I see about 95% less choppiness with this fix with QC35II on Debian 9 testing, kernel 4.18.20-2.
– Andrey Portnoy
Jan 5 at 7:52
Although there's this Canonical article that advises against doing this: In particular, avoid model=generic – that is almost guaranteed to give you trouble. In many cases, when trying different models, you will find that you might fix one thing but break another. voices.canonical.com/david.henningsson/2012/07/13/…
– Andrey Portnoy
Jan 5 at 7:57
|
show 2 more comments
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f475987%2fa2dp-on-pulseaudio-terrible-choppy-skipping-audio%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Edit the ALSA configuration file
sudo gedit /etc/modprobe.d/alsa-base.conf
Add the line
options snd-hda-intel model=generic
to the end of the file, and reboot.
answered Mar 7 '15 at 14:58
ConfirmAndCreateThisAccountConfirmAndCreateThisAccount
8112
This worked wonderfully for my BOSE quiet comfort 35 II speakers (ubuntu 18.04)
– Victor Parmar
Jun 26 '18 at 12:39
This simple fix also worked for me after a lot of searching. Ubuntu 18.10, bluetooth earphones (promate trueBlue).
– Francesco Napolitano
Nov 20 '18 at 14:15
Created an account to mention that this solved my problems too (QC35II). An explanation would be helpful; but either way, you are a life saver
– Sam
Jan 3 at 10:34
I see about 95% less choppiness with this fix with QC35II on Debian 9 testing, kernel 4.18.20-2.
– Andrey Portnoy
Jan 5 at 7:52
Although there's this Canonical article that advises against doing this: In particular, avoid model=generic – that is almost guaranteed to give you trouble. In many cases, when trying different models, you will find that you might fix one thing but break another. voices.canonical.com/david.henningsson/2012/07/13/…
– Andrey Portnoy
Jan 5 at 7:57
|
show 2 more comments
Edit the ALSA configuration file
sudo gedit /etc/modprobe.d/alsa-base.conf
Add the line
options snd-hda-intel model=generic
to the end of the file, and reboot.
answered Mar 7 '15 at 14:58
ConfirmAndCreateThisAccountConfirmAndCreateThisAccount
8112
This worked wonderfully for my BOSE quiet comfort 35 II speakers (ubuntu 18.04)
– Victor Parmar
Jun 26 '18 at 12:39
This simple fix also worked for me after a lot of searching. Ubuntu 18.10, bluetooth earphones (promate trueBlue).
– Francesco Napolitano
Nov 20 '18 at 14:15
Created an account to mention that this solved my problems too (QC35II). An explanation would be helpful; but either way, you are a life saver
– Sam
Jan 3 at 10:34
I see about 95% less choppiness with this fix with QC35II on Debian 9 testing, kernel 4.18.20-2.
– Andrey Portnoy
Jan 5 at 7:52
Although there's this Canonical article that advises against doing this: In particular, avoid model=generic – that is almost guaranteed to give you trouble. In many cases, when trying different models, you will find that you might fix one thing but break another. voices.canonical.com/david.henningsson/2012/07/13/…
– Andrey Portnoy
Jan 5 at 7:57
|
show 2 more comments
Edit the ALSA configuration file
sudo gedit /etc/modprobe.d/alsa-base.conf
Add the line
options snd-hda-intel model=generic
to the end of the file, and reboot.
answered Mar 7 '15 at 14:58
ConfirmAndCreateThisAccountConfirmAndCreateThisAccount
8112
Edit the ALSA configuration file
sudo gedit /etc/modprobe.d/alsa-base.conf
Add the line
options snd-hda-intel model=generic
to the end of the file, and reboot.
answered Mar 7 '15 at 14:58
ConfirmAndCreateThisAccountConfirmAndCreateThisAccount
8112
answered Mar 7 '15 at 14:58
ConfirmAndCreateThisAccountConfirmAndCreateThisAccount
8112
answered Mar 7 '15 at 14:58
ConfirmAndCreateThisAccountConfirmAndCreateThisAccount
8112
answered Mar 7 '15 at 14:58
ConfirmAndCreateThisAccountConfirmAndCreateThisAccount
8112
8112
This worked wonderfully for my BOSE quiet comfort 35 II speakers (ubuntu 18.04)
– Victor Parmar
Jun 26 '18 at 12:39
This simple fix also worked for me after a lot of searching. Ubuntu 18.10, bluetooth earphones (promate trueBlue).
– Francesco Napolitano
Nov 20 '18 at 14:15
Created an account to mention that this solved my problems too (QC35II). An explanation would be helpful; but either way, you are a life saver
– Sam
Jan 3 at 10:34
I see about 95% less choppiness with this fix with QC35II on Debian 9 testing, kernel 4.18.20-2.
– Andrey Portnoy
Jan 5 at 7:52
Although there's this Canonical article that advises against doing this: In particular, avoid model=generic – that is almost guaranteed to give you trouble. In many cases, when trying different models, you will find that you might fix one thing but break another. voices.canonical.com/david.henningsson/2012/07/13/…
– Andrey Portnoy
Jan 5 at 7:57
|
show 2 more comments
This worked wonderfully for my BOSE quiet comfort 35 II speakers (ubuntu 18.04)
– Victor Parmar
Jun 26 '18 at 12:39
This simple fix also worked for me after a lot of searching. Ubuntu 18.10, bluetooth earphones (promate trueBlue).
– Francesco Napolitano
Nov 20 '18 at 14:15
Created an account to mention that this solved my problems too (QC35II). An explanation would be helpful; but either way, you are a life saver
– Sam
Jan 3 at 10:34
I see about 95% less choppiness with this fix with QC35II on Debian 9 testing, kernel 4.18.20-2.
– Andrey Portnoy
Jan 5 at 7:52
Although there's this Canonical article that advises against doing this: In particular, avoid model=generic – that is almost guaranteed to give you trouble. In many cases, when trying different models, you will find that you might fix one thing but break another. voices.canonical.com/david.henningsson/2012/07/13/…
– Andrey Portnoy
Jan 5 at 7:57
This worked wonderfully for my BOSE quiet comfort 35 II speakers (ubuntu 18.04)
– Victor Parmar
Jun 26 '18 at 12:39
This worked wonderfully for my BOSE quiet comfort 35 II speakers (ubuntu 18.04)
– Victor Parmar
Jun 26 '18 at 12:39
This simple fix also worked for me after a lot of searching. Ubuntu 18.10, bluetooth earphones (promate trueBlue).
– Francesco Napolitano
Nov 20 '18 at 14:15
This simple fix also worked for me after a lot of searching. Ubuntu 18.10, bluetooth earphones (promate trueBlue).
– Francesco Napolitano
Nov 20 '18 at 14:15
Created an account to mention that this solved my problems too (QC35II). An explanation would be helpful; but either way, you are a life saver
– Sam
Jan 3 at 10:34
Created an account to mention that this solved my problems too (QC35II). An explanation would be helpful; but either way, you are a life saver
– Sam
Jan 3 at 10:34
I see about 95% less choppiness with this fix with QC35II on Debian 9 testing, kernel 4.18.20-2.
– Andrey Portnoy
Jan 5 at 7:52
I see about 95% less choppiness with this fix with QC35II on Debian 9 testing, kernel 4.18.20-2.
– Andrey Portnoy
Jan 5 at 7:52
Although there's this Canonical article that advises against doing this: In particular, avoid model=generic – that is almost guaranteed to give you trouble. In many cases, when trying different models, you will find that you might fix one thing but break another. voices.canonical.com/david.henningsson/2012/07/13/…
– Andrey Portnoy
Jan 5 at 7:57
Although there's this Canonical article that advises against doing this: In particular, avoid model=generic – that is almost guaranteed to give you trouble. In many cases, when trying different models, you will find that you might fix one thing but break another. voices.canonical.com/david.henningsson/2012/07/13/…
– Andrey Portnoy
Jan 5 at 7:57
|
show 2 more comments
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f475987%2fa2dp-on-pulseaudio-terrible-choppy-skipping-audio%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
