JSM, the transmit speed of the SC2000 hardware is always constant in Cue or Play modes. In fact it doesn’t know the difference between Cue and Play.
It’s interesting that you find it a tad slower in Play.
The question is, what does tad equal to in milliseconds?
What is your latency set to?
If you make it shorter, does it help?
I kinda guessed that, afterall it doesn’t care which button is mapped. So i am thinking that the problem** … is with the mapping or something in the 1.2.7 update
**(i hate to call it a problem, after all I owned a VMS4 for a few months and that was a major problem 
so much so even after a replacement unit the thing would turn itself off in the middle of a set ) … .
As for latency, the only latency i can adjust is for the Audio 8, which is currently at 4ms @48khz, this is made up from 1ms USB and 4ms Audio and I use the latest drivers, it’s just the same with the other drivers. I can’t drop this any lower, if i do i can’t use 4 decks and effects without audio drops.
I was unaware that you could adjust the latency of a USB controller via software, could you direct me to the utility to do this, it sounds ideal?
And going back to your statement about HID not being quicker than MIDI, are you sure you have this right? To transmit MIDI over USB a Cable Number and Cable Index are added to the message, and the result is encapsulated in a USB packet. The resulting USB message can be double the size of the native MIDI message. Since USB is over 15,000 times faster than MIDI (480,000 Kbits/sec vs 31.25 Kbits/sec,) USB has the potential to be much faster. However, due to the nature of USB there is more latency and jitter introduced that is usually in the range of 2 to 10ms, or about 2 to 10 MIDI commands. Some comparisons done in the early part of the 2000s showed USB to slightly slower with higher latency, and this is still the case today. An interesting and very detailed article can be found here ..
whereas HID constantly watches for a state change, surely making it quicker and far more accurate (hi res jogs for example).
This could be an interesting new thread … “Is HID faster than MIDI”
I have to apologise, it’s not an issue with the controller, i found that when quantise is activated the response is slow (you’ve seen the video), when it’s off it’s as fast as anything i’ve connected to it.
Now i can bash buttons all night long and not have to worry about the response time.
So the “issue” is over to NI for investigation.
I love this controller …
I think im gonna get one. Or two…
LOL…yeah…quantise will make you be in phrase regardless whether you push the button late or early.
I was fiddling around with this this weekend and also now understand exactly how it works!
Its sick actually!
But even sicker that you can turn it off and do you own thing.
Get 2…I wish I had
ETA for mine is ~4PM today XD
Lol fine two it is!
I’m also considering one or two of these in the future, but by time i can afford them there will probably be other options.
JSM, thanks for the follow up, this is good info to know.
Does that 4 Deck .tsi mapping work for just one controller? Or was it meant for 2?
Yes, for 2 units.
You just need to change the MIDI CH on the 2nd unit to 3/4.
Push [shift]+[cue2], thats it.
actually when doing a “juggle” routine you need the quantise and the snap on, keeping things in time. The problem it seems is that the quantise is only operating at 1/4 rather than 1/16 or 1/32 … i saw it being requested as a feature on the NI website. Perhaps build 1.2.7 is a little stricter than the previous builds as i didn’t notice it with the nanopad and 1.2.6
Anyway, i can still do the routines, i just have to remember to hit “sync” after the last juggle … or the things runs out of time very quickly.:eek:
If you are “sample dropping”, then it’s fine to leave the snap & quant on, as you wouldn’t normally try to create a “machine gun”/“drum roll” effect.
I hope that when NI finally gives us a sample bank for TSP, they increase the quantise to 1/32
Thanks a lot, LEDs works perfect with your modified tsi.
Regards
can anyone explain how to get the FX Knob Rings to light up while using Traktor…
Tryed figuring it out from the TSIs I got here but nothing lists as having a specific “Output” for the effect paramiers like Dry Wet Advanced (and the like.
I modified the TSI and stripped it of it FX mapping so I can do my own…but I cant for the life of me figure out how to light up the LED rings on the controller
There is a midi map of all available LED possibilities in the “manual” or maybe the quick start guide, can’t remember which.
Ummm Yeah and its completely impossible to apply to Traktor…
WTF is 0x3C (taken from the MANUAL) suppose to mean exactly?
Can someone shed some light beyond “hey look at the manual”
The manual would have been the first place I looked…
Channel 0 midi note 3c im guessing
There is no channel 0 …
I’m going to go ahead and say that I’ve never read a Denon manual for anything, that I don’t own an SC2000 (but I’m looking into it), and that I haven’t mapped things like that.
But, I’m guessing that Denon assumed that anyone who wanted to do those types of things knew something about computers.
0x3C means (hexadecimal)3C, which translates to 60 in the decimal numbers you’re used to. (this convention of 0x meaning ‘hexadecimal’ is universal in the computer world)
Assuming that it’s giving you a note value for the light, that statement in the manual means that it’s talking about midi note C3 (as in note C-natural in octave 3…the reversal of digits is a coincidence) controlling that parameter. The channel is the channel that the controller is on (probably 1 or 2 depending on layer, but that could be different), and the rest of the message has to do with how the controller decides to do the lights.
Chances are the signal 0x90C37F sent on the correct channel would turn the light all the way on and that 0x90C33F would turn it halfway on…but now I’m in the realm of speculation and I’m probably wrong about some details…but the answer to your question is actually in here.
BTW, when I started writing this post, I knew nothing specific except that 0x… meant hexadecimal. That was about 6 minutes ago. Google is a wonderful thing.
on a wireless controller i have there is