V3.0.1 Processing Error on Preview - Click on the Red icon in the output list to read the error message.
There is no Red icon.
OK after more searching I need to update my NVidia Driver - I had v512 from May 22 and the prgram wants version 5.20 or newer. I’ll test that now.
yes, just noticed that. i’m using a RTX A4500 but last driver update are 517.40 lol. so can’t use the 3.0.1 for now. must wait nvidia update their driver for this brand which is different than the geforce one.
from what i could read on the log, they updated the minimum use for cuda to 12.0 in 3.0.1 while 517 driver use 11.1
hope Nvidia will update their driver quickly ! 3.0.1 doesn’t have error on my 1050ti which have 522 last driver fortunatly.
I just updating to version 3.0.1 and I have new issues:
-If the newly imported video is trimmed, no preview or export possible. Clicking button will just make the picture blink for a millisecond then nothing happening. If export as is choose, then the export screen appear but nothing happen after clicking the save button.
-If no trim is done at first, the preview button is possible to be press. When clicking it, the preview try to process but after like 2-3 min, the app crash.
Conclusion, 3.0.1 unusable for me.
BUG: If I select stabilization with rolling shutter, the result is just a completely washed out screen, pretty much a couple of hues that were in the video. Happened with the initial release and this one as well.
Edit: Forwarding through my processed video, I see this happening with the stabilization choice to reduce jitter also, it just takes longer to occur.
I tried reprocessing my video in handbrake and ffmpeg to make sure my source was not the issue.
Just to give some confirmation: the minimum NVIDIA driver version is 522.25. We’ve updated some of the hardware encoders in this release. Apologies for missing it in the initial release notes, I’ve updated the top of the thread to mention it.
Funny, they still have the bug when you click on the preferences window it activates the load media action from the screen behind it if you didn’t click specifically in one of the buttons in the preference page… you would think someone testing this would notice and correct it at some point.
It’s quite clear that in house testing doesn’t actually cover USE of the product as a normal user would. A significant amount of the annoyances couldn’t possibly get through if they did.
Clicking in Topaz 3.01 to “show in Explorer” only seems to work when the file is completed, not when it is in progress:
Is this an expected action, can it be updated to do two things:
Show you where the temp file is being built so you can confirm/monitor your free space in the temp drive?
and/or to reveal in finder even if it’s an in progress file, or at least tell you why it can’t reveal it so you know vs thinking its doing nothing?
frankly I will never use this new version which is really horrible sorry to say. it’s always full of messed up things. let’s all get back to 2.6.4 to show the VEAI team that they have to continue following this version 2 which will always remain the best and that they have to stop the production of version 3 seriously. Let’s all be strong and together to tell the team to continue version 2. wake up people and stop saying that version 3 is good, you can see that it hasn’t been good as a version since its creation. this version 3 is a big regression of VEAI that we knew before, version 2 will remain the best. let’s all be together to tell them to continue version 2 and if they don’t want to, well we too will stop paying for the license simply because they don’t listen to their customers. because it is we who pay as far as I know. my post is not offensive it’s just to wake up some people who haven’t opened their eyes yet.
As bad as 3.x is, there were things in the code for 2.x that prevent taking it much further. I just wish they’d take a hard look at the mess that 3.x is, back up, and methodically fix it, starting with the annoyances that any basic QA could have caught, and then LISTENING to user feedback by way of a JIRA.
I agree with you, because from the beginning they don’t really listen to us so that version 3 is correct. How many times have we told them to speed up video encoding for export? in the end it is always very slow. how many times are they told to solve the problem of this version 3? in the end, well, not much to settle. I say even if they make this version 3 that they continue on the other side version 2 for those who use it. I think version 2 may have new options I’m pretty sure.