Open uisato opened 1 year ago
I believe the issue might be the fps of 60, it doesn't generate enough frames if the fps is higher than the original i have noticed, checking now.
Videos were originally at 59,94 fps and I re-rendered them to 60 fps specifically for testing TemporalKit (since it triggered some errors if I wanted to use 59,94). So I don't think that's the issue now. What do you say?
That's weird, sit should have delt with that fine, you're on the most recent version of temporalkit right?
Can you send the test video so i can try with that?
Update: Spent all frickin' night trying to figure it out. You were right, dear Ciara, it was the fps all along: for some reason, Premiere was not rendering videos in the FPS I wanted. Fixed that, and now it all works like a charm.
Thanks again, my friend. ♥
EDIT2: Broke again, it's just generating copies of video's first frame.
I'll just transcode the video to H.264 format and it'll be fine
when i click recombine and then it generate crossfade.mp4 video, then i compare to the original video it seems that the crossfade give me an extra frame in the middle of the duration.... I need the frame to match the original video completely... any advice?
What could be going wrong? TemporalKit doesn't seem to be generating frames properly. [It apparently only takes a single frame out of the entire 3 second video]
I've made a little video so you can see what's happening: https://www.youtube.com/watch?v=Odutcc8to5o
When I try different videos. The first time I try to run the whole thing through TemporalKit, kind of works, but doesn't generate keyframes. When I try again, this happens again [doesn't even generate frames, just multiples copies of the first frame.]
EDIT: Managed to make it work somehow, but it still isn't generating frames properly, generating some strange results: https://youtu.be/u2Evi9ggUzI
EDIT2: Broke again, it's just generating copies of video's first frame.
UPDATE: If you're having problems with "faulty" results [like the ones in the first edit], it's probably the resolution. [I was at 1024 when I should have picked 1080.]
On the other hand, if TemporalKit is not generating frames properly, that's probably caused because you picked a wrong FPS value.