Subsonic Forum

Is anyone else having problems since the last few days with Chromecast audio playing? The app will connect to the speakers and play the bleep sound but when I try to play something it just shoots me back to the main screen of avsub. If I try to play music before connecting and then cast it the app crashes and gives me a weird error about uitableview when I open it back up. I do see a few API errors on the server about page but nothing that I could use to try to troubleshoot.

Any ideas?

I'm having the same problem in AVSub v. 19.

Hi,

this is weird because Chromecast hasn't changed in the last version and its also working OK for me!

What sort of Chromecast are you using? Audio, or original stick version or other?

Cheers
Rich

I'm using Chromecast Audio with the stock settings. As the OP described, I can do the initial connection and hear the bleep, but then when I immediately play a song I get a red bar saying "reconnecting to [device]," another bleep, and then AVSub returns to the previous album view without playing the track. This just started with the release of v19. The OP reported seeing some errors in his log file, but I don't see any in the three Subsonic logs. The main log shows the same thing as it does when I used to play tracks successfully. I've tried various formats (mp3, flac, etc.) and the behavior is the same. AVsub continues to display the Chromecast connected logo in the upper right, and if I go back to the main connection bar, I see the "disconnect and stop" dialog, so it apparently thinks it's connected.

I just tried it with a regular Chromecast stick (1st gen) and it does the same thing.

Maybe a Java thing? Mine shows 1.8.0_91.

Update: I just upgraded to the latest Java build, 1.8.0_111, and the problem persists. Running on Windows 10, which I have been for months.

Subsonic version is 5.3 (build 4569), which also hasn't changed.

Update: the Chromecast issue persists in version 19.1.1

I also have a Chromecast Audio. As OP described; I get the bleep but then no audio.

I also notice in the app, it initially goes to the now-playing screen, and I get the bleep, but then it bounces back to the menu.

I'm guessing something is going wrong with the app. Maybe it works with the Chromecast Video/HDMI device, but not the Audio?

I've always used iSub; I specifically bought AVSub for the Chromecast support, so I'm hoping this can be resolved!

I should add, in case it might be useful, my device is an iPhone 5S running iOS 10.

My phone is a 6s running 10.0.2, if that helps.

Adalle, I'm having the same problem whether I attempt to play on a Chromecast Audio or a regular Chromecast A/V (1st generation). I'm also a former iSub user who gravitated to AVsub for the Chromecast and replaygain support.

Hi,

I'm on holiday this week, but will look on my return. I've seen the issue where you get 2 beeps but this is AVSub trying to recover when it thinks the connection has broken.

Do you know what firmware version your Chromecast devices are running? You can see this through the iOS Chromecast App.

Thanks
Rich

Thanks, Rich. Both my Chromecast Audio and my first-gen Chromecast are on 1.21.74816

Other users who are having this problem; what version of Subsonic are you running?

Ok, I loaded up the new 'Google Home' app, it says:

Cast firmware version: 1.21.74816

I think this is the current/latest firmware, and matches what chasmo is running. So maybe the problem is specific to the latest firmware.

I'm sure it doesn't matter, but Playback sounds are enabled (which I think is default), and Full dynamic range is enabled (which I think is not default).

My iOS version as per iPhone Settings is: 10.0.2 (14A456)

Even developers can be permitted some vacation, I suppose. Or rather, holiday.

Thanks for your attention even while you're on holiday. I'm sure you'll figure it out once you're back. Happy holidays 'til then!

Hi,

I've just checked my firmware - I have one device at 1.21.74816 - this is an HDMI based V1 device. My 2 audio only devices are still at 1.20.66189.

Off to try now.

Cheers
Rich

Hi all,

I managed to replicate the problem, but this must be really new as I was only looking at Google Cast stuff just before V19 and it was working fine. Bad timing I guess!

It looks like Google has rolled out changes that affect "sender apps" (AVSub is a sender app) using the V2 SDK (they now have V3). There are new status's in the V3 SDK that the V2 SDK doesn't know about and it's causing AVSub to think the device is idle when it is in-fact loading.

I have made some, err, creative changes(!) that have got it working again locally and I've sent this release to beta testers so hopefully will get some feedback shortly.

If feedback is positive, I will roll it out as a release.

Cheers
Rich

Thanks, Rich. Chromecast support is working again in the .2 beta. It also seems like the connection between AVSub and Chromecast has improved - in previous versions it would drop after a couple of tracks. Even with the Chromecast still playing, AVSub would show nothing going on and would require variously restarting AVSub, reconnecting to CC, or stop/start of the CC device to restore the connection. It seems to be greatly improved in this version.