JACK, PulseAudio and Firefox: Enable JACK for firefox in the near future
Firefox bug #1345661 was closed with "WONTFIX", which certainly will break my current setup in the near future (I play firefox sound through alsa_in:loopback->JACK). I have read that Firefox has JACK support now, though it is not yet stable. Questions:
- Will JACK support in Firefox be officially supported?
- Will Ubuntu enable JACK support in Firefox before raw ALSA support ends?
I the answer is No No, how can I reliable restore functionality without breaking JACK? It is possible to run PA through alsa_in, but I guess that would introduce some extra latency, break AV sync, or introduce signal distortion due to multiple resamplers.
firefox pulseaudio alsa jack
asked Jun 10 '17 at 8:15
user877329user877329
1251421
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
Firefox bug #1345661 was closed with "WONTFIX", which certainly will break my current setup in the near future (I play firefox sound through alsa_in:loopback->JACK). I have read that Firefox has JACK support now, though it is not yet stable. Questions:
- Will JACK support in Firefox be officially supported?
- Will Ubuntu enable JACK support in Firefox before raw ALSA support ends?
I the answer is No No, how can I reliable restore functionality without breaking JACK? It is possible to run PA through alsa_in, but I guess that would introduce some extra latency, break AV sync, or introduce signal distortion due to multiple resamplers.
firefox pulseaudio alsa jack
asked Jun 10 '17 at 8:15
user877329user877329
1251421
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
Firefox bug #1345661 was closed with "WONTFIX", which certainly will break my current setup in the near future (I play firefox sound through alsa_in:loopback->JACK). I have read that Firefox has JACK support now, though it is not yet stable. Questions:
- Will JACK support in Firefox be officially supported?
- Will Ubuntu enable JACK support in Firefox before raw ALSA support ends?
I the answer is No No, how can I reliable restore functionality without breaking JACK? It is possible to run PA through alsa_in, but I guess that would introduce some extra latency, break AV sync, or introduce signal distortion due to multiple resamplers.
firefox pulseaudio alsa jack
asked Jun 10 '17 at 8:15
user877329user877329
1251421
Firefox bug #1345661 was closed with "WONTFIX", which certainly will break my current setup in the near future (I play firefox sound through alsa_in:loopback->JACK). I have read that Firefox has JACK support now, though it is not yet stable. Questions:
- Will JACK support in Firefox be officially supported?
- Will Ubuntu enable JACK support in Firefox before raw ALSA support ends?
I the answer is No No, how can I reliable restore functionality without breaking JACK? It is possible to run PA through alsa_in, but I guess that would introduce some extra latency, break AV sync, or introduce signal distortion due to multiple resamplers.
firefox pulseaudio alsa jack
firefox pulseaudio alsa jack
asked Jun 10 '17 at 8:15
user877329user877329
1251421
asked Jun 10 '17 at 8:15
user877329user877329
1251421
asked Jun 10 '17 at 8:15
user877329user877329
1251421
asked Jun 10 '17 at 8:15
user877329user877329
1251421
asked Jun 10 '17 at 8:15
user877329user877329
1251421
1251421
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I've compiled mozilla-central firefox with jack support and output (sources) Automatically get created when you visit a site with audio (i.e youtube).
However - input sink sources do not get created ; I don't see them appear in cadence/jack patch bay. So anything that relies on Mic input fails. i.e meet.jit.si / webrtc tests...
Another problem is that even using the pulseaudio bridge ; the same issue input sources even when connected correctly to the pulse-sink don't get recognized by firefox. In Chrome however Mic input correctly uses the plugged capture to pulse-sink. So I think this is a firefox bug in the way it detects and reports Mic presence information.
My personal view is that the Input/capture sink sources should be created on firefox start up rather than on a per-tab/site basis as with the output sources in the jack only case.
answered Jun 15 '17 at 4:23
Joel Wirāmu PaulingJoel Wirāmu Pauling
1
Mic presence detection? In the old days, there was no such thing. It was always "present" as an input jack on the soundcard, and it still is, on more professional stuff. Mine has 2 XLR connectors that can be used as either line or mic depending on gain. For JACK, it should just create input ports.
– user877329
Jun 15 '17 at 6:02
in firefox/adobe flash. hardware devices (alsa) only are detected. in chrome/pepperflash software devices (pulse and loopback) are also detected. I'm not sure what causes the difference.
– ravery
Jul 13 '17 at 11:26
add a comment |
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%2f923990%2fjack-pulseaudio-and-firefox-enable-jack-for-firefox-in-the-near-future%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
I've compiled mozilla-central firefox with jack support and output (sources) Automatically get created when you visit a site with audio (i.e youtube).
However - input sink sources do not get created ; I don't see them appear in cadence/jack patch bay. So anything that relies on Mic input fails. i.e meet.jit.si / webrtc tests...
Another problem is that even using the pulseaudio bridge ; the same issue input sources even when connected correctly to the pulse-sink don't get recognized by firefox. In Chrome however Mic input correctly uses the plugged capture to pulse-sink. So I think this is a firefox bug in the way it detects and reports Mic presence information.
My personal view is that the Input/capture sink sources should be created on firefox start up rather than on a per-tab/site basis as with the output sources in the jack only case.
answered Jun 15 '17 at 4:23
Joel Wirāmu PaulingJoel Wirāmu Pauling
1
Mic presence detection? In the old days, there was no such thing. It was always "present" as an input jack on the soundcard, and it still is, on more professional stuff. Mine has 2 XLR connectors that can be used as either line or mic depending on gain. For JACK, it should just create input ports.
– user877329
Jun 15 '17 at 6:02
in firefox/adobe flash. hardware devices (alsa) only are detected. in chrome/pepperflash software devices (pulse and loopback) are also detected. I'm not sure what causes the difference.
– ravery
Jul 13 '17 at 11:26
add a comment |
I've compiled mozilla-central firefox with jack support and output (sources) Automatically get created when you visit a site with audio (i.e youtube).
However - input sink sources do not get created ; I don't see them appear in cadence/jack patch bay. So anything that relies on Mic input fails. i.e meet.jit.si / webrtc tests...
Another problem is that even using the pulseaudio bridge ; the same issue input sources even when connected correctly to the pulse-sink don't get recognized by firefox. In Chrome however Mic input correctly uses the plugged capture to pulse-sink. So I think this is a firefox bug in the way it detects and reports Mic presence information.
My personal view is that the Input/capture sink sources should be created on firefox start up rather than on a per-tab/site basis as with the output sources in the jack only case.
answered Jun 15 '17 at 4:23
Joel Wirāmu PaulingJoel Wirāmu Pauling
1
Mic presence detection? In the old days, there was no such thing. It was always "present" as an input jack on the soundcard, and it still is, on more professional stuff. Mine has 2 XLR connectors that can be used as either line or mic depending on gain. For JACK, it should just create input ports.
– user877329
Jun 15 '17 at 6:02
in firefox/adobe flash. hardware devices (alsa) only are detected. in chrome/pepperflash software devices (pulse and loopback) are also detected. I'm not sure what causes the difference.
– ravery
Jul 13 '17 at 11:26
add a comment |
I've compiled mozilla-central firefox with jack support and output (sources) Automatically get created when you visit a site with audio (i.e youtube).
However - input sink sources do not get created ; I don't see them appear in cadence/jack patch bay. So anything that relies on Mic input fails. i.e meet.jit.si / webrtc tests...
Another problem is that even using the pulseaudio bridge ; the same issue input sources even when connected correctly to the pulse-sink don't get recognized by firefox. In Chrome however Mic input correctly uses the plugged capture to pulse-sink. So I think this is a firefox bug in the way it detects and reports Mic presence information.
My personal view is that the Input/capture sink sources should be created on firefox start up rather than on a per-tab/site basis as with the output sources in the jack only case.
answered Jun 15 '17 at 4:23
Joel Wirāmu PaulingJoel Wirāmu Pauling
1
I've compiled mozilla-central firefox with jack support and output (sources) Automatically get created when you visit a site with audio (i.e youtube).
However - input sink sources do not get created ; I don't see them appear in cadence/jack patch bay. So anything that relies on Mic input fails. i.e meet.jit.si / webrtc tests...
Another problem is that even using the pulseaudio bridge ; the same issue input sources even when connected correctly to the pulse-sink don't get recognized by firefox. In Chrome however Mic input correctly uses the plugged capture to pulse-sink. So I think this is a firefox bug in the way it detects and reports Mic presence information.
My personal view is that the Input/capture sink sources should be created on firefox start up rather than on a per-tab/site basis as with the output sources in the jack only case.
answered Jun 15 '17 at 4:23
Joel Wirāmu PaulingJoel Wirāmu Pauling
1
answered Jun 15 '17 at 4:23
Joel Wirāmu PaulingJoel Wirāmu Pauling
1
answered Jun 15 '17 at 4:23
Joel Wirāmu PaulingJoel Wirāmu Pauling
1
answered Jun 15 '17 at 4:23
Joel Wirāmu PaulingJoel Wirāmu Pauling
1
1
Mic presence detection? In the old days, there was no such thing. It was always "present" as an input jack on the soundcard, and it still is, on more professional stuff. Mine has 2 XLR connectors that can be used as either line or mic depending on gain. For JACK, it should just create input ports.
– user877329
Jun 15 '17 at 6:02
in firefox/adobe flash. hardware devices (alsa) only are detected. in chrome/pepperflash software devices (pulse and loopback) are also detected. I'm not sure what causes the difference.
– ravery
Jul 13 '17 at 11:26
add a comment |
Mic presence detection? In the old days, there was no such thing. It was always "present" as an input jack on the soundcard, and it still is, on more professional stuff. Mine has 2 XLR connectors that can be used as either line or mic depending on gain. For JACK, it should just create input ports.
– user877329
Jun 15 '17 at 6:02
in firefox/adobe flash. hardware devices (alsa) only are detected. in chrome/pepperflash software devices (pulse and loopback) are also detected. I'm not sure what causes the difference.
– ravery
Jul 13 '17 at 11:26
Mic presence detection? In the old days, there was no such thing. It was always "present" as an input jack on the soundcard, and it still is, on more professional stuff. Mine has 2 XLR connectors that can be used as either line or mic depending on gain. For JACK, it should just create input ports.
– user877329
Jun 15 '17 at 6:02
Mic presence detection? In the old days, there was no such thing. It was always "present" as an input jack on the soundcard, and it still is, on more professional stuff. Mine has 2 XLR connectors that can be used as either line or mic depending on gain. For JACK, it should just create input ports.
– user877329
Jun 15 '17 at 6:02
in firefox/adobe flash. hardware devices (alsa) only are detected. in chrome/pepperflash software devices (pulse and loopback) are also detected. I'm not sure what causes the difference.
– ravery
Jul 13 '17 at 11:26
in firefox/adobe flash. hardware devices (alsa) only are detected. in chrome/pepperflash software devices (pulse and loopback) are also detected. I'm not sure what causes the difference.
– ravery
Jul 13 '17 at 11:26
add a comment |
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%2f923990%2fjack-pulseaudio-and-firefox-enable-jack-for-firefox-in-the-near-future%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
