Most of these controls behave as expected but they are listed in detail for the sake of completeness anyways. The current assignment will then be shown for one second in the upper row.Ĭurrently up to 4 Pages are supported (with 4 hotcues each). They can be changed by using the corresponding Encoder. The four lower buttons of the topContainer are hotcues. If the Button was pressed for a shorter period than 275ms, the button will remain in that state until it is pressed again (like a toggling button). Original state (like a regular shift-/pushbutton).
This means that if the shiftbutton is pressed for a longer period than 275ms it will bounce back to its Toggle switches instead of pushbuttons (enabled via components.js ). Moreover the shiftbuttons can also work as Shift Ī shift button is bound to its Deck, which means that you can’t use the shift button of Deck1 to access a shifted function on any of the other three Decks. Hey Crossers, Ive read the Cross MIDI output mapping topic 3 times before trying to map but cant get it to work so where does it go wrong Ive tried a few different things but the outcome is the same. The mapping features some peculiar features which might not be discoverable by standard trial-and-error. The Deck consists of the jogwheel, play, cue, the topContainer (which hold the eight square buttons and the four encoders), pitchslider, pitchrange, search, keylock, tap, sync and pitchbend ±.
