I am experiencing a rather strange issue with casting Tidal content. If I select the cast device before commencing playback of a Tidal album that has been added to my library, I get the following and the album won’t commence playing:
However, if I select the cast device after commencing playback of the album, it will cast to the device just fine.
If playback (of non Tidal content) has been commenced after casting, Tidal tracks or albums from my library cannot be queued (either via Play Next or Add to Queue). The onscreen notification that they have been added appears but they are not added to the play queue.
But if the playback has been established by the method of commencing playback before casting, I can add Tidal tracks to the play queue.
The final part of this very strange puzzle is that radios will play and queue up Tidal content just fine regardless of when casting is commenced but adding Tidal content once playback is underway depends on when I commenced casting.
Reproduced on both the Chromecast 2nd gen and Shield TV built in Chromecast. Continues after restart of all devices.
Edit: I should note that none of this occurs if just playing music, Tidal and non-Tidal, on the Pixel.
I’ve found exactly the same issue. It’s very strange that to play Tidal content you have to initiate play before casting. Hopefully someone may be able to cast some light on this.
I have the same problem, Tidal streaming (on a Plex machine on network controlled by Plexamp Android) just spins and never plays. Server based music files though are fine.
Same thing happens with Sonos casting, works fine for local content but not Tidal.
I can sometime get it to sporadically connect, starts playing on the Sonos but disconnects from Plexamp, but the queue is still going on Sonos.
Again local content plays and connects fine. Did a check through Plex App itself and that seems to work fine casting Todal music to Sonos, so it’s just Plexamp. Also this happens from my Android Device (OnePlus 7 Pro) and from a Windows 10 machine as well.
At least we have some Casting, which is brilliant! (thanks Plexamp team )
Sadly, this is still happening especially when remote controlling a player on another machine, it seems like plexamp is talking to the server in a different way to the Plex app and I’m not sure the server likes it. I’ve seen a black screen and spinner on my Android phone too so many times I’m scared to touch the app.
This seems to happen more on tidal tracks, that I’ve added to my library, and whilst the servers web app works solidly, if I try to remote control a player, on the server machine, from my phone the phone either crashes, or skips through tracks or shows the black screen of spin… On the windows machine that has the player I’ll see an error flash up as it it tries to play the tracks but fails.
Sorry for the long description but I’d really like to help fix this and more than happy to be a tester/reporter to help get this resolved for others. @elan
I have been testing Plex Server for the last few days with just local content, no Tidal. I am seeing the same issues as above. Playing tracks on my Android phone using plexamp works fine but as soon as I try sending tracks to other devices running plex player the blank spinning screen starts, sometimes I cant even establish a connection when selecting a device from the list of other playback devices.
This issue seems to be mostly in relation to other plex players, when selecting a chromecasf device all seems OK.
My plex server is a Windows 10 desktop and remote players are android devices, tablets and android TV. Would love to get this resolved and only to willing to help.
This issue is not resolved in 3.2.1. Selecting Chromecast device and then starting playback of Tidal album added to my library now just crashes the app every time.
Starting playback of the tidal album and then selecting the Chromecast device will ensure playback.
the issue casting TIDAL content added to library to chromecast will be fixed in the next release. if you’re seeing something other than this, please open up a separate thread with the specific description and app logs.
)
Will look. Is this only with TIDAL content added to library, or directly from TIDAL as well?