Issue with Tidal Media Loading and Compatibility with Roon Server on 2015 HP Computer (ref#OPYWSA)

Full form submission

What’s happening?

I'm having trouble connecting to Roon

What type of connection issue?

Sometimes I can connect, sometimes I can't

When I try to listen FLAC 192 kHz 24 bit I will gor this sentance: "Tidal media is loading slowly. This may indicate a networking or connectivity problem". Could this problem accure because of my too old year 2015 HP-computer, where the ROON-server is located. What is the minimum demands for ROON-server?

If it only happens with 192/24 then it is most likely either a performance problem on the network problem or with the computer.

For straight playback of 192/24 (without DSP and on a wired network connection) the HP should probably be fast enough, but let us know about other factors:

  • Is the HP on wifi or wired?
  • What type of CPU is in the HP (or tell us the HP model)
  • Are you playing the 192/24 from local files or Qobuz/Tidal?
  • Are you using MUSE (DSP) in Roon?
  • What are you using as the output device?

Here are the official specifications:

Hi Suedkiez, thank you for taking my problem :slight_smile: !

  • My HP is on wifi. I have tested also wired, but same result, 192/24 is not working. But working with Tidal OK.
  • HP-840G2 and CPU is Intel(R) Core™ i5-5200U CPU @ 2.20GHz 2.20 GHz
  • I am not using MUSE
  • I am playing mainly Tidal with Roon

Glad to help but I am not quite sure what’s going on :slight_smile:

OK, this can happen, it’s just the first thing to check in this case

The design of Roon and solutions like Tidal differ a lot and put load on different parts, so it’s not unusual that they behave differently. Roon puts more load on the server and the network, Tidal on the endpoint.

Thanks. The HP’s CPU is not the latest :wink: but on gut feeling I would have said it should be fine for straight playback of 192/24. I have a 10th gen NUC from 2020 with ROCK, and this is the comparison of CPU single core speed (the most relevant benchmark for Roon). Mine at the top, yours at the bottom:

So yes there is a difference, but nominally it’s just 30% difference and mine does not even notice the load caused by 192/24 playback. I would have guessed MUSE but you don’t use it…

Can you post a screenshot of your signal path while you are playing 192/24, please.

But do you have any 192/24 local files? It would be very helpful to know if the problem occurs with them as well.

Oh, and are you using an external DAC or what else is your output device? How is this connected?

Thank you for these replies.
Signal bath I do not know how to take it, so I have ask some professionals to check my network.

From Tidal everything plays well, even 192/24. My DAC is HifiRose RS150B.

Perhaps I need to buy new computer to place Roon server there?

It’s Roon’s Signal Path, you just need to click this little “light” on the play bar in Roon while you are playing:

It will tell us a little bit about the computer performance.

OK, so this is Roon Ready and connected by the computer network? Also on wifi?

We will find out

How, nice to see the signal path so easily :slight_smile: The small glowing light was Purple. But same problem, after start 192/24 stopped and informed me

OK, the signal path seems fine when it was taken. At this point, it did not display the performance indicator, meaning that performance was by far good enough, despite the small usage of MUSE for the crossfade.

It doesn’t look like the speed of the HP is your problem.

Which brings us back to whether the HifiRose is network-connected and whether this is by wifi, too.

1 Like

My HifiRose is by wifi. Now all problem has been solved.
The problem was in the internal network. One port was faulty, and the network lane was only 80/8, but changing the port brought the result to 100/100, so now also 192/24 repeats as it should. Thanks for the advice :slight_smile: !

2 Likes

Great, thanks for updating the thread with the information. I hope you can enjoy the music now :slight_smile:

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