Bonte,
There you go again.
When you actually build anything, then lets talk.
Enough said.
Thank you for your offer, but I’d rather talk to Amir then. 
1 Like
@ROSEHAN
Hello,
I did a reset and that did not solve the problem.
There is no problem with my network, because with the same connection the same cable the eversolo T8 was performing flawlessly with the same files form the same NAS from the same folder.
To help you with this the issue occurred after i chose to play the second album or after fast-forwarded the track that was playing from the app.
The issue failed to load the next track has the behavior of appearing in the playback queue but fail to
start.
Now i am facing another buggy behavior. Just watch the video bellow.
20261017_193719035.mp4
Generally the firmware it’s not well structured. This happened when i added second smb folder from my NAS from the same path as the first one and deleted it afterwards. And as i understand needs to rescan my library. That’s an awful behavior.
You have to try a little harder.
I am adding another buggy behavior. I’ve changed from smb connection to adding a disk connected to a usb of the device. The music never starts. Try to play music together with library scanning. Always in tests use DSD512 files and not 16bit flac files and say afterwards there is nothing wrong. See the video bellow.
What can i say…
To help you… generally the device needs a lot of restarts to get in working order. Hangs a lot. In programming there is an … if (condition == true) but there is also an … if (condition == false) and that conditions your development team is not using and the device hangs and needs restart to get out from this unconditioned states.
This is the speed of transferring files to the connected usb hard disk through sfp connection.
With this so slow speed how can we expect the buffer to fill instantly thought network. No my network is ok. Your firmware makes the network connections of the device so slow.
My friend, you aren’t reading the posts from me and other users very carefully:
-
TIDAL buffering issue on the RS151
The problem isn’t on my end; it’s happening to another user, and it started immediately after they installed the latest firmware. I’ll suggest that they try reinstalling the TIDAL app and logging out of their TIDAL account—maybe that will help.
Personally, I’m still holding off on installing the latest update because I’m genuinely worried that my RS151 might stop working properly afterward. It’s a ridiculous and embarrassing situation, but those are the facts. -
Option to downgrade firmware
Given how many issues you’re having with updates, I’d personally look into this immediately—though I should note that downgrading firmware via external storage carries a significant risk for users. -
VU meter performance
Looking at what you’ve just written, it seems you misled us about 10 weeks ago, when you claimed that this issue would be resolved by the end of October with a new firmware update. It’s worth being more careful with what you post—it’s embarrassing later on, and some of us actually remember what you’ve said on the subject. Honestly, given the current pace of your system software updates, I’m not sure we’ll ever see the VU meters working correctly. -
Changes in sound quality following a firmware update
It’s difficult for me to comment on this, as I’ve never installed a flawed firmware version—I’ve always waited for the corrected releases—and the sound on my device is fine. However, some users have reported that their players sound worse after installing the latest firmware. It’s probably worth looking into this.
Unfortunately, the measures mentioned above yielded no results. On Monday, a friend’s Rose RS 151 is heading to an authorized service center for repairs. The player is only 14 months old—exactly the same age as mine, as we bought them at the same time. The only difference is that I didn’t install the latest firmware.
I am sure that the sound stage completely changed on my RS130 with the latest update: body is missing and clarity as openness in soundstage. I am not sure what to do now since on the other hand some issues have been fixed.
Maybe Rose you can comment on this and check out the worse sound performance. 🤷
Thank you
1 Like
Normal, we are a few who have noticed an audio change on the Rs130 and asked to return to a previous version. ˋ
Currently I am in 5.9.07
1 Like
And wasn’t the 07 software even worse than version 08?
For the audio the 5.9.07 is very good
I don’t know what you touched in LINE OUT.
I use the XLR output fixed at 3V on my RS151.
I’ve lost a lot of clarity and soundstage. The listening experience is mediocre now. Firmware version 03 sounded much better.
I’ve checked all the output settings, filters, etc., and I even did a factory reset. Everything has been thoroughly checked.
There’s no point in repeating myself. I would just like to know when you plan to release a firmware update to fix this issue, as it seems to be affecting many users here.
Thanks.
2 Likes
C’est simple : jamais !!!
No, I do not agree at all with that assessment.
Rose is a great brand delivering spectacular sound.
I am sure they are actively working to improve their firmware.
3 Likes
I had to call on 2 times to have previous FWs and 4 friends did like me!!
Users have been complaining about a failed system for weeks!!!
Well, take a look at one! 
@JMBARG was right back then. Everyone said he should finally stop crying. Jimmyboy was the first to realize it.
2 Likes
Go For Early 5.12 firmware:)
1 Like
Is there an Early Adapter firmware after 5.11.08 ??
yes, seems so:
But it’s apparently not any newer… VU works with this version.
https://community.roseaudio.kr/t/early-access-ver-5-12-05-rose-os-5-12-05-sw-update-notice/15140
2 Likes
Early Access 5-12-05 came out 18th of june and Official Software 5-11-08 came out 21th of september.
So why should 5-12-05 be “newer” ??
This post was flagged by the community and is temporarily hidden.
If you find it and these are your words “a fucking piece of shit” why dont you buy another device and leave this place.
You are not helping here 
3 Likes
This post was flagged by the community and is temporarily hidden.
1 Like