BTW it’s Artemis not Artemies
I confirm for the preview, it has been bugging for quite some time now, when we get to a point, it shifts the source image by one or two images. hard to compare in good conditions, I prefer the preview of 2.6.4. but hey… apart from that, the latest versions are faster and I noticed especially with gaia when I upscale the video.
Artemis V8 and earlier is what your referring to. You can import V8 into version 2.3 of Topaz, but it was around then that V9 was done and broke it. You can’t import models into version 2.4, so consequently 2.3 is what I still use currently - and this was one of the reasons. The other is also because V3 has no frame control yet for exporting and side by side comparisons on preview are still borked.
You can also use any of the Artemis versions in Version 1 of Topaz as well as they all pre-date it - I have played with Artemis back into 1.5.3 of Topaz.
The main downside is that my scripts that worked well with Artemis take a long time to export. As the current version still won’t bring in Avisynth imports, I have been trying to replicate the results in Proteus so I can export much quicker and then process in Topaz.
The export only would usually take 6x hours. In V2.3 this is fine, because as it exports it upscales, so the overall time is greatly reduced. To do the same thing in current versions meaning adding 30-40% more time to process an episode, putting aside the fact that Artemis doesn’t work well anymore.
Results are mixed still, but I have placed some examples in the star trek thread recently, which I think replicates much of what Artemis “used to” do - unfortunately its such a very specific thing where different videos may have such very different Proteus settings that copy pasting is almost useless unless your working with the exact same source file.
You are right, those are the versions!! 
Hi, thanks for this Version 3.2.0.4.a - but unfortunately my MacPro 2019 still crashes.
Sending you 2 logs, mayby it is revealing:
logsForSupport.tar.gz (968.6 KB)
logsForSupport.tar.gz (241.7 KB)
Hi. The bench results aren’t totally consistent, as I found some differences…
On another bench, I got:
Gaia 1X: 5.28 fps
4X Slowmo Chronos: 11.89 fps
4X Slowmo Chronos Fast: 17 fps
when using video AI 3.1.10 I was trying to upscale some old tv shows that I had and notice when viewing the preview in and external video player there is about 5 seconds where the video is frozen and only audio plays from the video, but of frames before the start of the preview frame, then when the audio catches up to the moment where the video is frozen the video will then play with the audio. This would make it impossible to upscale old tv shows.
I suspect they have a fix, but can’t apply the change because it creates problems elsewhere, otherwise live preview would be working today.
That’s within run-to-run variance. If you were getting greater than 2 plus or minus frames per second, I would call that unstable.
That’s because when making previews, it cuts at key frames. Sometimes there is a lot more audio in the cut than video. When doing a full video, without cuts, there should be no such issue.
Frame interpolation keeps turning itself on any time you save a new preset, even when it is not required (no frame rate change).
deinterlace doesn’t work that good think it was better even in 264, maybe you could look at it and add more options since there are many ways to de interlace thanks.
I highly suspect its related to the change in no longer handling frames of the image - one the things that can kill my usage of V3 still. In V2 the sequences were handled by frame number not time index, and I suspect that change is what has broken the previews and why its taking so long to fix it.
My guess is they need to fix the frame handling before the previews can be fixed, and given that the frame handling was changed entirely in V3, its probably a very large change. Having said that, someone else’s work flows may be able to enlighten me, but I have seen no advantage from changing from frames to time index - it only seems to have made everything harder/worse.
Is there an underlying reason that is more technical I don’t know of? Otherwise, it would seem to make more sense to drop the time index handling entirely and revert back to frames. If it hasn’t been fixed over a year after starting V3, it feels like it was a bad move from the start.
1 Like
Hi,
About the problem with Ventura and MacPro 2019.
I just tested with the latest version of Ventura, the 123.3 which has just arrived.
VAIE lasts longer in the calculations but still ends up in a computer crash.
2023-03-28-06-32-56-Main.tzlog (1.1 MB)
2023-03-28-07-28-20-Main.tzlog (17.2 KB)
2023-03-28-07-27-0-Main.tzlog (17.0 KB)
2023-03-28-07-15-59-Main.tzlog (17.9 KB)
1 Like
Hello, I have used this version and I got error is “Unknown error” when I try for upscaling my video to 4K on my computer with CPU I7-9750H , Ram 32GB and GPU RTX 2060 Super. I have try to try again many times but i still got that. Can u give me a solution for this ? Thanks!
They switched to using ffmpeg under the hood. It does not process by frame numbers. There is a built-in filter that can do frame numbers, but I have not tested it to see if that would be actually be something they could use to get that functionality back for us.
Does setting Max memory usage % to 10 help?
Hello Topaz Labs Team
Before I start explaining what I observed, let me say that I’m not an expert on videos or operating systems, so if there are any errors in what I’m trying to explain, please correct me instead of just criticizing.
Every time I put a video to process, I go to the windows task manager, in process details and I increase the priority of “Topaz Video AI.exe” and “ffmpeg.exe” to “realtime”, This is still not the problem, doing this works normally.
What I realized is that my computer has 2 video cards, one intel and the other nvidia dedicated 3D, the “ffmpeg.exe” process is all the time allocating GPU1-3D (nvidia), but the “Topaz Video AI.exe” process it keeps switching (I think every frame of the video) between GPU0 (non-dedicated 3D-intel) and GPU1-3D (nvidia) in a copy process every cycle.
I think that’s why VIDEO AI’s main screen has that flickering window background look, vibrating the color tone a little lighter and a little darker, I believe because the program is constantly switching between video cards.
Would not forcing this process to run only on the dedicated GPU card, instead of copying from one card to another, increase the overall performance of the program?
Would it be possible to implement an option to force the priority that the “VIDEO AI” process will run within windows? and another option to really fix which video card will be used?
In before the thread closure - there is already an option under Preferences to choose which GPU (or set to Auto).
