Touching a parameter in insta. render while it is processing leads as before to intant crash.
Doing it smotthly, rendering after rendering is ok
Still a bad interrupt call while processing.
There are the same issues like in the version before. No real preset management. Even my new presets of the version before are gone but even older from many versions before re-appeared. When I make a new preset and check the box it immediately closes the preset box.
Iâm still not getting anything inside vai when I use the preview in to out. My machine spins up, but unprocessed stays on the right-hand pane, no thermometers nothing happening?
It doesnât seem to like previewing between in / out points. The interface seems to fight against you. Unless you get all the clicks right, it wonât preview.
The previous version were not like this. (From version 2 and on)
Also, you guys had it nailed, you could set the various folders exactly how you wanted it. Now itâs wanting to save files here and there (Just like Windows expects) but we had control on that, and now itâs not so obedient.
BTW: It would have worked OK if you had put things into the Win temp folder, so you donât have to worry about deleting the files, which some here want or need, and then if we change the folders you could go with that.
Also, an option not to delete the temp files.
And forcing the previews into the âdefaultâ folder, because of the new projects.
I donât like applications that store data in Windows folders, often on drive C: and even worse in hidden Windows folders like AppData. All data should be stored within the application folder.
I am still having issues with iphone portrait videos with instant render, the unfiltered video plays normal, the instant preview with enhancement applied will show up without rotation (the frame of the instant render preview is still portrait but the actual content is rotated counter clockwise 90 degrees and stretched). (normal rendered previews work fine)
âShow in Explorerâ does, as usual: nothing. It never did before and it still doesnât. Also the temporary file is not always to be found in the export path told in the Preferenfes. I was not able to figure out where the file is just in case it is not in the export path.
Yes, exactly. Developers didnât have to listen to MS. I had it setup nice, tvai was installed in the default location, then I had everything else going to my very lightly used f: drive (m.2 2tb)
Iâve been loath to say this about any new software, but TVAI v5 is really going backwards. Everything should focus on a good output as quickly as possible. âProjectsâ are really a wrong direction and yet they are made absolutely central to the new version?
The default âProgram Filesâ folders on drive C on Windows are highly protected. You get all kinds of errors from Windows security if your program needs to write anything. Thatâs why most programs either write to My Documents or more hidden places like appData.
Since Topaz canât guarantee that everyone is going to install it on another drive than C, they have to store their stuff somewhere thatâs always allowed to be written to freely.
To expect from none-professional testers to be familar with hidden system folders to deliver certain files or infos on request which happend quite some time ago feels a bit odd to me.
People are asking for OFX for Vegas. Reading the Project would mean reading the Time Line from other Programs .Resolve can import Final Cut.This would be TVAI using the Time line to import the clips.
That request doesnât make sense. Those are completely different programs with different abilities. What would you expect to TVAI to be able to open from any of them?
Based on info from a post in the v5.1.2 release thread, I can confirm that you canât swap between generated previews to view them. The Previews list doesnât seem to be keeping track, and as soon as you select a different preview or generate a new one, all previous previews are lost.
Yes, v5 does not work well at all. It randomly shuts down, sometimes with my fans a blazinâ As @alanhusband-677420 notes the grid is not working right at all. I suppose that when you made the decision to return the grid to most recent one on the bottom as default, that showed everything we need to know about the interface happening here. (Take a look at Photo AI, and another meltdown).
Get the grid sorted, itâs a monstrosity, and appears to be an afterthought.
Iâm lightly thinking, divide the program in half, and have the two displays have their own grid, and quit with the parent/child relationship in the grid.
Of course, the main problem now, is the Projects?? Youâre never going to compete with Adobe on that, so I say just stick with the basics. Great upscaling and cleaning up of video.
Get rid of the projects, and quit wasting energy on things 98% (99?) of users are never going to use, like multiple GPUs. (Unless you can figure out a way on Intel chips to use the built in gpu along with a discreet nvidia gpu.
OK, I see you guys were trying to âgaslightâ me!
5.1.3.1 Finally works well. I see you â* Fixed render in-to-out.â
Yeah, been saying that for awhile. It would have been nice to know you were working on it or looked into it. Same thing happened with then âvariable frame rateâ issue, that took a bunch of posts, but no messages, like 'oh, we see the issue, weâll look into it.
Thanks for fixing that, it was some weird things happening prior to it.
