Well… bugs are related to the end user and their computer. I’ve had no experiences with bugs on V3 so came here to express that because the devs need to know that at least 1 person isn’t having problems.
My processing PC is a workhorse that never crashes for any app. Its been running for 3 weeks non-stop processing videos from V2 and now V3 so if V3 really was the issue then it would have crashed by now or given me an error.
Reading back through the complaints it seems that most people just have incompatible hardware or out of date drivers. End user issues.
Shit happens! And nothing is so perfect that it never will crash. Bugs are related to users as well as to the tools they are using. And the comments in this forum prove it for both.
I cross my fingers for you that that you can stay happy with your system.
Strange problem with 3.0.1. If you upscale to 4K then the export is displayed with every media player in a small window with thick black borders. Unfortunately also with my video editing program. There you first have to enlarge the section so that it fits into the 4K window.
Here with VLC Media Player:
are you sure you’re not running 3.0.0 instead of 3.0.1 ? your comments would be accurate with 3.0.0, this version work pretty well for a basic use (upscalling, trim, crop etc…), but the 3.0.1 has unfortunatly lot of bugs and issues. didn’t had the choice to come back to 3.0.0 to use the software. and despite some bugs which are there too (like corrupted videos if the rendering is on a too short trimmed video), it seems so far to work ok by using only upscaling (artemis and proteus/auto).
the 3.0.1 is a complete another story unfortunatly.
i’m the one here who try to tell the most positives comment since day one (March 2020), at a point that it p*** off some people here, but i’m not blind.
if a version doesn’t work, or have issues which make the software not possible to use, i tell it.
3.0. there are bugs and other issues (just found an another one, we see part of the original video on the left of the playback window, if we crop a 16/9 video), but 3.0 is a software perfectly usuable.
maybe the issues are related to the Av1 implantation, i don’t know. anyway that’s not important in itself to know from the user side “what’s the problem”. we can’t here. only devs can fix that.
I did install VEAI 3.0.0 along with existing 2.6.4, and it was okay, but after in-app-updating to 3.0.1 - did the installer take the 2.6.4 Programdata folder over?
Edit: At least not the model folder, though, I think, but 3.0.1 in-app-routine/installer wrote in “Topaz Video AI” folder in ProgramData, whereas when I “ordered” the VEAI 3.0.0 installer to use “Topaz Video AI3” one, which, at that time, it did.
Just a quick update that we’ve banned a previously frequent poster from the forum for unacceptable behavior towards other posters. This is the first time we’ve banned an active user.
We do read every comment. While the medicine is sometimes bitter, we actually love negative feedback directed towards us, because it gives us urgency and shows us how much people care about what we’re building. It is, however, unacceptable to jump down the throat of other members, for which we’ve warned this user before. This has a chilling effect on actually open discussion and feedback, so we would be negligent if we didn’t do anything about it.
Please keep the honest feedback coming, and thanks for your patience as we keep improving the product.
I might be the only other person that has not had any major issues, but I attribute that to me mostly using the CLI. I might open the GUI to check some things, but I’m not using it for much model setting tuning right now.
I really like the weekly updates. They give me hope that in a few months, TVAI will be back to the level of VEAI for most people.
My 3.0.1 works OK now, a couple of reboots later (I did reboot before my first post and tests).
The only thing I did differently today was to remove 3.0.1 from my system, then reinstall 3.0, then check that it worked as expected, and finally reinstall 3.0.1 directly from the original 3.0.1 installation file (the .msi) that I’d previously downloaded. I did not this time install it by using the “update” button that appears in 3.0.
There are of course other issues as reported by other members e.g. regarding the preview design and functioning, but I can work around them until resolved.
Speeds on the same models I have used (Chronos fast, Artemis High) with the same settings are the same as 2.6.4. Apollo is caught out less often than Chronos though, albeit it’s slower.
Good news that every comment gets attention. Bad news to make public that a poster had to be banned for whatever good reason. That can be done more elegant without announcement.
I think I found something.
So, DVDs have the annoying frame rate of 29.97. Most everything put on DVDs was originally 24 FPS, but already modified for broadcast to 23.976 FPS.
I just opened an MPEG2 video straight form a DVD and ran a 15 second preview on it with the default 29.97 frame rate. I had the preview windows set side by side. The original preview got behind quite fast and by the end of the clip was only about two thirds through.
Form that MPEG2 source, I transcoded it to H.265 at 23.967 FPS using the drop or duplicate method of frame rate change.
I then loaded that into TVAI and ran the same model and settings, but this time the preview windows stayed in sync.
I wonder if the same logic that is used to get smoother results in TVAI vs VEAI, is also what’s making the previews out of sync for so many users.
Dude, most of us have been here testing releases and reporting issues for many months, trying to help improve the application. For you to come in out of the blue and start asserting that most of the issues are ‘end user issues’ is extremely ignorant and borderline offensive.
Unless you’ve tested every beta build and early access since January, you aren’t qualified to comment on what is and what isn’t a user issue.
I’m glad that things are working well for you but do us all a favour and stay in your lane.
If they wanted to set an example for the rest of us that abusive behavior won’t be tolerated, they needed to announce it. I think it was the right decision, but it’s just my opinion.
if my memory is correct, the allow recovery button in the preference is there for that, same with the videoai tag in each videofile. so this feature is scheduled at some points, but as a user like everybody else here, i can only tell what i know or learned, and not when it will be there. so we’ll know soon i hope !
!