ML0 to ML9 where ML0 is just the normal non-shifted mapping.
This allows you to have up to 10 MIDI layers on the same controller Shift logic selector allows you to use 2 buttons using increment and decrement to change which Modshiftlogic you want to use. You can map individual buttons to set on or off a particular shift logic. You can have up to 9 Modshiftlogic commands available. Everything that I done has been by reading the MIDI mapping topic here and by experimenting. To be clear I never had or currently have a mapping xml spec sheet.
#Resolume 5 where is midi map located .xml trial
Not even 1 of the official mappings uses this, and no info is available, so how is anyone supposed to use this? (to be honest, after a lot of trial and error I'm beginning to see first results which I will post in the other thread soon). The past days I've been trying to find any info on using the ShiftSelector functionality. Now this is a daunting task, but with the specs that really doesn't need to be. The complete specs of the mappings xml file format should be available so people (not only FigDJ!) can create mappings. This could really help Mixvibes in to getting actual added value for their product by their own users. I would be happy to start writing such a document myself by reverse engineering and getting help from both Mixvibes support and experienced community members (FigDj comes to mind.).Ĭan we expect any improvement in this department for Cross 4? What I'm looking for is a complete specification of the mappings xml file with all possible valid elements and their attributes. I consider myself pretty technically inclined, but find the process of reverse engineering existing mappings just to get some examples mind boggling.
I know what message each control sends and what it can accept to turn leds to a specific color).Ĭross has a simple MIDI learning module, but has nothing to support output mappings. I'm not talking about the controller specs these are well defined and available (i.e. I'm in the process of trying to create a complete MIDI mapping (both input and output) for a controller and I find the lack of documentation striking.