Tidal cache function error on RS150B and RS250

Function TIDAL / QOBUZ / SPOTIFY
#1

Hello Roseloa,
Unfortunately I had to realize that after update 4.21 the Tidal cache size can no longer be adjusted. The illustrated error message follows.
With the SSD 870 EVO, only 1GB is now available as standard.

20220711_183205
20220711_1832054032×2268 1.24 MB

I swapped the SSD, reformatted the SSD, had folders created and created TidalCache folders myself. reboots performed. In all variants, an error message appears as shown. This was adjustable before the update. Please check this error.

20220711_182932
20220711_1829324032×2268 1.29 MB

It’s a very good function, but it no longer works because the memory is full and nothing works anymore. Persistent cache loop.
Please look at this. It is both with my RS150B and also with the RS250 with different SSD. This can only be a software error :wink:

Best regards -MiKo-

1 Like
#2

Hello @MiKo

I have few questions before I answer to your questions.

  1. If you click on the part marked in red, a pop-up will appear.
    How many GB does the Settable Capacity say?

    image
    image1026×508 141 KB

  2. If you click the part marked in red, you can set the storage location. Please check if the path is properly set to your SSD.

    image
    image1005×529 141 KB

  3. Please check if the same problem occurs even when another USB or storage device is connected.

Thank you

#3

Hi RoseHan,

the capacity is 1863 gb.

20220712_223912
20220712_2239124032×2268 1.29 MB

After pressing Attachment, the error message appears immediately.

the path is correct. I also created and tried my own paths. It is therefore exactly this SSD.

Another SSD connected to USB does not have this error.
If I format the SDD originally formatted in Rsoe RS250 in Windows with NTFS and connect it as an external SSD with USB, this error also comes up.

It is strange that I have the same problem with my RS150B. There I can no longer change the capacity with the same error message and Tidal crashes.

All this only came after the update to 4.21

I think it has something to do with formatting on “ROSEDISK”. Is formatting with the Rose devices mandatory? Since the display with red/green cached these problems have been there…

#4

Hello @MiKo

  1. Please check if the same symptom appears after changing from Language Option to English on the Rose device. (Occasionally there is a bug that appears for each set language.)
    Rose device—>Settings—>System settings—>Language Option—>English

  2. Currently, we cannot reproduce the same symptoms. I want to check it remotely.
    If an error message appears after setting 500GB in Settable Capacity, close the error popup and click Settings —> System Settings —> Remote Debug.

  3. In addition, please tell us the Rose model name and ROSE ID in Settings > System Information.

Thank you

#5

Hello ROSEHAN

  1. the problem can be solved by changing the language.
    If you switch back to German afterwards, the cache works.
    But the capacity doesn’t work. So it’s definitely up to the language option.
    Can you please include this in one of the updates in the future. Thanks.

  2. I ran remote debug.

  3. For your purposes and troubleshooting:
    RS250: 0C871E (remote debug performed)
    RS150B: 0C860C (here is the same language problem)

One last question:
Is it possible to copy the already generated cache of an RS150B to the RS250’s SSD? That would be great. Does it work? Or does a separate cache have to be generated on each device/SSD?
Thank you…

#6

Hello @MiKo

Does it mean that if you change the language to English, it will be set to the 500GB you want? When you switch back to German, the problem appears. Is it right?

We want to remotely debug with your device at 9:00am German time.
RS250 & RS150: If an error message appears after setting 500GB in Settable Capacity, close the error popup and click Settings —> System Settings —> Remote Debug.
If possible please leave a comment below

Thank you

#7

Hello ROSEHAN,

it behaves like this: I can only set the capacity when the system language is set to English. If I switch back to German as the system language, the caching works, the 500GB are displayed, everything is ok. tidal only crashes if you want to set a different capacity. otherwise everything works fine.

Were you able to debug it? I was probably gone. The device must be switched on. Do you have to confirm something? How does your debugging work?

Do we have to repeat it? Or is my description of the error sufficient?

One last question:
Is it possible to copy the already generated cache of an RS150B to the RS250’s SSD? That would be great. Does it work? Or does a separate cache have to be generated on each device/SSD?
Thank you

#8

Hello @MiKo

We want to remotely debug with your device at 9:00am German time.
RS250 & RS150: If an error message appears after setting 500GB in Settable Capacity, close the error popup and click Settings —> System Settings —> Remote Debug.
Follow my explanation. Please tell me when you set remote debug.

For your question. It will not work that way. When copying, the cached sound source may be crashed. And the cached sound source may not be recognized.

Thank you

#9

Hi ROSEHAN,
I will switch on the devices at 8:50 German time.
I will do remote debugging on both devices at 08:55.
Is that OK?

#10

@MiKo

Yes I will tell the person in charge.
Thank you

#11

Remote debugging is done 08:55.
The message showed that it is switched on.

#12

@MiKo

Yes we are looking on it

It is currently replayed on our side, and it seems that it will be fixed in the next update.
Thanks for your help.

#13

Even if it was a bit difficult, but I enjoyed doing it. After all, that helps everyone :slight_smile: