On Tuesday 29 January 2008 11:14 pm, Garth Dahlstrom wrote: > On Jan 29, 2008 2:00 PM, Ben Wheeler <[EMAIL PROTECTED]> wrote: > > BUT it is similar to BUTTON and SWITCH which I think used > > CCs with the same value, or something like it (I never understood the > > difference between the two). > > (hand up) Oh, Oh, Oh! I know the answer to this one... [I'm the guy who > is responsible for a switch being different from a button.] > > >From http://mixxx.sourceforge.net/wiki/index.php/MidiMapping > > - button - a button has a *Down* (non-zero) and an *Up* (zero) state, > these occur together when pressed/released, this switch only triggers on > the *Down*, *Up* is ignored. (Herc) > - switch - a switch has a *On* (non-zero) and an *Off* (zero) state, > these occur separately. (Herc) > > An example of a switch: > On the front of the Herc Mk2 there is a Headphone monitoring Switch. When > this switch is moved from Deck A to Deck B, you receive an "On" for Deck B > and an "Off" for Deck A. When it is moved from Deck B back to Deck A, you > get an "Off" for Deck B and an "On" for Deck A... So as you can see the > "Off" state is not coupled in the same action as the "On" state. > > Where as with a normal Midi Button, you push the button creating an "On" > and when you release you get an "Off". > > Cheers, > > -G Okay, I understand it. But how can I make my Controller working correctly? =)
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
