Hello, thank you for your feedback!
To elaborate a bit on the point 2 - the best way to work with slot-based parameters is making a custom Max for Live device including:
- a [live.menu] populated with slots of the function of the specific fixture you are working with
- mapping the slot index values to the corresponding DMX values (as specified in the fixture’s manual), using an object like [coll] or [zl.lookup]
- scaling this to a range between 0. and 1. by dividing the incoming values by 255.
- prepending the incoming values with the corresponding modulation keyword (e.g. slot), as specified in the Beam fixture profile
Here is an example of this, based on the Monoprice LED bar in the 2 channel mode: Monoprice 612601 LED Bar - 2ch.amxd (251.4 KB), along with the corresponding fixture profile: Monoprice 612601 LED Bar - 2ch.sbf (472 Bytes).
While we would like to also provide a more generic out-of-the-box tool for working with slot-based parameters, the approach of making a custom device per fixture profile will likely always remain relevant when you want to make use of Live’s automation/mapping and enjoy features such as seeing names of the slots being reflected in the Envelope Editor:
In regards to creating your own fixture profiles - as Mattijs already mentioned - the Fixture Editor allows you to do that. It is a part of Beam we are still developing though and there are situations the Fixture Editor does not support yet, e.g. adding custom modulation keywords. In such cases, you can open the fixture profile file (*.sbf) in a text editor and edit the profile manually (the fixture profiles are in the JSON format).
We hope to provide a better workflow for this soon. In the meantime, you are always welcome to contact us and we can make the fixture profiles for you.