Just tried to help. I also do this for 20 years, professionally for more than 12 years. And I do not have to boast somehow either. And 60/24 makes 2.5. Good luck, and high respect for what you’re doing!
I’m not saying you aren’t helping. I’m saying that when I say the output is smooth, I’m not wrong about it. In TDeint’s case, we’re interpolating frames to get there. I said as much, at multiple times. That’s why I gave you an extensive explanation for what scripts I run and how I process the file.
The reason the method works is because the interpolated frames are near-duplicates of the originals. The reason they don’t get noticed is because we repair the frame boundary issues that make them noticeable. The end result is an image that maintains the same smoothness as the original.
All data is stored on an NTSC DVD as 59.94 interlaced fields, including these DVDs. We keep the three progressive frames and repair the interlaced ones, either by weaving them, repairing via the “Repair” command, or outright borrowing them from a second file. These methods can be used to eliminate the distorted frames at frame boundaries.
Because all data is stored on these NTSC DVDs in 59.94 interlaced fields, 59.94 fps is not a problematic target as far as motion is concerned. A D2V file, processed in this method, runs at 29.97 fps not 23.976 fps by default. Progressive frames are retained, interlaced frames are deinterlaced, and new frames are interpolated.
https://www.extremetech.com/wp-content/uploads/2020/09/Sacrifice-Correct.jpg
This is what a proper Staxrip file looks like before you run a program like TDeint. That’s what you see when you pull a D2V file into the application for editing. Then you run TDeint against this file and you double the output rate to 60 fps. There is no invocation of the 2.5x multiplier. At 60 fps (having used TDeint for interpolation), the video remains perfectly synced with the audio and neither 23.976 nor 29.97 fps content moves too quickly.
I will upload you video clips if you would like to see it.
EDIT:
Seriously, Frank. In no way am I trying to either imply you are unhelpful or crap on your expertise.