Numark DJ2GO Scripting

[z3r0]

wow rage much ...jk i do understand though and i might just leave those buttons not used at this rate and if someone could make a .bat or.run so i can load the midi debug that would be great

[Pegasus]

To get the MIDI debug output, run Mixxx from a command prompt with the --midiDebug option and it will print out all of the MIDI messages as it receieves them (and put them into mixxx.log which you can monitor.) If it still doesn't, then you need to rebuild Mixxx with the debug=1 flag.

http://mixxx.org/wiki/doku.php/midi_con ... controller

[z3r0]

Sniffing your controller

First, try using the MIDI Learn functionality in the Preferences→MIDI Devices window at the bottom (in Mixxx 1.7.0 and higher.) It will help you get many of the essential functions mapped quickly without having to do any hacking.

If you don't have the MIDI spec for your controller, first check the manufacturer's web site under Support. Look for Manuals or User Guides. MIDI specs are usually given in an appendix at the back of the manual. Failing that, you can usually sniff the MIDI data the controller sends with the following procedure:

Start Mixxx (1.8.0 and later) from a command prompt using the –midiDebug option like so:
Linux:

user@machine:~$ mixxx --midiDebug

Windows: (v1.7.0 and later)

C:\Program Files\Mixxx>mixxx --midiDebug

Mac OSX:

$ open -a mixxx --args --midiDebug

Look at the output
Watch the console output or look at the Mixxx.log file which will contain all of the MIDI messages Mixxx receives. As you manipulate the controller, the MIDI commands it sends will be printed to the screen/logged to the file. Compare the status (first) byte in each line with the table above and note which button/slider/control sends what message.
For example, when you move a slider, you might see

Debug: [...]: "MIDI ch 1: opcode: B0, ctrl: 2, val: 3D"
Debug: [...]: "MIDI ch 1: opcode: B0, ctrl: 2, val: 3A"
Debug: [...]: "MIDI ch 1: opcode: B0, ctrl: 2, val: 3D"
Debug: [...]: "MIDI ch 1: opcode: B0, ctrl: 2, val: 3B"
Debug: [...]: "MIDI ch 1: opcode: B0, ctrl: 2, val: 3C"

In this instance, it's sending 0xB0 (which when we look at the table above, we see that it's a Control Change message on channel 1) We also see that the second byte, 0x02 in this case, is the control number that was moved, and the third is the value or position of that control, which you can ignore for the purposes of mapping.
Add the byte values to a <control> block in the XML file
Just plug the first two bytes into a <control> XML block for <status> and <midino> respectively. This is detailed in the next section.

Sniffing your controller

First, try using the MIDI Learn functionality in the Preferences→MIDI Devices window at the bottom (in Mixxx 1.7.0 and higher.) It will help you get many of the essential functions mapped quickly without having to do any hacking.

If you don't have the MIDI spec for your controller, first check the manufacturer's web site under Support. Look for Manuals or User Guides. MIDI specs are usually given in an appendix at the back of the manual. Failing that, you can usually sniff the MIDI data the controller sends with the following procedure:

Start Mixxx (1.8.0 and later) from a command prompt using the –midiDebug option like so:
Linux:

user@machine:~$ mixxx --midiDebug

Windows: (v1.7.0 and later)

C:\Program Files\Mixxx>mixxx --midiDebug ---------- will not work

Mac OSX:

$ open -a mixxx --args --midiDebug

Look at the output ------- what outputwill not load from console
Watch the console output or look at the Mixxx.log file which will contain all of the MIDI messages Mixxx receives. As you manipulate the controller, the MIDI commands it sends will be printed to the screen/logged to the file. Compare the status (first) byte in each line with the table above and note which button/slider/control sends what message.
For example, when you move a slider, you might see

Debug: [...]: "MIDI ch 1: opcode: B0, ctrl: 2, val: 3D"
Debug: [...]: "MIDI ch 1: opcode: B0, ctrl: 2, val: 3A"
Debug: [...]: "MIDI ch 1: opcode: B0, ctrl: 2, val: 3D"
Debug: [...]: "MIDI ch 1: opcode: B0, ctrl: 2, val: 3B"
Debug: [...]: "MIDI ch 1: opcode: B0, ctrl: 2, val: 3C"

In this instance, it's sending 0xB0 (which when we look at the table above, we see that it's a Control Change message on channel 1) We also see that the second byte, 0x02 in this case, is the control number that was moved, and the third is the value or position of that control, which you can ignore for the purposes of mapping.
Add the byte values to a <control> block in the XML file
Just plug the first two bytes into a <control> XML block for <status> and <midino> respectively. This is detailed in the next section.

[z3r0]

↑ the error i keep geting
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.

[likkyla]

I will attempt this when I get home. I will also try to sniff it out with Tail.

[Pegasus]

z3r0: Okay, the command you enter is just

Code: Select all

mixxx --midiDebug

the stuff before the '>' is the command prompt Windows presents, do not enter that too.

You must be in the Mixxx program directory for it to work. So do the following:

• Right-click the Mixxx icon, then click properties or Shortcut properties
• Click the Shortcut tab, then select all of the text in the Start In box (should be something like C:\Program Files\Mixxx\)
• Press CTRL-C to copy it
• Start the Windows command prompt (Click Start->Run, then type cmd and click OK)
• Type cd " but don't press enter.
• Right click the title bar and choose Edit->Paste.
• Add a close quote, so the final command should look like
  

  Code: Select all

  cd "C:\Program Files\Mixxx"

  Now press Enter. This puts you in the correct directory.
• Type

  Code: Select all

  mixxx --midiDebug

  and press Enter

[z3r0]

I'll try that after I get some sleep 5:34AM need sleep

Again on iPod

Also this seems to be like a holiday sig for now but.

Sleep all day party(or development) all night

[z3r0]

tried it but no output on the console

[Pegasus]

Right. On Windows you'll need to look at mixxx.log in your user profile directory. http://mixxx.org/wiki/doku.php/troubles ... xxlog_file

[z3r0]

well useing the log i still could not find the values