macros:function:triggers.togglemappingenable
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
macros:function:triggers.togglemappingenable [2020/01/26 10:33] – icke_siegen | macros:function:triggers.togglemappingenable [2022/01/25 07:35] (current) – icke_siegen | ||
---|---|---|---|
Line 24: | Line 24: | ||
I found that in a **new show in v11** the factory defined mappings have the titanIds 1815 and 1816, and user-defined macros start with 1817. but this may change as soon as anything else is programmed, and is of limited use. | I found that in a **new show in v11** the factory defined mappings have the titanIds 1815 and 1816, and user-defined macros start with 1817. but this may change as soon as anything else is programmed, and is of limited use. | ||
- | In a **new show in v12** the factory mappings have titanIds 1817 and 1818 and the user-defined macros start thereafter. However v12 has a function to make use of the mapping' | + | In a **new show in v12** the factory mappings have titanIds 1817 and 1818 and the user-defined macros start thereafter. However v12 has a function to make use of the mapping' |
- | In a **new show in v13** the titanIds have changed again and are now in the 1820 range, depending from macros loaded on startup. There is no DJ Tap mapping, MIDI Show Control has user number 1, and user defined | + | In a **new show in v13** the titanIds have changed again and are now in the 1820 range, depending from macros loaded on startup. There is no DJ Tap mapping, MIDI Show Control has user number 1, and user defined |
macros/function/triggers.togglemappingenable.1580034815.txt.gz · Last modified: 2020/01/26 10:33 (external edit)