U46DJ not compatible with Novation Dicer

[superdj4life]

But some functions are not too difficult to implement. If you know the interfaces and also the commands it is not difficult.

that's the problem I know the novation side, well sort of, but i don't get what i should be doing to the .ini files for mixvibes

**FROM THE NOVATION PROGRAMMERS REF**

Set LEDs
Hex version 9A-9Fh, Key, Velocity.
Decimal version 154-159, Key, Velocity.

A note-on message changes the state of a LED. Key is the MIDI note number, which determines the LED location. Velocity is used to set the LED colour

Velocity is determined by choosing a number according to the colour of the button:

Value Meaning
00h (0) Red
10h (16) Red-orange
20h (32) Orange
30h (48) Orange-amber
40h (64) Amber
50h (80) Yellow
60h (96) Yellow-green
70h (112) Green

To this number, a LED intensity from 0 to 15 (Fh) can be added, where 0 is off and 15 is maximum
brightness. Dicer will light the button accordingly.

***END***


what i don't get is how to turn that into something the MV .ini file understands as "turn this dice this color"

[christiankoopmann]

Hey,

you can test like this:
#msg data1 data2 COMMAND
MIDI Note Func. Player data1 data2 COMMAND
#90 00 9a Loop 1 1 16
#90 00 9b Loop 1 0 16

The MIDI note is not correct but the rest could work. I set this for my Numark for setting the Pitch Range.

No guarantee that it is working for the Dicer but this is how I would map it.

regards
Christian

[Hannes]

But some functions are not too difficult to implement. If you know the interfaces and also the commands it is not difficult.

I never said that

[superdj4life]

you can test like this:
#msg data1 data2 COMMAND
MIDI Note Func. Player data1 data2 COMMAND
#90 00 9a Loop 1 1 16
#90 00 9b Loop 1 0 16

do i need to add the %output flag at the beginning so the button presses aren't received as inputs?

i.e
%output

(button) (function) (data1) (data2) COMMAND
#9b 3e 7f LOOP 1 1 16

Set LEDs
Hex version 9A-9Fh, Key, Velocity.
Decimal version 154-159, Key, Velocity.

A note-on message changes the state of a LED. Key is the MIDI note number, which determines the LED location. Velocity is used to set the LED colour.

Knowing this which field is MV using for key? data1 or data2? also what field would COMMAND correlate to? If i can figure that out this problem is solved!

thanks in advance

[christiankoopmann]

Hey,

yes the output commands comes after the %output.

#9b 3e 7f LOOP 1 1 16

this would be a light on function for Loop on deck 1. The commands are setted up (syntax):
(MIDI note) (function) (deck 1,2,3,4) (Data 1 = light on/off 1/0) (Data 2 = MIDI message)

This should be the config for that. So if you want to map a light to a button you need 2 lines one where you enable it and one where you disable it.

Code: Select all

#9b 3e 7f    LOOP           1          1         16
#9b 3e 7f    LOOP           1          0         16


I don't know if this is absolutly correct because I'm only a customer too but I mapped three controllers with led Output and there it worked for me.

regards
Christian

[superdj4life]

thanks. the code seems to work with the exception of the of the color at the end. i can get any light to turn on....as long as it's green.

[christiankoopmann]

thanks. the code seems to work with the exception of the of the color at the end.

No problem. OK that it is green says that the data 2 not work correctly. Maybe the support or one of the dev team could answer that question.

regards
Christian

[Hannes]

Hi,

maybe that´ll help you out. it´s quite detailed.
http://www.djtechtools.com/2010/09/02/how_to_map_dicer-led-midi-mapping/

regards
J