Is there a reason why disabling and enabling presets with incoming actions only works for presets and not for translators within a preset? Only having that available at the preset level means that there can only be one group definition for “disable all others”. I would like to be able to enable and disable processing and be able to group those mutually disabled sets within presets. Something like “disable all other translators within this preset”, but not affecting the enabled state of translators within other presets or the enabled state of presets.
Marked as spam
Hmm... after thinking about it a little bit, it seems that it's not absolutely necessary to be able to group things that way. It would still be convenient, though, to be able to logically structure the functionality of a complex project where stuff that applies to a certain controller input is all organized within a preset and whatever enabling and disabling of processing pertaining to it happens within that preset.
Hmm… after thinking about it a little more, I think I changed my mind. Maybe it’s fine that you can only enable and disable presets with actions and not translators. In fact maybe it’s better, since it means that all unnecessary processing will be disabled for a given event–provided that you structured your project that way. It just would have been good if I had understood that. But I do now.
Please log in to post a topic
(this is your bome account, not the old forum account):.