There are at least two issues.
One definitely seems to have to do with layers, sync, and cues and is pretty subtle. According to the videos, it appears to affect both the non-M and the M.
The other speed issue is where the M’s motor changes speed suddenly and doesn’t reset until you put the pitch fader at zero. The screen doesn’t change and the record speed detection still functions properly. This is not subtle when it happens and has nothing to do with sync.
That’s no joke. I had the same thought with all of Gemini’s problems on the MDJ.
Hi @JWiLL, thanks for replying!
Yes, i can reproduce the error on my 5000 non-M. Few observations:
Personal thought:
The player is setting the tempo of the loaded track to the master clock when you press play. So not on load (like Traktor does). This causes an (unnecessary) peak in CPU load, because the player has to do several things at the same time (play, tempo sync, beatmatch, keylock). High quality audio files (AIFF) demand a lot of the system already. So maybe syncing the tempo clock on load will provide you with and option to better distribute that load. It also means the player will not have to beatsync (cause it already aligns the track on 1 on load), which is 1 task less to compute.
This does not completely fix the strange behavior of course. It is strange the master layer is accepting tempo changes from other sources.
All great info - much appreciated! A couple of follow up questions:
Are you able to reproduce the issue with mp3 or Wav files?
Do you have solid repro steps or does it happen randomly?
There appear to be solid reproduction steps for the first, subtle issue related to cues, layer, and sync that affects both players.
My initial hunch on the not-subtle M motor speed thing is that it may be related to heat but prior to the fans turning on, but that’s obviously hard to test. I was sort of cooking my Mackie mixer with it right up against the Ms to get it to happen. It could also be related to layers, since from my own videos it happens after I have previously used the other layer, even if it’s not playing on the background layer. So maybe a soft takeover source of it is another possibility.
Well, the video was made spontaneously and about 1 minute after Reticuli asked for a video. And this was the second try, cause i filmed it the wrong way the first time (also happened though). So quite a solid repro, i think.
I could try to redo it with mp3’s and WAV’s. I have those. But i currently am not able to and very busy, so lets see if you can reproduce it with AIFF’s at the office first. 
Also: i am on firmware 1.2.0. Firmware 1.2.2. is bugged for AIFF playback, as you can read (and is reproduced very solidly) in this thread: 1.2.2: electrical interference noise when loading new tracks
Not in the mood to upgrade to 1.2.2. again to test if that firmware still has the issue. It probably has, because all previous versions have it. Plus i’ll have to downgrade again, and am busy enough as it is.
What are your pitch fader range settings? When that happened to you did you notice a change in the pitch range on any of your layers?
Default settings on pitch range. Not touching the pitch range fader when playing with sync.
So I’ve been in touch with InMusicBrands who are Denon DJ’s parent company. Here is part of their response…
"The issue is starting to look like there is a hardware fault with the unit and in that instances it may be best for you to return the unit back to the place of purchase to organise a warranty return.
I will be showing the videos and link you have sent over so far to my collegues for further investigating and we hope to get the bottom of this issue as soon as possible.
Thank you so much for your detailed reponse and continued support in our products. "
I would take that with a grain of salt. Most of the issues I see look like they can be fixed by filtering or by the mapping away of it in the software.
Let’s just say that if the platter is supposed to only control the layer that you are on then how come it seems like it’s dictating to both? The solution would be is to ensure that the other layer/deck ignores the platter, right? But we’re using sync so now the software has to take into account both layers/decks, it can no longer ignore some things. And there is where the rabbit hole lays.
Hardware issues are noticeable on the face, when you see them you will know.
Software issues are dictation problems.
Too bad I can’t connect this to my computer as controller yet. I could see a lot of things, probably do a lot of things too.
I tend to agree that it looks like its a software issue but by going for the swap out, I can hopefully eliminate faulty hardware as the cause. If the artefacts present again, then either Denon have a faulty batch of SC5000M’s floating about or it’s gotta be a software issue.
Unfortunately, what I’ve experienced is not easy to recreate reliably and document.
Once I have the new unit, I’ll spend a couple of hours mixing with it to see how it behaves and let you all know how I get on.
Doubtful. I would ask for a specific explaination of the hardware fault and how they’ve determined this before sending units back. Sounds like just throwing spaghetti at the wall and hoping something sticks, or at least get people to stop posting so much while their units are in-transit. There are too many having the subtle speed problem. The reason I’m not experiencing it is probably due to not using sync.
I never noticed either till I started using the sync.
I preped a drive that I’ll be using for giging on the M. The crate for the drive was made with the Traktor import feature in engine prime.
I found issues with sync usually if when I load a track for the first time and has been analyzed by the deck. (this would fall in the hard to repeat category since the deck analyzes the track once so must use a fresh track every time to repeat).
I also find that it’s better to set you pitchfader range to +/- 20% for the sync to work more properly.
Other than sync the deck works as expected.
So, I swapped over my player today. Got a brand new unit, no quibbles. Got it home. Set it up and had the damn thing speed up when dropping in a tune using hot cue 1 within about 5 mins of turning it on!
Hey Everyone,
Thanks to your help, we’ve been able to reproduce the playback speed fluctuations. We are working towards a solution now and will provide update as soon as the root cause has been identified, addressed and fully tested. Again to confirm, all speed fluctuations are firmware and not hardware related so, a forthcoming update will resolve this.
Note: We have not been able to reproduce the momentary fluctuations with sync turned off. Just putting this out there in case you need an immediate workaround.
Thank you for all of the helpful details and our apologies for the troubles.
I’ll let you know once the fix is available.
I assume you’re talking only about the subtle fluctuations that have to do with sync you’ve been able to reproduce. Have you yet been able to reproduce the M motor speed change that requires you to return to zero pitch? Vince said you hadn’t been able to previously. This is a more catastrophic issue and predates this subtle variety you appear to be talking about that occurs only with sync.
Thank you very much sir
Yes, we’ve reproduced both.
There is a fluctuation with sync that affects both SC5000 and SC5000M.
And there is a separate issue (as in your video) specific to the SC5000M motor that we have also reproduced.
Both are under investigation/development now.
Both will be addressed with firmware.
Awesome. Lets fix this!
Good news, thanks.