>
> When you use their own latching mode you can set values for lights that
> are on the inactive page. When you switch to that page, they'll already
> be on. It's a really nice system because it means the host app doesn't
> need to know anything about the latching system.
>
yep, that is quite c
On Sat, 2012-06-02 at 23:31 +0300, zestoi wrote:
> ah yep, this is true. also the k2 is kind of odd that you have to send
> different messages, not just different values, to select alternative
> colours. i'm really not sure why they implemented it that way. i'm
> also planning on getting a k2 soon
>
> >
> > it might also be nice to have a builtin layer system with led recall.
>
> I definitely think this would be useful. I'm working with the Xone K2
> right now and although it has its own latching system there is also a
> mode where the lights and buttons are completely driven by software.
On Sat, 2012-06-02 at 23:01 +0300, zestoi wrote:
> we definitely need them, which is basically part of the modifier
> system we have been discussing:
>
> http://mixxx.org/wiki/doku.php/modifier_system
Thanks for the link. I searched for "shift" and didn't find this.
>
> it might also be nice
we definitely need them, which is basically part of the modifier system we
have been discussing:
http://mixxx.org/wiki/doku.php/modifier_system
so you'd be able to map a control to change or query a modifier from xml,
javascript or the gui.
it might also be nice to have a builtin layer system wi
A lot of midi controllers have a "shift" key, which effectively doubles
the number of buttons by allowing the user to hold the shift button
while pressing another to activate secondary behavior.
Because the controller xml spec doesn't support buttons with
dual-functions, this means a lot of logi