Fortunately, the second scenario is both much more common, and easier to correct. With just an average rate, there's no way to tell a video with inconsistent timing throughout, from one with mostly perfect timing, but one or two short/long frames. But that doesn't mean your video's timing is bad. Quite literally, frames ÷ seconds = frames/seconds = fps. That 24.999875 you're seeing is an average frame rate - the number of frames, divided by the runtime. While it's possible it would be able to correct frame rate issues as a side-effect of what it does, if nothing else it's likely overkill for the purpose, and probably not entirely necessary anyway. It's an interpolated frame-generation algorithm more than a rate-control one. It still produces the final file, which is all I care about, but it also doesn’t clean up the temporary file that is created during processing, which I assume is due to the crash.I don't have the Topaz software, but from reading their site, it appears that Chronos is, as you say, about slow or fast motion - exclusively. I’m on Windows 11, Core i9 12900k, RTX 4090, and 32GB of RAM.ĮDIT: The program is also still crashing after the completion of a (large) file. This is based on using the Proteus model, with the new Replace Duplicate Frames feature - I haven’t tried it without using that to see if that is the reason for the speed decrease. Also, by comparison to v3.1.2, I’m finding that I’m maybe 2-4 fps lower on this newer build I was pulling as much as 17fps with the older build. ![]() This doesn’t seem to have any effect on the file generating the video properly, but I thought it was worth mentioning. ![]() ![]() With this new release, I’m finding that previews generate okay until it gets a few seconds worth of rendered data and then it will loop the same (early) section regardless of if you try and move the slider indicating how far along your render is.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |