SC6000 Midi Problem - Constant Sending of Note 90 38 7F or G#3

Engine DJ Hardware Media Players
1

Having a midi problem, hope someone could help please!

I’m attempting to midi map a button on SC6000M but on the midi map page, it is indicating a button is being constantly repeated about every 0.25 seconds. The midi note is G#3 or more specifically: 90 38 7F. It is preventing me from mapping anything as that button / note / signal keeps being pressed and doesn’t allow for anything else to happen.

Has anyone ever had this problem?

Does anyone know what 90 38 7F or G#3 maps to on the SC6000?

As a clue, a search states this:

90 = Note On. 38 = 56 pitch or G#3. 7F = Loudness 127, max velocity.

Any help would be appreciated. TIA!

1 Like
2

I could be wrong

Turn off the motor see if it’s still sending the midi signal

3

I encountered this issue when mapping SC5000M and SC6000M for traktor. I have been told by some denon or serato staff (not sure at this moment), that this is due to Serato requirements. They need constant midi signal from platter in order to track the platter rotation. So this constant midi message sending is on purpose.

1 Like
4

Thanks for the idea but unfortunately the software I’m working with (Djay) does not seem to allow motor off function whether the dedicated hardware button or on the software.

Your thought though has something to do with what another posted on this thread has mentioned. Hoping to sort this out one way or another. I just even want to know if it’s just a problem with my personal unit or if it’s a limitation with the model as they are suggesting.

5

Wow, that is interesting. And unfortunate if true. :sob:

So just to confirm, you never got the SC6000m to midi map because of a constant midi signal being sent? If so, that’s my experience exactly as the midi map function in Djay keeps registering a particular “button” or signal and prevents all other buttons or knobs from being mapped. And when you try to map that signal to perhaps work around it, it crashes the midi map screen.

Regardless, thank you for sharing your experience. Very helpful.

6

Could anyone else please confirm if they ran into this issue as well?

Ot at the very least, confirm if this constant platter-related midi signal is true?

Lastly, does anyone know a way in some backend or hidden setting to turn this off for non-Serato use? Thanks in advance.

7

It is true, as it was confirmed by the developers them selfs. You can midi map the device if you use a midi filter, to filter out unwanted signals.

Check boms midi translator or midi ox.

1 Like
8

Really great info, thank you very much. I really like this deck. Would be amazing if I could midi map it. I’ll update if I can make something work.

9

Do you know of a midi filter for iOS, please?

10

Try midi pipe for mac.

1 Like
11

Thank you, but iPad is my main computer of choice for now. I tried looking for free midi filter apps on iOS and tried a couple but no luck so far. Unsure about shelling out $$$ for any unless someone had a solid recommendation where they have done exactly the same thing. Thanks again.

12

Well, with iOS is a bigger issue than with any other platform in terms of open source programs. So might be expensive and still not working well…

13

Update: After reporting the issue, the Djay devs confirmed the issue was indeed the constant signal as you had said. The great part is they said they are looking into a potential fix. Keeping my fingers crossed. Will update here again if/when it gets fixed.

2 Likes
14

Cool, let’s see what they come up with :slight_smile: