Allen & Heath Xone:1D - pitch bend problem

[Blackbrook]

HEllo,

I was mapping my Allen & Heath Xone:1D today and ran into some problems: The pitch bend function does not work via MIDI on both decks. Let me introduce parts of the xml-file:

Code: Select all

            <control>
                <status>0x9f</status>
                <midino>0x16</midino>
                <group>[Channel1]</group>
                <key>rate_temp_up_small</key>
                <options>
                    <normal/>
                </options>
            </control>
            <control>
            <control>
                <status>0x9f</status>
                <midino>0x7e</midino>
                <group>[Channel2]</group>
                <key>rate_temp_up_small</key>
                <options>
                    <normal/>
                </options>
            </control>
            <control>
                <status>0x9f</status>
                <midino>0x13</midino>
                <group>[Channel2]</group>
                <key>rate_temp_down_small</key>
                <options>
                    <normal/>
                </options>
            </control>


Except that the down bend for channel one is missing it is complete. I have sniffed all the needed midi commands as posted in the wiki (start mixxx with parameter '--mididebug') and inserted those commands. Here is a list of the mididebug output wile I have pressed all four buttons (+/- for both channels)

Code: Select all

Debug: [PM 3. Xone MIDI Device MIDI 1]: "MIDI ch 10: opcode: 90, ctrl: 25, val: 7F"
Debug: [PM 3. Xone MIDI Device MIDI 1]: "MIDI ch 10: opcode: 80, ctrl: 25, val: 0"
Debug: [PM 3. Xone MIDI Device MIDI 1]: "MIDI ch 10: opcode: 90, ctrl: 16, val: 7F"
Debug: [PM 3. Xone MIDI Device MIDI 1]: "MIDI ch 10: opcode: 80, ctrl: 16, val: 0"
Debug: [PM 3. Xone MIDI Device MIDI 1]: "MIDI ch 10: opcode: 90, ctrl: 13, val: 7F"
Debug: [PM 3. Xone MIDI Device MIDI 1]: "MIDI ch 10: opcode: 80, ctrl: 13, val: 0"
Debug: [PM 3. Xone MIDI Device MIDI 1]: "MIDI ch 10: opcode: 90, ctrl: 21, val: 7F"
Debug: [PM 3. Xone MIDI Device MIDI 1]: "MIDI ch 10: opcode: 80, ctrl: 21, val: 0"


What makes me weird first is that although the midi channel is stated there as 10 all other commands configured with the midi wizard work on channel 16 and channel 16 is configured in the Xone:1D too (works with this channel on Mixvibes Cross). In the wiki it says that I should enter the opcode in '0x..' but as you can see it is always 90 or 80. So I have had a look at all the different commands (by the wizard) and those carry the numbers shown in the 'ctrl' field.

Anyone got an idea?

Thanks in advance!

Cheers,

Steve

[Pegasus]

Yeah, that is a bit confusing...all of the numbers in the MIDI Debug output are hexadecimal, so 10 in hex is 16 in decimal. (I guess I should change the debug output to show "0x" in front of everything for clarity.) Keep in mind that the debug output shows the MIDI channel starting at 1, while the status byte shows them starting at 0.

So it looks like you need to change the MIDI note number for ch2 rate_temp_up_small (Where did 0x7e come from??) as well as copy the rate_temp_down_small block from CH2 and change it to ch1 and the correct note number for the desired button. Then you should be good to go.

[Blackbrook]

This is what I did now

Code: Select all

            <control>
                <status>0x9f</status>
                <midino>0x25</midino>
                <group>[Channel1]</group>
                <key>rate_temp_down_small</key>
                <options>
                    <normal/>
                </options>
            </control>
            <control>
                <status>0x9f</status>
                <midino>0x16</midino>
                <group>[Channel1]</group>
                <key>rate_temp_up_small</key>
                <options>
                    <normal/>
                </options>
            </control>
            <control>
                <status>0x90</status>
                <midino>0x13</midino>
                <group>[Channel2]</group>
                <key>rate_temp_down_small</key>
                <options>
                    <button/>
                </options>
            </control>
            <control>
                <status>0x9f</status>
                <midino>0x21</midino>
                <group>[Channel2]</group>
                <key>rate_temp_up_small</key>
                <options>
                    <button/>
                </options>
            </control>      

But unfortunately it has absolutely no effect Is there anything that I should change (in the GUI too)?!

Thanks again!

Steve

[Pegasus]

Make sure to reload your mapping file (in Preferences) with each change you make.

[Blackbrook]

I have restarted mixxx every time I have changed something in the mapping file because I do not find any reload or refresh button. I have copied my mapping to /usr/share/mixxx/midi now so that it appears in the drop down list. Nevertheless I get another problem now. The adresses seem to be correct because if I change <options> to 'button' the pitch bend buttons in the GUI light up and stay "marked". So I guess the option is the only thing that is wrong here. Every option in my mapping is 'normal' and in comparison to the play and cue buttons which work that way it should work this way with the pitch bend buttons too. Any ideas?

Cheers,

Steve

[Vythica]

Where did you find a driver for the Xone: 1D? Do you think the same driver would work for a Xone: DX?

[Pegasus]

The adresses seem to be correct because if I change <options> to 'button' the pitch bend buttons in the GUI light up and stay "marked". So I guess the option is the only thing that is wrong here. Every option in my mapping is 'normal' and in comparison to the play and cue buttons which work that way it should work this way with the pitch bend buttons too. Any ideas?

The pitch bend buttons may send different messages than the Play and Cue ones. Run Mixxx with --midiDebug again and see if they send a message on press and release or just press, then check the play and cue buttons. If none of the <option>s work, then you'll need to use a script function to handle lighting those buttons.

(Incidentally, I've just committed a change for 1.9.2 to make the MIDI debug line much clearer.)

[rryan]

Hi Blackbrook,

Is your Xone:1D mapping ready for inclusion in Mixxx? I'm packaging up 1.10 right now and if it's ready I could include it.

Thanks!
RJ Ryan

[llankru]

Hi folks!

I just messaged Blackbrook and he said he uninstalled Mixxx a good while ago and lost his mappings in the process.
If however anyone could give me some pointers how to work the jog and the encoder knobs I'd make a mapping and gladly provide it for inclusion in future versions.

Cheers
llankru

[Pegasus]

Aww, sad to hear that he bailed out... it sounds like he was close!

Take a look at the sticky at the top of this forum. It links to all relevant information on scripting which you'll likely need for the jog wheels. (There's an easy example under Scratching on the MIDI Scripting wiki page that can can be used with likely only minor changes.)