![]() Other banks that are “on” have solid blue lights banks that are “off” have orange. The other three knobs (1-3 from left to right) control various parameters as follows:Īll knobs are coded for soft takeover because tParameter() does not currently support the default soft takeover behavior. The right-most knob on each side is mapped to Quick Filter. Pressing a button selects that bank as “active” holding the button functions as “FX Shift” (“FXS”), which has two uses:įXS+BrowseL/R changes the assigned effect chain in the selected bank.įXS+Knob changes knob behavior (see below).įX Assign 1 turns the active bank on/off for the current channel.įX Assign 2 can be used to turn the other banks on/off for the current channel by holding Assign 2 and pressing the bank select button (useful if you just want to turn a given bank on/off without changing the bank you are actively controlling) The four effect buttons are used to select an “active” bank the knobs and assign buttons then control the active bank. All four effect banks can be assigned to any of the four decks. Both sides (left and right) call the same functions, giving you direct control over any two of the four effect banks at any given time. I completely rewrote the effect handling because I wanted direct control over the parameters. I hope this is helpful for others – many many thanks to Craig for the original script, I just wanted something more specific to the way I mix. I have tested the script thoroughly with the Late Night skin but I don’t know how it will work with other skins. I have listed only the changed functionality below. Here are my modifications to the original script. (See the Wiki page for the full documentation). I think this is an innovation in this mapping that may not be available on other controllers (or skins) at the moment). Not having to repeatedly toggle slip-mode on/off to re-sync playback after looping in slip-mode is a real benefit. (You really need to play with this to appreciate how cool the effect can be and how it opens up new looping possibilities. This auto-loop/slip-mode interaction (together with the auto-loop on hold behaviour) is far better than the behaviour of the “LateNight” skin (which is unaware of slip-mode in general), as it allows for some very nice looping effects while keeping the underlying beat of the track intact. In slip-mode, the auto-loop buttons will “re-sync” playback when released by turning slip-mode off and then immediately re-applying slip-mode (you may see the slip-mode button flash briefly when this happens). There is no GUI control for slip-mode in the “LateNight” skin, but this mapping already has it selectable on each deck via “FX Control” button 1 (the button lights up blue when slip-mode is active). You can also adjust the loop size while an auto-loop is “locked” by pressing a different auto-loop button then locking that with the LOOP ON/OFF button once again.Īuto-loops are particularly useful with slip-mode active. Unlike the “LateNight” skin, the controller auto-loop buttons are only active when held (which is generally what you want with short auto-loops), but you can “lock” them (so you don’ have to hold the button, perhaps only useful for the longer auto-loops), by tapping the LOOP ON/OFF button once you have pressed auto-loop button you want. Second row hot-cue buttons 5-8 = auto-loops to Top row hot-cue buttons 1-4 = auto-loops to They are laid out in the same manner as in that skin, i.e.: tap the DEL button to light it up, not holding it), the hot-cue buttons can now be used to activate the 8 “auto-loops” that are present in the “LateNight” skin (and possibly others). If you hold one of the 4 FX-Assign buttons down, you can now change the effect in that effect-unit by using the “Browse” left/right buttons. ![]() This eliminates accidental hot-cue deletions when in DEL-mode (which is used for a number of other functions). ![]() To clear a hot-cue, you now have to hold the DEL button down while pressing the hot-cue button. More file clean-up as a result of the pull-request.Ĭhange in the DEL button behaviour. I’ve updated the mapping files in the original post (to V1.4), and edited the original post above again to reflect the new changes which are: ![]()
0 Comments
Leave a Reply. |