Chromecast “Audio” not found by pulseaudio-dlna on 16.04
I have a brand spanking new Chromecast Audio. I can cast to it from my Android phone using cast-enable apps like Spotify and Pandora. I can also cast to it from my Android phone using the awesome AirAudio app.
I can cast to the Chromecast Audio from Ubuntu 16.04 using either (A) Chrome's google cast plugin; or (B) mkchromecast. But the former is inconvenient (no media key support) and the latter seems to have huge latency issues (around 27 seconds) -- and it is also seems to require WiFi as opposed to allowing an ethernet connection.
What I can't do, is find the Chromecast Audio using pulseaudio-dlna. Pulseaudio-dlna simply does not see the Chromecast at all. This is unexpected because the pulseaudio-dlna does find my AVR receiver and my DirecTV receiver. And as noted above, other Ubuntu apps can find the Chromecast Audio. After reading the usage notes for pulseaudio-dlna, I checked for a firewall issue -- but the Ubuntu 16.04 computer does not have the firewall on.
Any ideas what is going wrong here?
(I tried posting an issue on the pulseaudio-dlna github page, but those are not generally answered.)
sound google-chrome pulseaudio android
asked Aug 20 '16 at 18:46
RsyncRsync
51931229
add a comment |
I have a brand spanking new Chromecast Audio. I can cast to it from my Android phone using cast-enable apps like Spotify and Pandora. I can also cast to it from my Android phone using the awesome AirAudio app.
I can cast to the Chromecast Audio from Ubuntu 16.04 using either (A) Chrome's google cast plugin; or (B) mkchromecast. But the former is inconvenient (no media key support) and the latter seems to have huge latency issues (around 27 seconds) -- and it is also seems to require WiFi as opposed to allowing an ethernet connection.
What I can't do, is find the Chromecast Audio using pulseaudio-dlna. Pulseaudio-dlna simply does not see the Chromecast at all. This is unexpected because the pulseaudio-dlna does find my AVR receiver and my DirecTV receiver. And as noted above, other Ubuntu apps can find the Chromecast Audio. After reading the usage notes for pulseaudio-dlna, I checked for a firewall issue -- but the Ubuntu 16.04 computer does not have the firewall on.
Any ideas what is going wrong here?
(I tried posting an issue on the pulseaudio-dlna github page, but those are not generally answered.)
sound google-chrome pulseaudio android
asked Aug 20 '16 at 18:46
RsyncRsync
51931229
add a comment |
I have a brand spanking new Chromecast Audio. I can cast to it from my Android phone using cast-enable apps like Spotify and Pandora. I can also cast to it from my Android phone using the awesome AirAudio app.
I can cast to the Chromecast Audio from Ubuntu 16.04 using either (A) Chrome's google cast plugin; or (B) mkchromecast. But the former is inconvenient (no media key support) and the latter seems to have huge latency issues (around 27 seconds) -- and it is also seems to require WiFi as opposed to allowing an ethernet connection.
What I can't do, is find the Chromecast Audio using pulseaudio-dlna. Pulseaudio-dlna simply does not see the Chromecast at all. This is unexpected because the pulseaudio-dlna does find my AVR receiver and my DirecTV receiver. And as noted above, other Ubuntu apps can find the Chromecast Audio. After reading the usage notes for pulseaudio-dlna, I checked for a firewall issue -- but the Ubuntu 16.04 computer does not have the firewall on.
Any ideas what is going wrong here?
(I tried posting an issue on the pulseaudio-dlna github page, but those are not generally answered.)
sound google-chrome pulseaudio android
asked Aug 20 '16 at 18:46
RsyncRsync
51931229
I have a brand spanking new Chromecast Audio. I can cast to it from my Android phone using cast-enable apps like Spotify and Pandora. I can also cast to it from my Android phone using the awesome AirAudio app.
I can cast to the Chromecast Audio from Ubuntu 16.04 using either (A) Chrome's google cast plugin; or (B) mkchromecast. But the former is inconvenient (no media key support) and the latter seems to have huge latency issues (around 27 seconds) -- and it is also seems to require WiFi as opposed to allowing an ethernet connection.
What I can't do, is find the Chromecast Audio using pulseaudio-dlna. Pulseaudio-dlna simply does not see the Chromecast at all. This is unexpected because the pulseaudio-dlna does find my AVR receiver and my DirecTV receiver. And as noted above, other Ubuntu apps can find the Chromecast Audio. After reading the usage notes for pulseaudio-dlna, I checked for a firewall issue -- but the Ubuntu 16.04 computer does not have the firewall on.
Any ideas what is going wrong here?
(I tried posting an issue on the pulseaudio-dlna github page, but those are not generally answered.)
sound google-chrome pulseaudio android
sound google-chrome pulseaudio android
asked Aug 20 '16 at 18:46
RsyncRsync
51931229
asked Aug 20 '16 at 18:46
RsyncRsync
51931229
edited Aug 20 '16 at 19:13
Rsync
asked Aug 20 '16 at 18:46
RsyncRsync
51931229
asked Aug 20 '16 at 18:46
RsyncRsync
51931229
asked Aug 20 '16 at 18:46
RsyncRsync
51931229
51931229
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
I was able to resolve this issue by resetting the router that was between my primary router and the computers that were failing to connect to the Chromecast Audio with pulseaudio-dlna. Some setting in the router (other than firewall) must have conflicted with pulseaudio-dlna.
That said, there is something in pulseaudo-dlna that operates differently than Google Chrome's casting plug-in and mkchromecast. Both of those worked under the old router setup.
Also, it may be notable that mkchromecast did not work with pulseaudio-dlna installed. So there may be more than one conflict.
[My primary problem now is major lag that seems to grow from about 2 seconds at the start of listening to Pandora/Pithos, to about 25 seconds after about an hour of listening.]
answered Aug 20 '16 at 23:27
RsyncRsync
51931229
add a comment |
I resolved the issue on this link a bug report and stopping the Linux firewall.
answered Dec 25 '17 at 15:18
Calvin PachecoCalvin Pacheco
11
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%2f814683%2fchromecast-audio-not-found-by-pulseaudio-dlna-on-16-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I was able to resolve this issue by resetting the router that was between my primary router and the computers that were failing to connect to the Chromecast Audio with pulseaudio-dlna. Some setting in the router (other than firewall) must have conflicted with pulseaudio-dlna.
That said, there is something in pulseaudo-dlna that operates differently than Google Chrome's casting plug-in and mkchromecast. Both of those worked under the old router setup.
Also, it may be notable that mkchromecast did not work with pulseaudio-dlna installed. So there may be more than one conflict.
[My primary problem now is major lag that seems to grow from about 2 seconds at the start of listening to Pandora/Pithos, to about 25 seconds after about an hour of listening.]
answered Aug 20 '16 at 23:27
RsyncRsync
51931229
add a comment |
I was able to resolve this issue by resetting the router that was between my primary router and the computers that were failing to connect to the Chromecast Audio with pulseaudio-dlna. Some setting in the router (other than firewall) must have conflicted with pulseaudio-dlna.
That said, there is something in pulseaudo-dlna that operates differently than Google Chrome's casting plug-in and mkchromecast. Both of those worked under the old router setup.
Also, it may be notable that mkchromecast did not work with pulseaudio-dlna installed. So there may be more than one conflict.
[My primary problem now is major lag that seems to grow from about 2 seconds at the start of listening to Pandora/Pithos, to about 25 seconds after about an hour of listening.]
answered Aug 20 '16 at 23:27
RsyncRsync
51931229
add a comment |
I was able to resolve this issue by resetting the router that was between my primary router and the computers that were failing to connect to the Chromecast Audio with pulseaudio-dlna. Some setting in the router (other than firewall) must have conflicted with pulseaudio-dlna.
That said, there is something in pulseaudo-dlna that operates differently than Google Chrome's casting plug-in and mkchromecast. Both of those worked under the old router setup.
Also, it may be notable that mkchromecast did not work with pulseaudio-dlna installed. So there may be more than one conflict.
[My primary problem now is major lag that seems to grow from about 2 seconds at the start of listening to Pandora/Pithos, to about 25 seconds after about an hour of listening.]
answered Aug 20 '16 at 23:27
RsyncRsync
51931229
I was able to resolve this issue by resetting the router that was between my primary router and the computers that were failing to connect to the Chromecast Audio with pulseaudio-dlna. Some setting in the router (other than firewall) must have conflicted with pulseaudio-dlna.
That said, there is something in pulseaudo-dlna that operates differently than Google Chrome's casting plug-in and mkchromecast. Both of those worked under the old router setup.
Also, it may be notable that mkchromecast did not work with pulseaudio-dlna installed. So there may be more than one conflict.
[My primary problem now is major lag that seems to grow from about 2 seconds at the start of listening to Pandora/Pithos, to about 25 seconds after about an hour of listening.]
answered Aug 20 '16 at 23:27
RsyncRsync
51931229
answered Aug 20 '16 at 23:27
RsyncRsync
51931229
answered Aug 20 '16 at 23:27
RsyncRsync
51931229
answered Aug 20 '16 at 23:27
RsyncRsync
51931229
51931229
add a comment |
add a comment |
I resolved the issue on this link a bug report and stopping the Linux firewall.
answered Dec 25 '17 at 15:18
Calvin PachecoCalvin Pacheco
11
add a comment |
I resolved the issue on this link a bug report and stopping the Linux firewall.
answered Dec 25 '17 at 15:18
Calvin PachecoCalvin Pacheco
11
add a comment |
I resolved the issue on this link a bug report and stopping the Linux firewall.
answered Dec 25 '17 at 15:18
Calvin PachecoCalvin Pacheco
11
I resolved the issue on this link a bug report and stopping the Linux firewall.
answered Dec 25 '17 at 15:18
Calvin PachecoCalvin Pacheco
11
edited Jan 25 at 19:54
answered Dec 25 '17 at 15:18
Calvin PachecoCalvin Pacheco
11
answered Dec 25 '17 at 15:18
Calvin PachecoCalvin Pacheco
11
answered Dec 25 '17 at 15:18
Calvin PachecoCalvin Pacheco
11
11
add a comment |
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%2f814683%2fchromecast-audio-not-found-by-pulseaudio-dlna-on-16-04%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
