Apollo or Chronos for Slow Mo?
What is the general rule of thumb (generic guide line) when to use what model for Slow Motion?
what use case or type of movie?
I know you might say, try both and see what works best for you, but that is not my question.
Chronos because it is much faster, unless it produces obvious artifacts in which case I try Apollo in 3.0.x, which are all I have access to in v 3. Others have said Apollo produces less sharp output on some videos so really thereâs no getting away from âtry both and seeâ as everyoneâs video types are different and speed matters more to some than others.
Iâm saying thatâs what I do, because it works for the kind of old videos I am using. The bonus is that itâs faster. But I donât âpixel peepâ (for want of a better phrase) like some do so I cannot tell you which is inherently of higher quality, they are both good enough for me on most videos.
Apollo analyses more frames (therefore slower) when interpolating a single frame. Apollo is better for video with more non-linear (less predictable) motion, whereas Chronus is faster but only gives best results with linear motion video.
But in fact, Apollo will make the video quality lower, and produce distortion in some scenes, if you care about it, never use Apollo until it is improved.
The best approach is to take a small extract from the full length video and see what each model does with it. The models really are source dependent and settings that work on footage A may well not be as good on footage B.
All you really can and should do is try things & see what works best for that footage - the long & short of it is that there are no hard & fast rules.
yeah, i did that already, the thing is i didnât see any difference on the output file(s) trying both. hence why I asked what is the rule of thumb/guide lines on when to use what module/filter for what video type/use case as a best practice.
that was true for Apollo v4, but since then Topaz released v5 which they claimed fixed may problems previously seen. so i am not sure this statement is correct anymore.
Been meaning to do this for awhile. Here are six of the same clip done with all the combinations I can think of with the interpolation models: Interpolation.zip link
Chronos Fast, output FPS 59.94, ChronosFast.mkv
Chronos Fast, output FPS original, slow motion 2.5x, ChronosFast25.mkv
Chronos, output FPS 59.94, ChronosSlomo.mkv
Chronos, output FPS original, slow motion 2.5x, ChronosSlomo25.mkv
Apollo, output FPS 59.94, Apollo.mkv
Apollo, output FPS original, slow motion 2.5x, Apollo25.mkv
All clips were output to png then converted back into H.265. So I cannot say the outcome will be the same if outputting straight to a video in TVAI.
I chose this clip because of how bad it is in Chronos Fast, but Iâm sure it does not expose all shortcomings. Just a really common one I have seen often.
Chronos slomo was pretty decent. I have had the same problem as in âChronos Fastâ, (first section). Good to see it can be fixed with Chronos Slomo!
On the last conversion we did, using both Apollo & Chronos (slow) to 0.96% speed on the original 25fps spurce file and then importing the output into After Effects & interpreting the footage as 24fps to stabilize it (as the output from both models results in a variable frame rate file according to MediaInfo) which then increases the run time by the 4% we lost in the slo-mo we found that the Chronos conversion resulted in a much more vibrant image than the Apollo one.
It feels like a bit of a faff to do the FRC this way, but it has proved to be the only method that results in a stable 24fps result suitable for use on an international Blu-ray.
If anyone has a better solution I would love to hear about it