User Tools

Site Tools


updating_controller_mappings

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
updating_controller_mappings [2017/01/20 15:15]
be.ing [Mixxx 2.1]
updating_controller_mappings [2019/08/11 12:10]
be.ing
Line 1: Line 1:
 This page has information for updating old controller mappings for the latest version of Mixxx. This page has information for updating old controller mappings for the latest version of Mixxx.
 +
 +====== Mixxx 2.3 ======
 +Support for [[MIDI scripting#​color API|colored hotcues]] was added.
 +
 +====== Mixxx 2.2 ======
 +There were no changes to the controller mapping system between Mixxx 2.1 and Mixxx 2.2.
  
 ====== Mixxx 2.1 ====== ====== Mixxx 2.1 ======
   * ''​engine.setParameter()''​ now works with ''​engine.softTakeover()''​. If your script implemented its own soft takeover mechanism to get around that bug, change it to use Mixxx'​s soft takeover solution instead.   * ''​engine.setParameter()''​ now works with ''​engine.softTakeover()''​. If your script implemented its own soft takeover mechanism to get around that bug, change it to use Mixxx'​s soft takeover solution instead.
   * MIDI input handling functions are now called with the appropriate ''​this''​ object (instead of ''​this''​ being set to the global object), allowing script files to be written with a more object oriented organization.   * MIDI input handling functions are now called with the appropriate ''​this''​ object (instead of ''​this''​ being set to the global object), allowing script files to be written with a more object oriented organization.
-  * ''<​key>''​ elements in XML that are bound to script functions can now be any JavaScript expression that evaluates to a function in the global context +  ​* Metaknobs, which act like superknobs for each effect within a chain, were introduced. Also, a new framework for focusing individual effects within a chain was introduced. Focusing an effect does not do anything by itself; it is up to controller mappings to do something different depending on the focused effect. The show_focus ControlObject of an EffectUnit needs to be set to 1 for the focus to be shown in skins. Refer to [[Mixxxcontrols#​Effects framework]] for details. 
-  * TODO: document new effects interface+  * [[Components JS]] library was introduced to make writing JavaScript mappings easier. It provides an [[Components JS#​EffectUnit]] object that makes it easy to map the new effects interface to the common layout of 4 knobs (or 3 knobs + 1 encoder) + 4 buttons for controlling effects 
 +  * New [[MixxxControls]] for looping and beatjumping were introduced. If your mapping has buttons mapped to fixed loop sizes, update it to use beatloop_activate and beatlooproll_activate. Replace reloop_exit with reloop_toggle,​ and add a mapping for the new reloop_andstop Control. Replace loop_move_X_forward/​backward with beatjumping,​ which now acts to move the loop if there is a loop enabled. 
 +  * TODO: document new library navigation interface 
 +  * A new [ChannelX], track_loaded ControlObject was added. If your script previously used track_samples to detect if a track was loaded, switch to the more readable track_loaded. 
 +  ​* ''<​key>''​ elements in XML that are bound to script functions can now be any JavaScript expression that evaluates to a function in the global context. Just because you can embed a JavaScript function in the XML file does not mean you should though.
  
 ====== Mixxx 2.0 ====== ====== Mixxx 2.0 ======
updating_controller_mappings.txt · Last modified: 2019/08/11 13:10 by be.ing