I still have the issue after the update 
Oh noooooo for real? Which issue exactly as there have been a few, specific ones.
This is very vague and I’m sure the Devs would like to fix your issue, and the community would like to advise but you haven’t given us much to go on.
- Which issue, audio glitches on loading, audio glitches when skipping, issues with song browser?
- What device are you using?
- Does your library have album art?
- Have you run a database cleanup after upgrading?
It is very difficult when someone says I still have the issue and doesn’t say which issue or how they are recreating it to know how to help them.
I’ve had issues like the waveform going blank mid track which caused the music stop before v5, but last night was the worst yet, coincidentally right after I updated my sc5000s to 5.0.4. Waveform disappeared at least 5 times, completely stopping the music. Didn’t matter which player either.
Seems like the only fix for these issue is buying Pioneer/AlphaTheta gear because hoping they’ll fix it one day and wasting time and ruining gigs is NOT worth saving money. A better ui is only good if it works, and it’s painfully obvious that it doesn’t.
When I tried CDJ3000X’s once, all networked players crashed on me simultaneously, I don’t think buying AT is gonna save you from that kind of experience…
Very curious what’s causing this, tbh. I’ve been using several Prime devices since 2017 and I have honestly never seen a track losing some of its waveform and its music.
Either must be track specific (encoding, art size, corruption) or a database issue (corruption, tables, hashes, old analysed data, no cleanup done).
I have 4 CDJ-3000x. All networked. I’ve never had any issues with them. Stupid expensive, but they just work.
I would never take those out though. I still use my sc5000 for taking around, but it looks like I will have to figure something else out because I can have this happening at gigs.
There’s loads of people who have had the exact opposite experience, nobody is denying that it happened to you - the exact circumstances to crash either denon or AT players are edge cases (or you’d see constant ruined club nights), and only occur extremely rarely or with specific use patterns / workflows…
It’s been happening for a while now, but not to the level it happened last night. This is the reason I sold two sc5000s and bought 4 CDJ-3000Xs. I routinely delete my databases and rebuild them from my reported xml files when weird stuff starts happening, like playlists disappearing or refusing to import.
I’ll post a video of it happening last night. Give me a few minutes…
similar experience here, I’ve only encountered very rare dropouts (4.2.0 and prior), the waveform warping glitch (> 4.2.0 but < 5.0.0), and the discussed frequent dropouts on 5.0.0-5.0.3. Everything’s been rock solid for me on 5.0.4, both on Prime4+ and the SC6000Ms I got recently 
With all due respect, you NEVER see Denon players at any serious clubs.
I suppose I only perform at unserious venues, then 
Unless you’re bringing your gear to the venue(s), I highly doubt any venues have Denon gear permanently installed.
Let’s stop derailing this thread perhaps. I’m curious about that video you mentioned, if you don’t mind sharing it
I only recorded 3 of the 5 times it happened last night. Here you go: https://youtu.be/_hvLM50m8Vs?is=K0szCsvwxzDLMI2R
Hmm, strange. Never seen anything like that before. Maybe the staff members could extract this into a new thread for the engineers to investigate? I’d wager this is unrelated to any dropout issues
I definitely had dropouts too but they were brief and difficult to document.
It sounds like your player is behaving as if your storage medium’s data transfer rate isn’t fast enough.
This is particularly strange, given that SC players are supposed to load the entire track into memory rather than playing it directly from the storage medium (as CDJs do)—unless that has changed since version 5.x.
Two questions and two tests:
What type of storage medium are you using when this happens? Do you experience the same issue if you downgrade to version 4.3.4?
Does this behavior also occur if you suddenly remove your USB storage device without ejecting it while running version 5.0.4? (This is to verify that full track caching is still working.)
Do you encounter the same problem on different SC players and/or Engine OS devices?
I’ve NEVER had this happen on CDJs with this same drive. I have had this happen on SC5000s prior to v5. I want to say it has happened all the way back to v3 and up.
I used to own 4x SC5000 players, but recently sold 2 and bought CDJs. My girlfriend also owns 2x SC5000 players. with that being said, I’ve experienced the behavior seen in the video on all 6 players we’ve owned.
I will try loading a track and unplugging the drive while it’s playing but I don’t feel I should need to do that. This has been an issue for far too long, and I think the only real solution is replacing them with players I know won’t behave like this. I can’t rely on these tools for work anymore. What good are tools that don’t perform when you need them to, especially when you’re being paid?
Due to the vagueness and other factors, its difficult to believe that one particular person on this thread has or had 4,3,2 or even 1 Prime model