Both of the current position when ddj-400. Enter your email address to receive alerts when we have new listings available for pioneer ddj for sale. Pioneer - ddj-400 controls key action shift secondary action s shift press this button down to access secondary actions as described in the shift action column 1 play play-pause loaded track play-stutter loaded track 2 cue set a temporary cue point at current position when track is paused or preview while pressed if cue point is assigned. Is it possible my pages are not defined correctly even though those few buttons seem to be working properly? Is there a tool like MIDI Trace or Chackl's MIDI Definer that would let us submit pages to the controller? HIDTrace does not have this ability.Pioneer will refurbish controllers, such as the pioneer ddj 400, and replace worn-out and damaged components. What suggestions do you have for this? Could all the outputs just be in 1 page? Since my output page is 32 bytes in lenght, I guess it could be possible. LEDs for Decks A/C work fine, but Decks B/D do not lit up at all. I tried the same concept with the LEDs and divided the output in pages same as the input. The buttons & PITCH slider work perfectly in all decks and taking in consideration the DECK CHANGE funcionality. 20 bits to differentiate between the pages for the Decks, bits 0x18 and 0x19 correspond to the PLAY & CUE buttons. ***** OUTPUTS ***** - Deck A - Deck C - Deck B - Deck D I'm using the 1st. ***** INPUTS ***** - Deck A - Deck C - Deck B - Deck D. Bits in GREEN are used by CONSTANT, Bits in RED are the PLAY & CUE buttons.
I'm stuck at the output side just like TechNZ, here is the code for the decks so far. I discovered my device spits out several HID pages, 10 pages from what I was able to notice, so after tweaking with the CONSTANT element I finally got the buttons and sliders working without having them overwrite each other. Input is easier to work out because you can simply press a button, move a knob, etc.
Unfortunately, output may more be difficult to work out for yourself without having the technical specification from the manufacturer available to refer to, especially if it's more complex than simply turning specific bits on/off (This is normally the way most HID devices work, but because S2 HID is intended to be exclusive to Traktor, it may be more complex than this.) You could try defining each output bit in turn and then mapping it to 'blink' to see what effect setting/resetting that bit has on the controller.
I also tried max="0x03FF" with the same results. Is this process correct? What I am missing? I think I'm getting confused with the order in which the bits, bytes and words get read and processed. So in case of the bits in RED bits 0-7 make up the 1st byte, and the other 2 bits on the far right make up bits 8 and 9 so in total there are 10 bits that change with the slider and they seem to be in the right order. From what I can see and understand bits are read right to left (LSb on right, MSb on left) and in the case of multiple bytes, the byte on the left is read first and it then moves to the next byte on the right.
I tried the following 2 lines: Neither line works, VDJ seems to take only in consideration the 1st 8 bits and it keeps disregarding the 2 bits on the second byte because when I move the slider 1 full sweep VDJ actually make 4 sweeps. Ok, the buttons seem to be cooperating so far but the sliders are not. However I'm having a hard time just making it appear in the MAPPERS section, I know the mapper file is good as it works fine with its MIDI counter part and I copy & pasted the VID & PID from the HID Trace tool. Hi guys, I'm trying to write a simple definition file for a HID device.