TVAI needs a better Interpolation when converting from 23.976 to 25 or 50 or 60 Frames.
I notice when there should be more smooth movement due to the higher framerate itĀ“s not there.
Instead there is showing up a stuttering making those Interpolation unusable.
Going from 25 to 50 would be never a problem because itĀ“s just another frame that would be perfect timed set.
But going from 23.976 to anything else would make it neccessary to render ALL images when you make a timeline for a second with 23.976 and 25 frames. The timecode of each frame is slightly different nowā¦and it doesĀ“nt help just to render in betweens of two framesā¦
So not making Frame 1 - 2 - 3 - 4 to 1 - 1.5 - 2 - 2.5 - 3 - 3.5 - 4 = normal way just render in between 2 framesā¦50% of frame 1 and 50% of frame 2.
Going from 23.976 or just say 24 to 25 frames it creates stuttering when you just add one frame every 24 framesā¦and the timecode of each frame is now wrongā¦the first 24frames are pressed together making them play a little bit faster(earlier) and then an additional frame is added.
Each frame when converting from 23.976 to anything else needs to be rendered in a different way so that the time the frame is played is matching the thing you should see.
If you press 23.976 frames together in order to add more frames into the same second you need something different than rendering an exactly in between of two framesā¦like 50% of frame1 and 50% of frame2.
It should be more like maybe we start with frame 1 and then we render frame 2(at this point without adding a frame but correcting the timecodeā¦frame 2 is no longer at the timecode where it wasā¦itĀ“s more towards frame 1ā¦so frame 2 should be more like maybe 4,0997% of frame 1 and 95,90% of frame 2.
23.976 frames means that there will be every 0,04171s another frame
25 frames means that there will be every 0,04s another frame
Frame 1 will be taken unchangedā¦Frame 2 should be 4,0997% of frame1 and 95,90% of frame 2 as example
At a special point of rendering itĀ“s time to add a frame in order to reach the wanted framerate.
A workaround using the present programs could be renders a really high framerate like 120framesā¦
So from 23.976 to 120 framesā¦in this way there will be a lot of frames created between frame 1 and 2.
When you now reduce the framerate from 120 frames to maybe 25 or 50-60ā¦the timecode of the frames could be less or no stuttering.
Trying that out:
What happens when converting from 23.976 to 120 framesā¦what do you expect to get ?!
YES: A lot of non moving frames that have been insertedā¦is this really interpolating ?!
Frame order: F=frozen M=moving
F-M-M-F-F-M-M-M-F-F-M-M-M
The sad thing is i am telling here how to code this shitā¦but i am not paid for it after all.
So the normal interpolating is failing here a lot but converting from 23.976 to 120 looks a lot smoother but has a lot of still frames in itā¦some times 2 still frames after another(no itĀ“s really mostlyā¦almost?!).
So removing duplicate frames afterwards would not help here a lot because thereĀ“s not only 1 frozen frame there are 2 and removing duplicate frames maybe canĀ“t handle those correclty.
How much frames do we need to convert from 23.976 to 25 using this software ?
The 2nd frame needs to be shifted 0,00171s more towards frame 1.
In one second 1/0,00171s=584,8ā¦so about 584,8 frames per second to match perfectly.
Normal frame interpolation sucks so we try another thing that works(i hope) itĀ“s slow motionā¦and the max is here 16xā¦what does this do it converts from 23.976 to 383,616 frames but plays still at 23.976
But that would be the most best way to get a smooth moving version to come closely to 25 or 50 or 60 frames/sec. when ripping of the unwanted frames afterwards.
So what does TVAI do when we choose slow motion x16 of 23.976 frames ?!
What do you expect ?..super slow smoothing movements ?!
NOOOO !
You get instead a lot of non moving frames added instead:
Frame order: F=frozen M=moving
M-F-F-F-M-F-F-F-M-F-F-F-F-F-F-F-M-F-F-F-M-F-F-F-M-F-F-F
ItĀ“s defenitely not what i expected spending so much money for this softwareā¦
I am spechlessā¦
Hmmm 23.976 frames converting to something else always sucks with TVAI.
Why ?..The software seems to search for places where it can put in 50% in between frames.
But this strange framerate makes it impossibleā¦so it works always this way:
A 50% in between frame connot be placed so we fill in with a still frame.
After all no interpolated frame is there just a lot frozen frames added to reach the amount of frames wanted.
But in my mind i would think render x16 frame should be no problem.
But here it is reality.
Next Try saving the 23.976 Frames Video in a way TVAI thinks it is 25fps.
The same shit comes out doing slow motion x16 with Apollo fast v2
Can it be that those interpolation/slow motion is totally broken in the official release just adding still frames ?!
To the devs:
To which version is it needed to revert back when those frame interpolation/slow motion worked you used to show these example videos on the web page ?!
And is it still possible to get money back when i realise that this software is a bulk of SHIT ???
Is there any chance to get those old devs back that left before all this shit came up ?
Or tell me where they go so i can buy in the future a software from them instead.
Something is really getting worse hereā¦
Next try what happens interpolation 25 to 50 frames.
It is working the right wayā¦no dupesā¦adding after each frame a frame.
But looking at frame by frame i seeā¦
FM=Fast Movement SM=Slow Movement
FM-SM-FM-SM-FM-SM-FM-SM
Again speechless i have to search for another software for interpolation TVAI sucks always.
