Using the auto-update functionality from the prompt within the program doesn’t give the user information that the update is being downloaded in the background apart from the progress bar in the top right corner. I would suggest a prompt along the lines of “Your update is downloading in the background. You can continue your work and manually start the installation later. Progress is indicated in the top right” or something like that.
The update at least recognised that V3 was open and offered to close it which worked without issues.
It would be nice to have some kind of documentation of this from the developers. Not buried in some forum post or in the hidden beta forum, but in the program itself, or on an online help document.
I uninstalled the software, ran some Windows cleaning & regitstry cleaning programs, rebooted, reinstalled Topaz, rebooted again, & now it’s working as it should be.
I am very dissatisfied with the speed.
Topaz should prepare benchmarks and collect CPU, GPU, MEM, M/B, I/O… from each user and investigate where the bottlenecks are occurring and consider how to deal with them.
No such efforts were made in Alpha, Beta and Early.
The fact that they don’t seem to be doing anything to improve the speed further increases my dissatisfaction.
I think the goal of topaz is to have only two softwares, Topaz Photo Ai, and Topaz Video Ai.
so the name follow how Photo Ai is named.
as we can see with the add of stuff like stabilisation, the software become more a “one for all” software than just an upscaling / enhancing software. (just my opinion, not sure it’s the right reason lol)
I’m sorry if this has been mentioned before, I don’t really want to read ALL the messages so far…
But I have a couple of suggestions:
It would be great if you can pause the rendering of a preview or export without having to stop it and start all over again. Also it would be great if you could -at that point- save the jobs you have running if for some reason you want (or have) to shut down your computer. Let’s call it “filename.tjb” (topaz job) that you can save as a file and reload after restarting Topaz. It would also enable you to save a job that has finished and open it again later to try different settings.
Also: when I’m using Premiere Pro and Topaz simultaneously I can no longer place in- and outpoints on a clip in the Premiere Pro viewer… (MacPro 2013, Monterey 12.6).
Finally: there are “lines” in the vertical middle of my exports that look like a tightly coiled spring that runs from the extreme left of the picture all the way to the extreme right… It’s in a clip that I stabilised and slowed down. Kinda makes the clip unusable.
these two options were planned for the release or the one just after, but because of the GUI crash issue we had in Beta, the developpement of Veai was “late” because of it. so these two features have been deleayed in a future release. (when ? i don’t know). but they are planned since the beginning. the developpement of the 3.0 branch has been done because having such a feature in 2.6.4 was not possible.
hope it answer a bit to your question. ;).
In Version 3.0.1 i have big problems with GUI crashing all the time, i set for example 2 videos on working go do something else and when i get back GUI is crashed disappeared from process list … and there are 2 ffmpeg.exe processes left alone working in infiniti loops, this start to be very frustrating.
if it’s the GUI only which crashed, the software didn’t. ffmpeg behind continue to render your video, and will normally finish the processing normally.
if the GUI crash with 2 videos working at the same time (parallel processing) try to only work with one video, and see if the same happens.
Topaz video AI 3.0.0.1 bug report after VEAI encodes enhanced h264 mp4 playback is okay in Windows 10 but now when imported in to
Vegas Pro 19 it only shows audio. I re-encoded video with ffmpeg and still no video displayed in in Vegas
this h264 mp4 says corrupt in Vegas pro 16 as well.
Topaz video AI 3.0.0.0 h264 mp4 video worked perfectly in Vegas 19. Problem only since 3.0.0.1 update.
These were two very short videos … GUI was showing 5 minutes of time each, after the crash I waited 2 hours out of curiosity and nothing finished rendering.
i’m noticing issues with file render and playing them (H264) in MPC-BE.
In Vegas Pro 19 Build 643, i can load the video but the audio track is longer than the video. don’t know if it’s in sync or not, can’t turn on the sound for now to check it.
ok, so we’re on another problem then. this 3.0.1 is definitively not good. i’ll go back on the 3.0.0 certainly and still use the 2.6.4 until the situation get better.
did you tried with processing only one video ?
maybe, we must understand that we’re on two releases which are full of bugs. so it’s kind of finding a temporary workaround to use them unless the software will have some of these issues fixed. it can take some times.
