Map parameters with Sysex editor or LUA code?

[Electrolove]

I’m working on a preset for Strymon BigSky. It works in such a way that when you change the type, only the parameters that are available for that type are displayed. This is done with LUA code. The LUA code ensures that all parameters are given the correct name, the correct interval, and that only the parameters that should be displayed are displayed and so on. It works really well and makes it much easier to understand how BigSky works.

Does this mean that I have to map the parameters with LUA code instead of the Sysex editor? When I try to map the parameters, all that appears is THIN FADER, THIN FADER, THIN FADER, THIN FADER and so on…

[martin]

both ways work, but you will need some Lua logic even if you use the Sysex editor - you can use Sysex editor to define to what parameters (possibly virtual / hidden) the parsed data will go and then use Lua to distribute the values to thin faders on the screen and adjust their visibility and labels.