Asset is not ready for playback (with TIDAL)

Hey guys,

I noticed that recently I’ve been receiving the error Asset is not ready for playback when trying to play some music from TIDAL. It’s weird because after some time or when playing different tracks it just works.

I found this in the log:
Jul 07 16:43:47 player volumio[1365]: info: Adding Item to queue: tidal://mymusic/albums/dateadded/139854397
Jul 07 16:43:47 player volumio[1365]: info: Exploding uri tidal://mymusic/albums/dateadded/139854397 in service streaming_services
Jul 07 16:43:51 player volumio[1365]: info: CorePlayQueue::saveQueue
Jul 07 16:43:51 player volumio[1365]: info: CoreCommandRouter::volumioPushQueue
Jul 07 16:43:51 player volumio[1365]: info: CoreStateMachine::updateTrackBlock
Jul 07 16:43:51 player volumio[1365]: info: CorePlayQueue::getTrackBlock
Jul 07 16:43:51 player volumio[1365]: info: CoreCommandRouter::volumioPlay
Jul 07 16:43:51 player volumio[1365]: UNSET VOLATILE
Jul 07 16:43:51 player volumio[1365]: info: CoreStateMachine::play index 95
Jul 07 16:43:51 player volumio[1365]: info: CoreStateMachine::setConsumeUpdateService undefined
Jul 07 16:43:51 player volumio[1365]: info: CoreStateMachine::stop
Jul 07 16:43:51 player volumio[1365]: info: CoreStateMachine::setConsumeUpdateService undefined
Jul 07 16:43:51 player volumio[1365]: UNSET VOLATILE
Jul 07 16:43:51 player volumio[1365]: info: CoreStateMachine::play index undefined
Jul 07 16:43:51 player volumio[1365]: info: CoreStateMachine::setConsumeUpdateService undefined
Jul 07 16:43:51 player volumio[1365]: info: CorePlayQueue::getTrack 95
Jul 07 16:43:51 player volumio[1365]: info: CoreStateMachine::startPlaybackTimer
Jul 07 16:43:51 player volumio[1365]: info: CorePlayQueue::getTrack 95
Jul 07 16:43:51 player volumio[1365]: info: [1594140231600] streamingServices::clearAddPlayTrack
Jul 07 16:43:51 player volumio-streaming-daemon[2108]: Loading tidal configuration
Jul 07 16:43:52 player volumio[1365]: info: Got an error in getStreamUrl, asking volumio for next track
Jul 07 16:43:52 player volumio[1365]: info: CoreCommandRouter::volumioNext
Jul 07 16:43:52 player volumio[1365]: info: CoreStateMachine::next
Jul 07 16:43:52 player volumio[1365]: info: CoreStateMachine::stop
Jul 07 16:43:52 player volumio[1365]: info: CoreStateMachine::setConsumeUpdateService undefined
Jul 07 16:43:52 player volumio[1365]: UNSET VOLATILE
Jul 07 16:43:52 player volumio[1365]: info: CoreStateMachine::play index undefined

Don’t really know how this is implemented but I’d guess that volumio is caching some track URLs that are changing or something like it.

Is anybody having similar issues? Any suggestion on how to avoid it?

I have the same issue it’s not so enjoying:) Do You have other issues apart of this one?