On Fri, Dec 19, 2008 at 6:48 PM, Robin Sheat <[email protected]> wrote:
> On Friday 19 December 2008 20:18:14 Garth Dahlstrom wrote:
> > I also added a fun little hack to the Hercules Mk2 output mapping. The
> > hack triggers the MIDI led command to blink the play button, when
> > "[Channel1/2] playposition" is greater then 0.9 and less then 0.99 -> so
> > the play button blinks for the last 10% of the song
>
> That's awesome :)
>
> I haven't had a chance to look at the new stuff yet, but I'm wondering
> about
> the possibility of centralising things. e.g., most of the herc consoles are
> similar. Could we have a standard set of mappings that are then inherited
> from
> for the specific differences per console?
>
I think trying to do inheritance or sharing will make things too
messy/confusing on a mapping level.
For now, one can copy the mapping file, edit the controller id attribute in
the file, load it into Mixxx and retrain any controls that don't work, and
the manually type over any output LEDs that don't work in the output
bindings tab. The whole process should be less then 10 minutes to make Mk2
-> MP3.
Some of the scripting bits might be reused by doing several levels of config
hash based on the "device" passed in, its going to be ugly to initialize;
something like this I would imagine....
HerculesCommon.device = {
"Hercules DJ Console Mk2": {
leds = {
"play": { 0x08, 0x02 },
"cue": { xxx, yyy }
}
},
"Hercules DJ Console Mk1": {
leds = {
"play": { 0x08, 0x02 },
"cue": { xxx,yyy }
}
}
....
}
....
HerculesCommon.device[device].leds["play"][ch]
__
--- == __/ t.O ==--
http://stacktrace.org/
------------------------------------------------------------------------------
_______________________________________________
Mixxx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
