Hi.
this patch is rather for Plugdata, since Pd imo does not have gate, tough u can use else/router, which is the same.

As a tribute to Omar I've shared a patch using his interpolation technique and update it on 3 values.
There was discussion on this topic on FB too (also deleted, tough) and consensus was, that value offset created when adding nother interpolation is caused by imprecision of slider. I found it is not EDIT "completely" true,
Slider in Plugdata is pretty precise.
It is - obviously - cause by leaving the smallest step value in previous approximation, which distorts the final result.
Solution is to send "0" to not used part, when interpolating other value..
EDIT: *Tough as mentioned, despite 6 digits are pretty fine (enough for DIY fine-tuning in DAW, without noticeable side-fxs. W/out this there was offset even 1/3 of step - 0.02-4 cca, now it is in 0.5 Hz range - beyond vst synth resolution), but this is definitely not the best suited approach for 12 decimals scala-like Pro fine-tuning etc.. that wont fly

BTW there should be probably even more elaborate solution, for more values - like using append+scale... if someone would like to beat the efficiency (make it dumber)) contest..

Happy patching.

Scale version is - obviously - in comments sesction..

https://www.dropbox.com/scl/fi/s1wncx9eytc50sukzwris/Interpolation.pd?rlkey=utcp4cd7dder4jpuduggkomji&dl=0

@Aliam.Sigsaly [switch~] is vanilla but just add the appropriate [declare] and your patches will work with most all flavors of pd. Your [> 0] -> [+ 1] -> [gate 2] and [sel 0 1] can be done more efficiently with just a [moses] and a couple [t b f]s. I also used [value] for the numbers to be interpolated between which makes things neater and allows you to use [send] to set the value. The issue with sliders are that they quantize to pixels, this is not much of an issue if your numbers are close together like in your example but if your number are 1, 2, 984 you start noticing issues, but often still good enough for the job.

Interpolation.pd
Edit: Also, if you rework the equation so $f5 is $f1 you get a bit more efficiency since it saves a type conversion and also makes things a little neater, fewer objects. Forgot to do that in my rework.

For the record, just so anybody else gets confused, it's not like it's plugadata which has more things than vanilla, it's really the other way around!

plugdata offers some externals that are from vanilla and has done a great job but it doesn't include 100% functionality and all objects from these libraries. The plan is to do so but it has already ditched comment and scope~ from Cyclone in favor of ELSE alternatives for good.

@oid: Thnx for patch.
Yea, u have to be right - Slider is more imprecise cause it is px based - and it is same in MAX, Pd, Plugdata,
I often use number box instead of slider to make more exact out.

Have a good one.

@oid Have even dumber version - 6 instead of 9 object - 1/3 enhancement in brutalist/ minimalist matrix.]]
Interpolation-scale.pd