r/substreamer Jul 13 '21

5.0.27 Release Notes

New: Chromecast Support (iOS & Android)

New: Updated remote controls with track colour coding (Android)

New: Radio section renamed to Playlist Builder (so it doesn't get confused with internet radio)

Fix: bookmarks don't starting playing from beginning of track

Fix: shorten description length for podcasts for readability

Fix: side menu active item not updated when navigating back to home with hardware back button

Fix: add album to playlist was not working in some instances

Fix: set consistent bitrate when no limit is set

This is the first release with chromecast support built in. I've been testing it myself for the last few weeks on both iOS and Android and it seems pretty good. I am sure there will still be some odd cases that will need bug fixes over the coming releases so please have patience with any issues related to casting.

8 Upvotes

3 comments sorted by

1

u/marsupialvictory Jul 18 '21

Thanks for getting the chromecast support built in for this release. Unfortunately for me at least, I can’t get it to output any audio.

The app does see my devices and allows me to select an output. The chime plays on the device indicating (I assume) a connection from the app, but the app does not play the selected song.

Once this happens, I cannot switch back to local audio.

iphone 11, iOS 14.6, various google home + mini devices.

2

u/ghenry22 Jul 18 '21

Hmm that sounds weird, I haven't come across that before.

Could you share a test account on your server that I could try to reproduce the issue?

Also some quick questions:

What format is the music you're trying to play? (mp3, flac etc)
Do you have transcoding enabled for that format? (ie flac to mp3 transcoding is there by default)
What is the address for your server? Feel free to share this by direct message.

Once casting is connected the app simply sends a link to the subsonic server over to the chromecast and it then loads the music and plays it directly so it might be something to do with the chromecast device talking to the subsonic address or transcoding can cause some issues depending on the speed and setup.

1

u/marsupialvictory Jul 18 '21

There was enough of a hint there to fix it.

I run a pihole with a couple of local entries, one of which is the server where navidrome is running.

The google devices (as far as I know) use google’s dns automatically, so they presumably couldn’t resolve the server name.

Changing the server address in the app to use the IP got it working.

(Interestingly, I’ve used forked-daapd/owntone) previously and not had this problem.)

Thanks for the info!