I reported at least twice during the beta that the application does not respect the minimum window size needed to display all controls. Video AI should limit the ability to shrink the application window just like Gigapixel AI or Photo AI do.
Would it be possible to review the app’s log files to see what could be causing this lockup?
To gather logs, please select Help > Logging and make sure that there is a check mark next to File Logging. Next, recreate the issue and then return to the Help menu and select > Get Logs for Support and attach the “logsForSupport” file to your reply.
You can securely submit your file(s) to our Dropbox using the link below. Please be sure to send me a note to let me know you sent something.
It appears that exporting when a project is on a network resource is causing TAVI 5.2.2 to lock up entirely in this new update. You guys fixed the network location importing issue last time but now in this version it appears to cause TAVI to become unresponsive indefinitely the second I click export until I force close it. If I map the same network location as a drive instead of as a resource everything works fine.
Tested on 2 different devices with a few different files all coming from my NAS. Tried a few different models just to be sure, instantly locks up the application. Changing the export location to a local drive or another network drive also does not help. Reverting to the previous version fixes this as well. I know mapping is an easy fix but I don’t normally map network resources as a drive for any of my workflows.
Finally, a huge enough improvement that it’s an upgrade to the last minor release! Pretty good. Now, instead of 2 second previews, I decide between 5 second and live previews depending on if I’m paying attention to motion or an image. The options scroll too slowly, and I wish the before and after view started with the import properly and displayed more reliably.
Why is Topaz even messing with this? It should focus solely on AI training and upscaling and then allow other, more capable tools the task of re-adding the audio track and subtitles. Adding all these extraneous and unrelated capabilities to the application only introduces more bugs, while at the same time, increases customer frustration. After all these years, I still see no reason to upgrade from version 2.
You’re right, but that’s now beside the point.
It is handling the audio and also other multiplexed streams that can be cut, converted or changed in timing.
If we would then need to process these streams and mimic the handling afterward and in other programs, the whole process would become a very tedious job or even undoable.
If I change the framerate, I expect the audio to stay in sync.
My guess is that you’re looking at it from your own perspective and don’t even have things like subtitles. Maybe not even audio.
My guess you also have a video editing program… I don’t know.
Anyway… That work now has been done in the past and it only needs a bit of work to add the stuff that was forgotten or deemed unnecessary.
This is a tool and like most tools it isn’t used in the exact way or for the exact purpose as you use the tool.
When the source file is on a slower (but not a slow) disk and the source file is big Topaz starts reading for more than a minute after taking a 5 second sample.
I don’t know why it needs to read at all on the source disk, but it does and it doing it at > 150 MB/s, so it’s not slow.
It’s as if it reads the complete 50 GB of the source file again.
Can’t you reproduce it using a NAS or a classic harddisk?
I changed my workflow and deliberately put the source file on an SSD.
