Rescan of media library

ROSE Products RS150 & RS150B
#22

I had to reboot my router and the router gave my NAS a new IP-adress. That caused my media db on R150B not to recognize my NAS. I deleted the db and connected my R150B to the new IP-adress.

So I did a new scan on the R150B of my music (275 000 tracks) on my NAS and was prepared to have to wait 96 hours for the scan to end as I did last time.

To my surprise the complete scan this time took “only” 31 hours. So some trimming has been done.

I will later add a couple of new CD:s and do a rescan to see if the rescan will also take 31 hours.

#23

I have about 52,000 tracks, approximately 1.5TB of FLAC music files saved on the Rose’s internal SSD and it used to take more than 3 hours for a full rescan of the Music Library.

After the last update, a full scan takes about 1 hour 40 minutes, so - although scanning time is still rather long - things have improved.

#24

The scanning time and the fact that SMB1 must be activate are two issues for a lot of people. HifiRose, do something about this or you are going to loose a lot of market share!

1 Like
#25

@Marc_62
I do agree with your opinion.
HiFiRose should be very concerned about customer satisfaction regarding these issues…

1 Like
#26

Just to mention. I use Roon, my Files are all on my NAS. Roon and NAS are connected with a 10 GB/s LAN setup. It takes less than 1 minute to do a re-scan of 120000+ music files.
I don’t like the library in the Rose due to missing things, and the speed.
I only have some SACD Files on the internal SSD for testing things. Otherwise I prefer Roon, with the better performance and the extra of information like in a WIKI.

#27

I also have Roon. The difference is that Roon is on my desktop computer with a poweful processor and a lot of memory.

I am beginning to believe that the lack of speed in scanning on my R150B is because it has a much less powerful processor and less memory. Thats why we will never see the same scanning time as Roon in the R150B. Any comment from HiFiRose would be grateful.

The only way to use the R150B with a large media library is to use the app in Folderview.

#28

I agree.
or really just use Roon - and use the Rose as a player only. personally I don’t care about the internal library. my complete music collection would not fit anymore on a SSD - and you are right, its mainly a performance issue, and the lack that just SMBv1 can be used for the NAS connection (I would prefer NSF) - and the limits are given.

#29

Hi Alessandro, I’m not clear on the effect of an internal Storage. Manny seems to say that with the internal SSD storage, he doesn’t need to rescan the DB after ripping a CD, to see and play it. Are you saying the opposite? I tried to rip a CD on a microSD card in the Rose, but I did have to rescan to see it… So is the SSD storage a solution to avoid rescanning? If so, I’d get one instead of playing my music from my NAS. Many thanks

#30

The answer is no - I have to rescan the SSD and it takes over 7 hours which is ridiculous :man_facepalming:t2::man_facepalming:t2::man_facepalming:t2:

#31

SSD internal storage is not the solution. (not if you have a media library that is 12 TB as I have)

The problem in my opinion is, as I said earlier, that my 150B has not enough processor and memory capacity to scan my media library in a reasonable time. That will never change because it is hardware dependent. They still can do some trimming and change SMB versions, but we will never get acceptable scanning times.

I would be happy if ROSE could clarify why the scanning time is so long if it is not hardware dependant.

1 Like
#32

Maybe shoddy programming?? :man_facepalming:t2::man_facepalming:t2:

#34

Yes, I agree. That’s how Naim Core is doing it :clap:t2::clap:t2:

#36

I have had my 150B for more than 1.5 years and the scanning time have improved marginally. I complained about the scanning time for 1.5 years ago and nothing much has happend so I would not be so confident that ROSE will fix this.

I agree with Flash that if ROSE had some simple knowledge of database structure they would have fixed a incremental scan a long time ago which would have reduced the rescan to minutes instead of 24 hours which is my rescan time. But I think that the problem is a hardware problem in conjuntion with a bad database structure that don’t allow incremental scan.

Once again I would be happy if ROSE would comment on this. Last time they leaved a comment they told me to be patient. After 1.5 year how patient do I have to be. After all this is a product in the high end market (at least regarding to price)

#37

Yes, it needs a rescan and for me (only a bit over 100000 titles on an internal 8TB SSD) it takes 23h with the current firmware.

#38

Hello, we are aware that many people are inquiring about the scanning speed. We are making efforts in various ways to improve it, but due to the limitations and structure of the system, it is not an easy problem to solve. Thank you for your understanding.

#39

Thank you for your reply.

Sadly it doesn’t please me that I was right about the limitations of the system stopping a satisfactory rescan time. The fact is that you (ROSE) will never come around the limitations of the system because it is hardware and database related. So we are stuck with those bad rescanning times.

The way I am solving this problem is by using Folderview when I select music to play and if I want information of artists and albums I use ROON (luckely i have liftetime membership)

#40

I don’t store music on the Rose at all. I’m happy with Roon - and a Rescan of 125000 Tracks takes only minutes (if not seconds) in my Roon Setup. In addition, Roon offers much more information to the music. I had Roon before my Rose 150 came into my setup - its just my Player - and I’m still happy with it.
I can understand people who bought it for just having a standalone player. But hardware is given - and except some optimizations - Rose customers have to live with it.
This is not a good situation, neither for users nor for the reputation of the Brand - because, people these days just talk or write about what’s not so good.

1 Like
#41

I’m not convinced that the hardware is the real limitation (you can also for for example a real old Logitech Touch or older RPIs as LMS server and client with thousands of tracks).
It seems for me more, that (I’m now developing near 40 years hard- and software) there is a limitation in the developer and design resources…

Also I using the Rose primarly as Roon endpoint (otherwise I’d sold it) , but it has to work also as a standalone device (also as backup in the case you’re offline).
Because you can’t use the Rose as gapless UPNP client (no openhome integrated), you’ve to use directly connected sources and so for larger music collections, the search functionallity for which you need a scan, is a must.

#42

I have a Logitech Squeezebox Touch (in my HiFi graveyard). For the Logitech Touch to play from my NAS it has to have a LMS server installed on my PC (the PC is doing the scanning and storing the DB) so that was a bad example of the hardware requirement. Belive me when I say, among other things, it is a hardware limitation .

I fully agree with you that there is a limitation in the developer and design resources or else the problems wouldn’t have excisted.

#43

No, you can use a Logitech Touch (USB HDD connected to it) standalone without any PC and then there runs the LMS and the Touch acts as server and client (in the same way you can configure PicorePlayer on a RPI) and so it’s very good example for showing that also a system with weak hardware can perform much better than Rose do…