Small gripe but this has been happening for4 a long time. Can you make it so that when I update the software I don’t have to pin it to the start menu every time?
With my Ryzen 7 5800x system and whatever GPU (3060 ti and 4080 specifically) my real world upscaling with Artemis is maybe 30% or so slower than indicated by the benchmarks, with everything else turned off including detail recovery, and audio set to none. Prores. Well that’s a lot, and I am sure there is a logical reason for it - but it doesn’t help to maintain confidence in the software claims and makes GPU/CPU combination comparisons very very difficult (you should see my spreadsheet!).
Assuming that others see this too, it seems to me that the benchmark program needs to be re-done to better reflect real world conditions. That’s for upscaling - but also, comparing slomo and e.g. Apollo with Chronos, that’s just as difficult for 2x slomo because the benchmarks only do 4x - which flatters the Apollos. Chronos is just as fast as Apollo for me at 2x, and much the same as Chronos Fast.
v.3.3.9 - a lot of useful fixes - is it worth updating to it or staying on the old version?
still using v.3.3.5 - this version is more stable
because versions 3.3.6 -3.3.7 -3.3.8 were terrible - with many different problems due to “Preview”
in version 3.3.5 I was able to turn off Preview and set it to ignore Preview and Trim
and starting from version 3.3.6 everything is bad - so try version 3.3.5 and set to ignore Preview
My point is that you referenced 3.3.9 specifically, when the problem has been present for all v3 releases since it’s inception. Which makes anyone reading your post think, oh, there’s a new problem in 3.3.9? So yes, misleading.
It’s never worked properly. As you know, I’ve already posted about it here, and I’m sure the devs are aware. When it gets fixed, or even can be fixed, is anyone’s guess.
Versions from 3.3.6 to 3.3.8 introduced a bug that I could not live with, namely the estimate function in Proteus manual mode did not work. This version seems to have fixed it, thank you.
I also tried the 3 functions for presets, create, delete and update and they work well. I did run into a little inconvenience: I want to create a preset for upscaling to 4k at a fixed 8k bit rate so I select the built-in “Upscale to 4K” then I changed the encoder bit rate from “Auto” to “8k”. Now to create a custom preset, I have to change the preset to “None” first before I can create a new one. I wish that create function (+ icon) is added to all the built-in presets in the future.
If you are working with 720p input resolutions and up, and exporting to anything other than ProRes, you will quickly see that export preview is broken.
It’s not convenient. If I need a quick preview, I just open the image file in the preview folder with Irfanview.
pressing the right arrow plays back the video at whatever speed the computer can handle. Normally though, when I want to do heavy detailed comparisons. I process the clip several times with all the variant settings and convert them to H.265 with software encoding. I then open them all in instances of Media player classic and swap between them.
The reason for all this is because I have to use the command line to get the results I want for most of the movies I process.
