I have been slow for a long time when it comes to viewing the songs from the playlists that I have on my hard drive with the SC6000.
The hard drive has always been fast for me and I have not had any problems. Until many months ago, it was slow. The word “Searching” appears for about 5-7 seconds. Especially on the deck that is connected via network cable.
Maybe it’s because of the cable? Or because the database is very large? I have many songs because I dedicate myself to events. And I have many styles of music from all eras.
Any solution? Does this happen to anyone else? Thank you!!!
I experience this with my harddrive on my SC5000’s but NOT my Prime Go. Denon keeps telling me it’s my harddrive, however they can’t give me a reason why it doesn’t occur on the Prime Go.
EDIT: 5-7 seconds is lucky! It can take my sc5000’s a couple minutes to load sometimes. And it often occurs multiple times throughout my gigs.
Ah thats bad then, I have that SSD too and around 5500 tracks, I still wouldn’t call yours massive and it definitely shouldn’t be doing that. You raised a support ticket and sent some videos to the Denon team so they can see the issue? I cant suggest anything else really.
15k tracks should be way beneath those 2TB or even 4TB upper limit which were reported to work with the Prime units, at least the ones with integrated SATA bays (400≈500MB/s).
The hard drive has always been fast for me and I have not had any problems. Until many months ago, it was slow.
That leads to some clues. Assuming your collection didn’t make a dramatic jump at that time. Sync or formatting issues? Something with the database conversion? (1.6.2->2.0)? Or the SSD itself, though the T5/T7’s are known to be very reliable and TBW e.o.l. is out of the question.
My only spontaneous idea would be to copy-sync or clone your collection to a different SSD and observe the loading times again.
I rebuild my library almost on a weekly basis. I just did another rebuild today.
Network Linked deck is slow to populate, I have timed it, sometimes it takes up to 3 mins.
If one is DJing from a single source drive, sure no problem as it appears to be at start that the loading is slow… but if you are switching drives, it is a problem.
PS - it also affects Streaming, as the streaming track would not load to deck until the database on the drive is fully available. So one cant even fall back on that whilst waiting.
Hopefully they are working on it.
Sandisk 500gb SSD
30000 tracks.
SC5000M /6000M
Decks are linked directly to each other with a single cable, I have tried CAT5/6, no router/hub.
I’ll check to synchronize everything well, to see if there is something there that is giving problems. If not, I’ll make a new hard drive, with all the playlists from scratch, to see if that works out.
I don’t think the super slow database loading occurred on my system prior to 2.4. It is interesting it doesn’t happen on the Prime Go; not sure if that counts towards process of elimination for what’s causing this issue.
I’ve relayed this issue to a technician multiple times over the past few months and haven’t heard anything back yet.
I have had the same feeling regards the data speed , I did a test using a 35gb image file.
Sent file to ssd drive inside the SC6000 = 35mins (yes thirty five)
Sent file to ssd drive in a USB-3 enclosure connected to my pc usb-3 port = 3.35mins,
Sent file to ssd drive in USB-3 enclosure connected to the SC6000’s USB-3 port = 3.35mins,
Pc is an AMD Ryzen 3600x, 16gb ram, nvme storage drive
Update
It seems some ssd’s do not work well with the SC6000’s, I installed a Integral V Series ssd into my second SC6000 player, the time of sending that 35gb file is now 2.10mins, much better than the Mushkin, I would say that the sata interface inside the SC6000 works fine.
The drives.
Mushkin MKNSSDSR500GB read 560mb/s - write 520mb/s, Integral 1tb V Series read 520mb/s - write 470mb/s, I will try test on a Samsung and Crucial next.
I don’t know if what I’m going to say will help you.
I have done several tests and everything remains the same.
The last test I’ve done is to put an internal hard drive (I have the SC6000). But I don’t have an SSD hard drive, so it can be heard when the hard drive reads.
But the funny thing is that, when the screen of the SC said “searching”, the hard drive did not work, it only worked (heard the noise that hard drives make when reading) when the songs were displayed on the screen.
With what has to be something internal to the machine. Something is causing the “fetch” to take longer than normal.
Once this is done, the speed normalizes. That is, this is done only the first time.
Ok yes it is to do with the drive itself, i have tested a few drives now, on a standard hard drive it is very slow pointless! on an ssd which is dramless you will still have a problem because of sustained transfer rate also too slow, if you use an ssd with good size dram onboard there is very little delay, almost none. I used to update my sc6000 just before i went to sleep as it took too long, now im down to about 20mins for the same 35k size library…night and day!, to add my linked player is near the same speed now.