Posts: 10.574
Threads: 57
Joined: May 2017
If you want morphing on scene changes instead, simply disable the scene change detection.
About the seeing what misc.SCDetect does, you could add some custom code to show whether the current frame is tagged as _SceneChangePrev=1 or not and thus is the last frame before a scene change.
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Posts: 40
Threads: 8
Joined: Dec 2023
(24.11.2024, 14:11)Selur Wrote: If you want morphing on scene changes instead, simply disable the scene change detection.
No! I would like to not have that doubled frame there, so later I just delete that and do another encode.
And having custom code doesn't sound like a me thing, hardly know what I am doing here.
Posts: 18
Threads: 4
Joined: Feb 2024
Hi selur, the dev worked perfectly and did a perfect job of identifying the scene cuts.
My question now, when RIFE detects a scene cut it repeats the frame to prevent a garbled frame between the scene change. However, on a panning shot, it comes across as a stutter as the final frame is duplicated (or very similar).
Is there a way for the system to anticipate the final frame and interpolate into it the same as it does with all the other frames? So that a panning shot ends with the same rate of movement rather than slowing down abruptly on the last frame? Currently using RIFE 4.15 (ensemble false) for reference. I've seen there is a blend function rather than duplicate on a scene cut, does that blend the final frame of the scene to the penultimate frame, or the final frame to the next scene frame?
Posts: 10.574
Threads: 57
Joined: May 2017
Nope, RIFE itself is blindly interpolating between frames.
The scene change detection basically just cuts the scene into chunks, feeds these chunks into RIFE and then adds
duplicates around the scene changes to meet the desired frame rate.
You would have to ask
https://github.com/styler00dollar/Vapour...cnn-Vulkan to add something like what you want to the code.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Posts: 18
Threads: 4
Joined: Feb 2024
Thank you for explaining, I'll reach out and see if they have a magic solution for my use case
Just a thought Selur, if RIFE is just blindly interpolating between two frames, what if the frame rate I set was just enough to generate an extra frame? I can't think off the top of my head exactly how that would work but though't I'd propose it if it could generate an idea.
Posts: 10.574
Threads: 57
Joined: May 2017
You would have to read the code to know for sure what exactly happens in which edge case.
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.