If you want to slowly "morph" between two presets, the traditional way is to "interpolate" with the pattrstorage object.

I was having problems with that method, because it seemed to fill up the schedular. So I've been using this method instead.

The preset won't do it alone, so as Mike said, this is usually done with pattrstorage. If you want to be able to incorporate the preset object however, here is a simplified hack of a M4L template Preset device to enable interpolation. Presets can be stored and named (but are actually managed by a pattrstorage)- Instantaneous presets are recalled in the usual way. To interpolate (set by the interpolation time value) enter the destination preset number in the number box. THere appears to be inconsistent behaviour when the Preset recall modes (preset button or number) are used alternately - but I don't have time to sort it right now...

@mikefonte I like your method but I think that would be too much hard coding for my current setup since I'd have to hook that up for each value. Also worried about triggering that many line~/snapshot~ objects at once. Great technique for smaller patches though. Thanks for the share.

@spectro This is a great place for me to build off of. Thanks so much for posting it. At the moment I'm having trouble with it automatically interpolating back to preset 1 after it reaches the values of any of the other presets. Guessing that's not intentional but I'll dig into to see what's triggering that behavior.

A bit less busy today so took another look at that patch. Here is a revised version that appears to address that (non)interpolation issue - and a few others - It bypasses the number box to select interpolated presets. Now to interpolate simply dial in a time value > 0.0 and select the preset. Also although I was under the impression that linking the preset object to the pattrstorage (see preset help file) would create problems with interpolation behaviour - that doesn't appear to be the case (glad, if a tad confused). If nothing else, linking enables the stored name of the preset to appear when hovering over the preset object with the mouse (useful) and also, any UI objects not controlled by a connected pattr object will not have their state stored in preset object by default - which may have been the cause of the problem you encountered above...