I was looking for a way to set a specific BPM speed to the a chase in one keypress.
I'm aware I can record a macro to do that but, unless there's a valid succession of keypresses I didn't find, the resulting macro will be related to the handle on which the chase is recorded and, thus, moving the chase will render my shortcut useless.
So I had a look at the macro xml file and, using the existing Xfade macros as a starting point, I wrote this :
Code: Select all
<macro name="Chase BPM 0" id="Avolites.Macros.BPM0">
<description>Set the speed of the connected chase to 0 BPM.</description>
Code: Select all
<macro name="Chase BPM 60" id="Avolites.Macros.BPM60">
<description>Set the speed of the connected chase to 60 BPM.</description>
<step pause="0.01">Chases.IncrementWheelParameter(0, 0.24)</step>
Using the same logic, I made a few other macro (BPM 120, 240, BPM add/remove 10, add/remove 25...), paying attention to maintain the xml structure and give them distinctive macro name / id, without fancy characters.
I modified the xml file and tested it in my Titan sim. The new macros are available in the show library and everything seems to work as expected.
But I'm no specialist, so before using that custom file in my desks and sharing it with other users, I'd rather be sure :
Can you please confirm that I made no mistake and that, while I'll use this at my own risks, I guess, this should be fine ?
I also have a few other questions :
- In the brackets (0, -14.4), the '0' refers to to wheel that will be modified by the value '-14.4'. '0' stands for the first wheel, '1' would be the third. Were there be a parameter assigned to the second/middle wheel, should we use '2' ? Just curious...
- Regarding BPM macros, a 'double speed' and 'half the speed' would be very handy. One cannot use the above method to achieve this, however, as the +- value can't be replaced by an operation (i.e. ' *2 ').
Is there another way of achieving this ?
- Of course, custom macros are far more easier and safer to build using the record macro function in the software. However, at the moment we cannot use this for everything, as some specific actions aren't recorded - wheel and fader movement, for example. Factory provided macros show that there are some workarounds but, while the 'macro name and id/description/sequence/step/step...' structure is quite simple to grasp, we obviously miss more information about the xml elements we could use. Is there any chance this could be at least partially documented at some point ? Maybe in the 'Titan Tips and Tricks' section of this forum ?