View Single Post
Old 04-26-2015, 11:15 AM   #5
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Nice, all those documents seem very useful!

Reading p. 3-4 of the SLMKII MIDI Programmer’s Reference seems to confirm what you found earlier:
Quote:
Originally Posted by SLMKII MIDI Programmer’s Reference
IMPORTANT: In Automap mode, most of the SLMKII control information is normally handled by a ‘hidden’ USB port – any control information can, however, usually be sent to one of the other normal ports – and still have the same effect. Control Information emanating from the unit in Automap mode, cannot normally be ‘seen’ by host programs; as this is normally transmitted on the hidden port – special steps have to be taken by any application program in order to ‘see’ control changes etc. The Ableton Template is an exception to this, in that the hidden-Port is not used, and control is normally done on Port2.
So, concluding, you want to have the device in 'Automap mode', but communicating (bi-directionally) over a regular USB MIDI port, not a 'hidden' one, much like the Ableton template is doing.

After quickly browsing through that document, it still isn't clear to me exactly what part of the Ableton template SysEx message is responsible for that, though.

I'd suggest to make a custom template .sysex file (with CC numbers, ranges, names etc. - a rough mock-up should do for now), find a somewhat decent SysEx / binary file editor that works on your platform, and start copy/pasting excerpts (e.g. the first 256 bytes) from the Ableton template into it, and try if it starts working (more or less) as intended.
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote