Thanks for reporting, we’re looking at it.
Can you tell us the exact actions you did to make it crash?
I was listening to an album from Tidal, added the entire album on the queue to be played and had no problems listening to it, then finished it and stopped listening. After a few minutes I pressed play on the same album (I believe it was in the same search results page, didn’t refreshed the browser or made a new search).
I don’t know if it is already asked or mentioned yet. But one feature that I really like about Tidal is Track Radio, I’ve discovered a lot of music with this feature. I mainly use Volumio to listen to music and the OS would be much completer if I could do my discoveries within Volumio as well.
Keep up the good work
2 Likes
2.839 now installed.
The Qobuz playlist limit of only 50 songs is STILL there!
This new release has just a new facility for us to test the “staging” cloud implementation. Davide is making sure the fixes we’ve done (cloud side) are working effectively. Once he reports that it’s ok, you’ll have the fixes deployed without the need to update your systems
now on 2.839
searching for ‘Richter voices’
qobuz search results are ok, but tidal search results are now to few.
no artist result and no track result in tidal.
can not search separat in tidal or qobuz anymore.
album track order in qobuz is still wrong.
Not sure if it’s the same issue but I get similar log entries when trying to play back Tidal tracks.
To reproduce I go to Browse->Home->Tidal->My Music->Tracks.
I do get the list of my “Tracks” (which is just favourited individual tracks in Tidal’s own user interface) however when I try to play any of them they do not play or even get added to the Queue, and I see errors like this in the system Journal:
Oct 14 10:45:04 volumio volumio[866]: info: Exploding uri tidal://mymusic/tracks/az/101288919 in service tidal
Oct 14 10:45:04 volumio volumio[866]: info: Adding Item to queue: tidal://mymusic/tracks/az/86380178
Oct 14 10:45:04 volumio volumio[866]: info: Exploding uri tidal://mymusic/tracks/az/86380178 in service tidal
Oct 14 10:45:04 volumio volumio[866]: info: Adding Item to queue: tidal://mymusic/tracks/az/26794046
Oct 14 10:45:04 volumio volumio[866]: info: Exploding uri tidal://mymusic/tracks/az/26794046 in service tidal
Oct 14 10:45:04 volumio volumio[866]: info: Adding Item to queue: tidal://mymusic/tracks/az/1904924
Oct 14 10:45:04 volumio volumio[866]: info: Exploding uri tidal://mymusic/tracks/az/1904924 in service tidal
Oct 14 10:45:04 volumio volumio[866]: info: Adding Item to queue: tidal://mymusic/tracks/az/3404950
Oct 14 10:45:04 volumio volumio[866]: info: Exploding uri tidal://mymusic/tracks/az/3404950 in service tidal
Oct 14 10:45:04 volumio volumio[866]: info: Adding Item to queue: tidal://mymusic/tracks/az/66740375
Oct 14 10:45:04 volumio volumio[866]: info: Exploding uri tidal://mymusic/tracks/az/66740375 in service tidal
Oct 14 10:46:42 volumio volumiossh-tunnel[2040]: Timeout, server eu3.myvolumio.org not responding.
Oct 14 10:46:42 volumio autossh[2042]: ssh exited with error status 255; restarting ssh
Oct 14 10:46:42 volumio autossh[2042]: starting ssh (count 2)
Oct 14 10:46:42 volumio autossh[2042]: ssh child pid is 5673
Oct 14 10:46:42 volumio volumiossh-tunnel[2040]: Warning: Permanently added '[eu3.myvolumio.org]:2222,[167.71.136.233]:2222' (RSA) to the list of known hosts.
Oct 14 10:49:22 volumio systemd-journal[186]: Suppressed 1123 messages from /system.slice/volumio.service
A single click on a song in the Tracks list results in several thousand lines in the journal so I’ve only quoted a few. 
Playing Songs via Artists, Albums or Playlists works, it is only playing via Tracks which is affected.
Strangely, I tried reverting to the old Tidal implementation (remove the flag file from the filesystem, reboot and log into Tidal again) and the same problem of “Tracks” logging errors and not working is still present… so this problem seems to be happening for the old implementation as well ?
Version 2.839 on a Raspberry Pi 4.
Just noticed that “Tracks” playback on Qobuz fails in a similar way:
Oct 14 12:33:19 volumio volumio[866]: info: Exploding uri qobuz://song/57323547 in service qobuz
Oct 14 12:33:19 volumio volumio[866]: info: Adding Item to queue: qobuz://song/356482
Oct 14 12:33:19 volumio volumio[866]: info: Exploding uri qobuz://song/356482 in service qobuz
Oct 14 12:33:19 volumio volumio[866]: info: Adding Item to queue: qobuz://song/40219412
Oct 14 12:33:19 volumio volumio[866]: info: Exploding uri qobuz://song/40219412 in service qobuz
Oct 14 12:33:19 volumio volumio[866]: info: Adding Item to queue: qobuz://song/53630186
Oct 14 12:33:19 volumio volumio[866]: info: Exploding uri qobuz://song/53630186 in service qobuz
Oct 14 12:33:19 volumio volumio[866]: info: Adding Item to queue: qobuz://song/4855051
Oct 14 12:33:19 volumio volumio[866]: info: Exploding uri qobuz://song/4855051 in service qobuz
Oct 14 12:33:19 volumio volumio[866]: info: Adding Item to queue: qobuz://song/44667834
Oct 14 12:33:19 volumio volumio[866]: info: Exploding uri qobuz://song/44667834 in service qobuz
Oct 14 12:33:19 volumio volumio[866]: info: Adding Item to queue: qobuz://song/4580734
Oct 14 12:33:19 volumio volumio[866]: info: Exploding uri qobuz://song/4580734 in service qobuz
Oct 14 12:33:19 volumio volumio[866]: info: Adding Item to queue: qobuz://song/53630187
Oct 14 12:33:19 volumio volumio[866]: info: Exploding uri qobuz://song/53630187 in service qobuz
Oct 14 12:33:19 volumio volumio[866]: info: Adding Item to queue: qobuz://song/46932393
So this issue is not even Tidal specific. Tracks playback used to work for me but I can’t remember when the last time I used it successfully was as I generally browse by artist or playlist. Maybe a few weeks ago or even a couple of months ? I’ve updated a few times in the last couple of months and also did a fresh install about a month ago as Tidal/Qobuz completely stopped working for me at the time and I couldn’t get it working again.
Is this Beta Tidal feature only available for Volumio paid users?
The native tidal plugin is only available to paid users.There’s a free trial though
https://volumio.org/my-volumio-overview/
1 Like
Updated to 2.844 on Odroid C2 …
Let me ask, what is the status of my previous observations :
- Missing tracks compared to TIDAL native application
- TIDAL MQA playback of 48, 96, 192 kHz
- TIDAL Skipping track after pause - resume playing
- TIDAL Not playable tracks ( copyright issue)
Great improvements of the QOBUZ plugin 
Will spend some more time to test it deeply,
Thanks a lot !
Today Tidal doesn’t seem to be working at all.
Clicking on Artists, Albums etc simply displays a red message in the top right corner “Error No Results”. The Journal shows:
Oct 18 12:52:32 volumio volumio[871]: info: CoreCommandRouter::executeOnPlugin: tidal , handleBrowseUri
Oct 18 12:52:32 volumio volumio[871]: error: Failed to execute browseSource:
Oct 18 12:52:43 volumio volumio[871]: info: CoreCommandRouter::executeOnPlugin: tidal , handleBrowseUri
Oct 18 12:52:43 volumio volumio[871]: error: Failed to execute browseSource:
This happened a few days ago then came right by itself. Qobuz seems to be working OK.
Is this a known issue with testing of the Tidal integration at the moment ?
Edit: After a reboot Tidal is working again, however as this has happened to me before I don’t think it’s a random glitch. I normally leave Volumio running 24/7 so it’s always available to use, I assume most people also do ?
I had the same problem. Logging out and in solved it for me until next reboot
Same behaviour with Tidal, after rebooting things works again.
Just moved to Beta to see if Qobuz metadata was any better. Have Superstar subscription. I still rarely see Album Story with any data. For example Coltrane ‘58 gives me Nothing Found in Volumio beta but there is certainly an Album Review in the Qobuz app on this album.
Why isn’t this coming through in Volumio?
MQA still doesn’t work in version 2.844.
All master albums, with MQA enabled in sources, show 44,1kHz/16bit and dragonfly red light is green witch means mqa is not decoded.
I had that problem for a long time, with several DAC’s. It’s not clear anywhere in Volumio site and this forum AFAIK, but you need a DAC that does both the decoding AND unfolding, like the Pro-Ject Pre Box S2 Digital.
Thanks guys for the feedbacks.
The new issue about need to log-in\log-out is being investigated as we speak (seems like an issue with the refresh token).
Regarding MQA, we are currently stuck, as we use a different endpoint as previous implementation and things seem not to work correctly when it comes to MQA. We are asking TIDAL but we did not receive any replies yet. Seems that other “Implementors” of this new TIDAL API are having our same problem…
Unfortunately this MQA thingy is preventing us from releasing this new implementation.
We’re going as fast as possible on this
Cant be realesed without this mqa implementation and remain to fix it in near future?