View Single Post
Old 11-20-2009, 11:44 AM   #75
indys
Human being with feelings
 
indys's Avatar
 
Join Date: Aug 2009
Location: AC, Sweden
Posts: 49
Default HUI

Maybe the best approach is to make an application that receives all the bells and whistles from c24 and then map it to midi in a user configurable way. In that way the compatibility won't be an issue. In cubase it is possible to map almost any event to midi (even tracknames and window openings) via the generic remote functionality and if the c24 converter uses a virtual midiport it should be doable. In that case all you have to do is to do the mapping for each host one time and then release the mapping-file public domain.

If the mapper also supports sysex the number of buttons and lights and functions is irrelevant as the message size is almost only limited by f0-f7. (Some buffer overflows can be seen if you take it to extreme ;-))

The question is how much functionality the converter needs to have: blinking lights, converting faderposition to db value for its display and so on... maybe that should be configurable to...

Yes, I have read the Logic control manual and implemented its HUI spec in a track display application. I think they was publishing most of hui specification in that manual not knowing that the protocol was kind of a secret :-)

/Indys
indys is offline   Reply With Quote