The new GUI is starting to grow on me.
A suggestion for the filters/options on the side bar:
Only allow expansion of one filter/option at a time, by clicking on the filter/option text label. We can see that any particular option has been turned on by the slide indicator but we don’t need to see all the details unless expanded. If you enable one and click on something else, the one you were just on automatically collapses.
This should deal with all the excessive scrolling concerns.
Running an i9-10900k CPU, an Nvidia RTX 9080 and 32GB memory overclocked, I was able to render a 19 minute 29.97fps video from ST to FHD at the rate of 2.4 fps using Proteus Auto.
More than 4-1/2 hours for mediocre results.
Re: Stabilization
I did some further tests and came up with the following
As far as I have been able to tell 3.0 is not using the GPUs fully yet. Here is my test with times that show this. https://community.topazlabs.com/t/video-ai-3-0-0-0-b/33157/308?u=mikef
In the VEAI 3.0 Back to the Future posting suraj mentions this is section 2:Workflow. I have looked through the change logs and have found nothing indicating that has changed.
https://community.topazlabs.com/t/veai-3-0-back-to-the-future/29931?u=mikef
What is obvious to me is that that will change at some point but not right now. I would not be using the beta for final work but just to test function and quality and report those issues. The GPU utilization/optimization has to happen for there to be a release version or they will have a product that will not be excepted.
The proteus auto slider for antialias/deblur only goes from -100 to 100, but the non auto slider already goes from -100 to 100, thus the auto slider should go from -200 to 200.
Set the model to auto and put one slider to 50. then switch off Auto.
you’ll see that the slider stay at the number you set up in auto (50).
I assume that the negative part only work when auto is set, as a reduction but not sure about that, as when switching off the auto button, it can’t go under 0 except for the blur/alias one.
This issue comes up often. No, it doesn’t use the GPU fully. They claim it will eventually.
Hi,
I am using the Microsoft Films & TV application to preview the output. But the video playback is stutering a lot.
The motion rendering is not good I think so.
Yours.
Vincent.
That app is junk. Don’t use it for anything.
Hi,
Normaly I experienced never issues with this application.
I shall make a try with VLC anyway.
Vincent.
I doubt it will make a difference with the video in question, but that app is junk either way.
@nipun.nath
Can you confirm the arrival in the next beta of the ability to change the bitrate to the AAC audio track converted by the program?
There is definitely a problem with the exported video (mp4 and mov). Beside not playing well on apps like Microsoft Films and Tv (which VEAI exports usually work fine on), I am unable to import the exported videos into Vegas Pro and I get a lag in response time when playing on vlc.
Hi, this need more investigation, please, give me some time to check the vegas pro part (i use and own Vegas Pro since a very long time , and use version 19 (last build), don’t know yet if i’ll upgrade to Vegas 20 (out next monday).
I just tested this :
i test both videos in MPC-BE (fork from MPC-HC), VLC, Film and tv app from microsoft, Gom player plus, Vegas Pro 19.
Result for VEAI 2.6.4 video : no problem at all with any of the softwares.
resultat for VEAI 3.0 : work fine in MPC-BE, VLC, Film and tv from microsoft, Gom player plus, but got an issue with vegas pro 19.
the file is imported with wrong information, one frame is imported (on a 2 seconds rendering) only and with a framerate of 60fps. worst, ratio is not respected.
i’ll redo a longer and another test, with the same source, and with an another one to see if this issue can be duplicated and give the same problem again in vegas pro. but with all the other softwares, i don’t have issue (but it was a 2 seconds clip).
While you’re at it, you may try a PotPlayer - a much nicer interface (IMO). It’s included in LAV Filters megamix too. I personally download them from free-codecs.com - a lot of great stuff there. I’m not affiliated with both in any way.
Seeing the same thing with my test outputs: audio/video out of sync, video freezing while audio continues. This is with VLC so not player related.
Thanks David. I appreciate your confirmation about the problems I’ve been having with the output files.
Couldn’t agree more, my CPU and GPU utilization isn’t really even going beyond 20% and export times are currently way too slow. Even if everything else was perfect right now, we really need MUCH better hardware optimization to take better advantage of our hardware and get the lowest export times we can since current speeds could mean a brutal slowdown of our workflow.
Besides enthusiasts, the biggest market they have are professional users who want to integrate this into their workflow and we need something efficient and reliable to make it happen. If they manage to just take care of optimization and the handful of remaining bugs, they’ll be seeing a swarm of new customers who are interested in purchasing licenses for their software.
Very nice detailed reply Martyprod. Thanks.
Some comments:
-The video I tested was 10mins long. Although it does play on Microsoft Films and Tv, I cannot fast forward (eg moving from start to 5min to 6min, etc). With vlc it will freeze at times and I have to restart vlc player to get it to work.
-Let me know if you can import it into Vegas Pro 19. Mine is Vegas Pro 18 and it will not import into that.
-As you said, no problems playing with VEAI 2.6.4 or importing into Vegas
Re: Stabilization: Another weird problem
I tried stabilizing an mpeg2 video and it did a decent job except for the automatic cropping and zooming but there was some interlacing (I did not deinterlace the original file).
I decided to deinterlace the original mpeg2 file with VEAI 2.6.4 and then import into the beta 3.0.0.1.b for stabilization. Strangely VEAI could not stabilize the deinterlaced video. The resultant file was the same as the shaky original even at 85 strength.
Not sure why the stabilizer will only work on certain files. In this case it would not work on a file deinterlaced by VEAI itself.
