Is this expected behavior when casting Tidal albums to Chromecast via Plexamp for Android?

Device: 1st generation Google Pixel on Android 10
Plexamp version: 3.2.2
Tidal with Plex Pass bundle subscriber

So I’ve just started using Plexamp and I like it very much. However, there’s one aspect of the app that differs from Plex, and I’m wondering if it is functioning as intended.

I wanted to listen to Bruce Springsteen’s new album today, so in Plexamp I used the search function, found it, and pressed the play button, already connected to my Chromecast Audio. The screen went dark with a white spinning icon for a few seconds, then returned to the album’s list of tracks, without playing anything. The app remained open; it did not crash.

If I disconnect from the Chromecast, the album will play as directed on my Pixel. After playback has started, the list of devices to which I can cast no longer shows my Chromecast…or any other castable devices, for that matter.

I then added the album to my library, and after connecting to my Chromecast again, attempted playback…which succeeded. And, the list of castable devices is fully populated once more.

This behavior takes place whether my source is set to the collection on my media server, or to Music (On TIDAL).

In the regular Plex app, none of these actions are required. I searched for the Springsteen album, already connected to the Chromecast, found it, pressed play, and the album began playing.

This behavior differs enough from what is described in this post (Issue casting Tidal content) that I felt a new post was warranted. Forgive me if my judgment on that was flawed.

Anyway, I would like for Plexamp to work as Plex does in this regard, as it would be frustrating, especially when wanting to play single tracks from various albums, to have to add those tracks/albums to my library each time prior to playing. Is this possible?

i can’t reproduce this issue; it’s possible that it’s been fixed already, in the new release awaiting review by Apple.

anyone else seeing this behavior?

that sounds more like a networking issue than anything else :thinking:

Apple? I am on Android.

Are the differences between the Plex client app and Plexamp sufficient that there would be such marked discrepancies in how casting operates? I’m willing to let updates play out to see if this resolved, but I don’t believe it’s a networking issue. All my other castable apps are behaving normally. Plexamp only demonstrates an issue when attempting to play Tidal content that’s not in my library.

Thank you for considering and replying to my issue.

sorry, i just meant the release in general, we try to release in lockstep.

very much so.

let’s see if the next release helps at all; if not, get us some debug logs and we’ll have a look!

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.