Track switching is too slow on Tidal.. vs. ProPlus vs. NAS/Mediserver.

S

stemplar007

Member
Joined
May 2, 2024
Messages
24
When using NAS/Mediserver, track switching is fine, but when using Tidal(Connect/Wiim Home Tidal client) it is too slow.. Can this be speeded up with a FW update? I think this is annoying..(this is almost the only problem I have with otherwise brilliant Wiim Home streaming software, e.g. vs. HEOS/ Tidal connect/BLUE os ) Thx.
ps. ps. This was already discussed in October, but the situation has not changed since then..
 
Last edited:
Mr Ee said:
How slow is too slow?
About 2 secs for me.
Click to expand...
Tidal connect 3-5sec. (16 bit 3sec/24bit higher bitrate 5sec sometimes) Tidal client (WHome) 2-3 sec. Mediaserver 1 -2sec. NET speed 200 mbps. Before that I had a WiimPP. device.. there was no such pause/buffer? in Tidal Connect ... I will add that I had a few weeks of correspondence with Tidal, because sometimes their server/cloud capacity was critically low.. now about a week ago. can be said to be good... so they are suspicious,,
 
of course we can say that I should use the WiimHome client and not connect.. But unfortunately in many respects the connect algorithm is better than the one implemented in W home.. e.g. Tidal updates new albums every Friday, compare them, but at the same time what does connect vs home show. The fragment is not included in home, what connect contains is also mixed.. this is a mistake, if possible it could be fixed.. One more question, is it possible to know how big the buffer memory is in the Wiim PP, and how big it is in the Ultra? Because this has also occurred to me.. thx
 
Just checked. Both my Ultra and Pro+ is less than 2 sec delay when selecting a new track in WHA or in Tidal app when already playing. This is independent of track length or quality.

Playing gapless to next track in both app works without problems.

I have a (external optical) 1 Gbps cabled network connection to both devices.

Maybe you can check your actual network speed. Looks like that could be the issue.
 
henninggodske said:
Just checked. Both my Ultra and Pro+ is less than 2 sec delay when selecting a new track in WHA or in Tidal app when already playing. This is independent of track length or quality.

Playing gapless to next track in both app works without problems.

I have a (external optical) 1 Gbps cabled network connection to both devices.

Maybe you can check your actual network speed. Looks like that could be the issue.
Click to expand...
As I wrote, Tidal has been glitching in my area lately... So I'm not sure if this is an Ultra bug.. but.. at the same time it's not unique, others have said this too.. One more thing, the internet speed is enough.. you don't need 1000 mbps if Netflix 4k HDR/Atmos is perfect without any problems or buffering... vs Tidal connect..
 
Have you tried toggling the ipv6 and preferred dns settings in the wiim app?
A week or so ago I was having issues with tidal connect taking up to 20 secs to skip a track.
It was a new wiim device (not an ultra), and I think this may have been part of the cause.
Or it miraculously worked ok the next night, and ever since.
 
There are also problems in my system, which appear differently, but I am sure that the reason is the same: the buffer size may be small, or the reading - updating with the image power data is not synchronized. Is it possible to know how much buffer memory was installed in which model?
Even under WHA and with T.Connect, playback starts after changing the track, but the screen appears with a delay of 6-10 seconds, e.g. the play/pause button, the metadata including the actual playback time.
Also, going back doesn't work during playback, only after the snapshot, according to my memories, it didn't work like that at first.
At this time got my tidal on pc this error message:
wiim tidal error scrshot.jpg
 
I think it's in the best interest of Wiim to investigate this. It rules out whether it's a Tidal problem or an Ultra problem. I have a lot of respect for the Wiim team for updating their firmware so quickly and frequently. This is a problem that can't be solved by not using Tidal Connect. Because the Tidal client is in Wiim Home. It has nothing to do with the internet speed (or ipv/dns settings), but it could be something to do with the Tidal-Wiim connection.
 
Last edited:
stemplar007 said:
I think it's in the best interest of Wiim to investigate this. It rules out whether it's a Tidal problem or an Ultra problem. I have a lot of respect for the Wiim team for updating their firmware so quickly and frequently. This is a problem that can't be solved by not using Tidal Connect. Because the Tidal client is in Wiim Home. It has nothing to do with the internet speed (or ipv/dns settings), but it could be something to do with the Tidal-Wiim connection.
Click to expand...
Have you raised a ticket to WiiM so they can inspect your device logs and perhaps suggest changes? Anecdotal evidence here doesn’t give them a chance to do that.
 
stemplar007 said:
Please read carefully. The main problem is not Wim Home. It's Tidal Connect, where track switching is too slow (3-6 sec)
Click to expand...
Are you saying it doesn’t happen with the WiimHome app?

Edit: I note you do mention the WiiM Home client in your opening post, so the above video would appear to be relevant.
 
Burnside said:
Azt akarod mondani, hogy ez nem történik meg a WiimHome alkalmazással?

Szerkesztés: Megjegyzem, hogy a nyitó bejegyzésben említi a WiiM Home klienst, így a fenti videó relevánsnak tűnik.
Click to expand...
Unfortunately, it doesn't allow editing, sorry, it mostly affects Tidal Connect.
 
stemplar007 said:
Please read carefully. The main problem is not Wim Home. It's Tidal Connect, where track switching is too slow (3-6 sec)
Click to expand...
You did say "using Tidal(Connect/Wiim Home Tidal client)". But yes, You are right. Playing on WiiM devices from Tidal app have very long delays, as if WiiM devices have to reconnect with Tidal for each track. I think that used to work?
 
There is a difference in the connect implementations for WHA and the original app, it's visible in the delay time when switching tracks for example. I always had it, so maybe it's related to the servers infrastructure for the country's region.
 
It is related to the quality of the track (bits per second). If you change the WiFi streaming quality in the Tidal app to low, the track change happens faster. Unfortunately the bit rate is then also low on WiiM.

Not sure WiiM can do anything about that?
 
You must log in or register to reply here.
Back
Top