ysfx: report internal state change to daw (wip) #72
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It would be nice to save an undo history, but unfortunately this is complicated. The issue to work around is that most DAWs (e.g. ableton and bitwig) do not call
getStateInformation
/setStateInformation
when callingupdateHostDisplay(ChangeDetails().withNonParameterStateChanged(true))
. This does work in REAPER though.You can get bitwig to store an undo point if you rename a parameter, but this is likely to cause bad issues down the road. Only changing a value seems insufficient.
It might be worth exploring exposing a fake parameter that basically triggers a
ysfx_save_state
that we store ourselves.