In addition to the missing Chronos models, there’s a major performance issue with this build.
Using a 1440x1080 input, upscaling to 1920x1080 with letterboxing, and FPS conversion using Chronos from 23.976 to 59.94, plus Proteus Auto, I get about 3.3 fps. In the 3.2.0.4 alpha, I get about 11.3 fps.
My system info is in the benchmark I posted above.
Is this the source of the almost 4x performance hit?
Edit: looks like it is, I ran the same processing job as mentioned above with interpolation off and the alpha and beta were about the same speed. So the new Chronos model in this build is causing about a 3.5x performance drop.
So other than incurring a massive performance hit, what does the new Chronos model do?
appolo is slower for me so, and from what I see it retains more detail. on the other hand for the previewed ones, around 47% of the first images are frozen.
Agreed. How are we supposed to ‘test’ if we don’t even know what the changes are.
Either way, this new Chronos is so slow there’s no point in playing with it further, especially when they won’t tell us how it differs from the other Chronos models.
Also, consistent naming schemes would be nice for the future.
For example, in the benchmark tool, the new Chronos is called Chronos while the old Chronos is called Chronos v2. This implies that the old Chronos is actually the new one when in reality it isn’t.
For me personally, the new Chronos should be called Chronos v3 so we know it’s newer than the old one (and it is chr-3 that in the command line, but not in the GUI)
The OLD Chronos is called Chronos v2 and it uses the code name chr-2 in the command line.
The NEW Chronos is called Chronos v3 and it uses the code name chr-3 in the command line.
The NEW Chronos is available in the GUI under the name Chronos.
You can not select to use the OLD Chronos from the GUI.
The OLD Chronos is in the benchmark, it is called Chronos v2
The NEW Chronos is in the benchmark, it is called Chronos.
Here are my Mac Studio Ultra benchmarks. First set, as per default. Second set, selecting the GPU (2nd option in the pulldown menu) and 70% VRAM Settings…
I noticed that TensorRT Chronos v3 models aren’t loading correctly on RTX 3090 (at least on Win10 22H2 with 531.41 Studio driver), which causes this beta to fall back to .ox model (on the screenshot, files are sorted from newest to oldest, the model files were deleted during the install):
After trying to preview the second time, this beta downloads all the .trt models again, before falling back to .ox.