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.
Implemented switch for handling legacy vs new interpolation
I decided to move the actual calculations of the interpolations outside of convolute, to make it more clear if we for some reason decide to add more interpolation modes.
I then have a function pointer that is set on each block that points to the active interpolation function. I though that would be more optimal than having several if-statements inside of convolute().
I have also included the morph interpolation that I talked about yesterday. It is only used in cases where the morph value has changed more than 5 frames in a block. It works pretty well to reduce noise in those cases.
A nice side effect is that it also reduces the noise when changing value with GUI, as those stepped changes will now morph instead of scrub.
Addresses #7784 #7777 #7696