An example of breaking previously saved plugin states is a plugin changing it's internal mapping of a fixed range input (0.f - 1.f for example). If a plugin dev wanted to change their mapping, for example to extend the range of a filter cutoff or a delay line, how could they do this without breaking previously saved states? One quick idea is to allow that internal mapping to be selectable by the user, one to be compatible with the old plugin version, and the new to be the redesigned range. But would doing that just be a cludge and pose more problems in the future?
Statistics: Posted by camsr — Sat Mar 30, 2024 11:26 pm — Replies 4 — Views 120