[compat] Subsonic
opened this issue · comments
Subsonic music streamer
www.subsonic.org
Cast button appears and connection tone is heard on Chromecast audio and Google home mini, but connection doesn't play audio. Firefox subsonic controls stop working. Disconnecting from cast device resumes normal operation without rebooting browser or rebooting page. Whitelisting doesn't work either.
Only tested on the demo site.
Doesn't require whitelisting, since it doesn't check the UA before loading the cast SDK.
Connection is established with a custom receiver and a media load request is sent, but never plays and eventually times out. The stream URL sent to the receiver doesn't resolve and is different to the one played in the browser, so could be that. Will need to test on a custom instance.
For me, it does recognise the app and displays the correct song, but doesn't play it. It gets stuck on "BUFFERING" until eventually, as you say, it times out and switches to "IDLE". This is on my server, not the demo site.
Just tried it and it seems to work fine for me now.
Are you on the latest version of the extension? Got any logs from the web console? This is what mine looks like after connecting and toggling playback a few times:
fx_cast (Info): cast.initialize
receiver list empty
init success
receiver found
launching app...
fx_cast (Info): cast.requestSession
fx_cast (Info): Selected receiver
session success: 78b96001-fca1-4d41-a0b4-913fa8b0d3fb
loading...http://192.168.1.219:4040/stream?player=1&id=2&auth=2019854181
media error
new media session ID:1 (loadMedia)
Object { sessionId: "78b96001-fca1-4d41-a0b4-913fa8b0d3fb", mediaSessionId: 1, activeTrackIds: null, currentItemId: null, customData: null, currentTime: 0, idleReason: null, items: null, loadingItemId: null, media: {…}, … }
Session Updated: 78b96001-fca1-4d41-a0b4-913fa8b0d3fb
BUFFERING
PLAYING 3
paused 78b96001-fca1-4d41-a0b4-913fa8b0d3fb
PAUSED
playing started for 78b96001-fca1-4d41-a0b4-913fa8b0d3fb
PLAYING
paused 78b96001-fca1-4d41-a0b4-913fa8b0d3fb
PAUSED
Sure, here is an example log:
fx_cast (Info): cast.initialize
receiver list empty
init success
receiver found
stream?player=4&id=5538&auth=970874528&scrobble=false
launching app...
fx_cast (Info): cast.requestSession
fx_cast (Info): Selected receiver
session success: cce4010f-b25d-47b2-bcfa-483c59e3bcc6
loading...http://10.8.0.1:4040/stream?player=4&id=8298&auth=1880004955
new media session ID:1 (loadMedia)
Object { sessionId: "cce4010f-b25d-47b2-bcfa-483c59e3bcc6", mediaSessionId: 1, activeTrackIds: null, currentItemId: null, customData: null, currentTime: 0, idleReason: null, items: null, loadingItemId: null, media: {…}, … }
Session Updated: cce4010f-b25d-47b2-bcfa-483c59e3bcc6
BUFFERING
IDLE
Session Updated: cce4010f-b25d-47b2-bcfa-483c59e3bcc6
This is version 0.05, updated 15 February 2020.
Hope this helps, and please do let me know if there's any more information I can give you.
Are you using remote access? Something I've observed is that the stream URL sent to the Chromecast receiver is always local to the network of the server (like 192.168.1.219, 10.8.0.1), which means it fails to resolve the URL and times out when casting via remote access. It's why the demo server didn't work for me in my initial test. This also happens in Chrome, so it's not an fx_cast issue as far as I can tell.
If it does work in Chrome and/or you're not using remote access, I'd be interested to see the equivalent log from Chrome and whether the stream URLs match.