The jump from VEAI 2.x to TVAI 3.x was major. Everything was rewritten. And, not only was the older functionality replaced with newer versions, they were chained together differently. This makes possible the use of multiple filters in a single pass. This required rethinking the roles of each filter and how they relate to each other.
It takes a bit of floundering around to become accustomed to the way these capabilities can be teamed up to give maximum results with the least amount of effort. Of course the processes may be a little slower, for the present, but when properly configured, the results are well worth the wait.
As far as the “raw” condition of this “released” product. A lot of the beta-testers were there to witness the evolution of v3.x beta from a bunch of ‘ideas’ and into a fairly well integrated system. But most of us thought that the production release was done a bit too early.
As I said in my previous reply, there are still a lot of glitches, (or bugs,) that need smoothing out. TVAI 3 has been a very complex developmental undertaking and the amount of software, and layers of software involved is considerable. There are bound to be adjustments and fixes for a while to come. However, despite this a lot of us are learning how to work around some of the problems for now, so we can take advantage of the advanced capabilities, and (of course) report any defects or make suggestions that may make the software easier to use and more reliable. - That is a big part of why this forum exists.
One thing I’ve discovered. is that there are some lower-level issues that can crop up during previews, which may cause the final export job to fail. My workaround for that is to save my settings in a Preset. Close TVAI and do a full reboot. Following which, I load my source, recall the saved preset, and export immediately. - I am certain that in the future, the problem(s) causing this will go away.
By the way, it is not uncommon for the primary release of any new and complex body of software to have some problems. Many of these are not detected until the software has been widely distributed. - It is impossible to anticipate all possible problems in a testbed environment, especially when the users/tester/programmers are already familiar with using it. And as I said before, TVAI 3.x is not just an upgraded version of VEAI 2.x, but completely rewritten.
I have a very fast system with an overclocked RXT 3090 in it. And I admit that I would like TVAI to run enhancements faster. I’m moving to an RTX 4090 soon, but from what I have heard even the more powerful GPU will not perform miracles. Even so, I am confident that the problems will go away and the processing will get faster. Until then I am using it and being patient until things improve.
As a woman from Montral, Canada once said to me “Paris was not built in a day.”
As my first team manager in a software development project told me "It’s the first hundred years that’s the hardest.