Video AI 3.0.0.2.b

Should I update the ffmpeg.exe file in the Beta folder or stick with the one provided?

Maybe you could allow users to rearrange the filters on the right side, and even allow removing unused filters or using one filter twice.

Please ADD this request =

:heart_eyes:

1 Like

lol,
1/ when we had VEAI 2.x.x, they put CRF in at some point. lot of people complained about it, and wanted the fixed bitrate back (by entering the fixed Mbs) (me included). they did it on 3.0 and now people ask to have CRF back lol.

2/ if my understanding of Ffmpeg is right (not sure), the two way to compress the result is already possible, just have to copy the cli command provided by VEAi, and change it the way you want to have it like you want. VEAi is just a plugin for ffmpeg with a Gui. it provide the models calculation while everything else (resize, encoding, import and export video) is managed by ffmpeg. (i’m not an expert , i can be wrong). the only difference is what you request, is certainly there but is lacking of a Gui button or something like that. that’s why the 3.0 has been redone from scratch and based on ffmpeg. because it was much easier to implement new stuff, fix them too, and as well add new feature (like VEAI will be at some point a ā€œpluginā€ for some video editors, certainly premiere pro and davinci (others i don’t know), like gigapixel, and others are a plugins for photoshop.

Then at this point, just add the CRF option in the VEAI GUI in addition to the bitrate choice, and we’re all happy (it doesn’t seem like an unreasonable request, on the contrary)!

4 Likes

It may make sense, but only precisely if you wish to achieve a specific final video size.
Otherwise, the ā€œqualityā€ based encoding mode (such as precisely CRF or CQP) is the best choice to have a video file optimized in the final quality/size ratio.

1 Like

i’m pretty sure that this feature will be implanted at some point, many people want both. the fps/spf switch has been implanted in the preference, so it could be the same for this, same for the timecode/number of frame too.

2 Likes

Can’t use x264 and x265 in either 2.6.4 or 3.0 beta, is it a licensing issue?

One of my PC’s is Ryzen & Radeon so cannot use NVENC and QSV.
As for AMF… I don’t want to use it for image quality.

If x265 could be used, I could share the encoding settings with another PC, but is that impossible?

When I try to run FPS convert via the FFMPEG command and specify -vf or -filter_complex with
veai_fi=chf-3:fps=60:device=0:vram=1:instances=1 or
veai_fi=chf-3:fps=60:device=0:vram=1 or only
veai_fi=chf-3:fps=60

neither one of those works (veai_up works flawlessly!). The error message is:

[veai_fi @ 000001FDD6E87840] Unable to parse option value ā€œ0ā€ as video rate
[Parsed_veai_fi_0 @ 000001FDB66DF340] Option ā€˜instances’ not found
[AVFilterGraph @ 000001FDD6E85740] Error initializing filter ā€˜veai_fi’ with args ā€˜chf-3:fps=60:device=0:vram=1:instances=1’
Error reinitializing filters!
Failed to inject frame into filter network: Option not found
Error while processing the decoded data for stream #0:0

What could be the reason for this, @suraj ?

@suraj Pleas Help! No matter what I try to do I always get this:

st: 0 edit list: 1 Missing key frame while searching for timestamp: 0

st: 0 edit list 1 Cannot find an index entry before timestamp: 0.

Guessed Channel Layout for Input Stream #0.1 : 4.0

Input #0, mov,mp4,m4a,3gp,3g2,mj2, from ā€˜/Users/joe/Premiere Temp/IMC_A_0239.mov’:

Failed to configure output pad on Parsed_veai_cpe_0

Error reinitializing filters!

Failed to inject frame into filter network: Invalid argument

Error while processing the decoded data for stream #0:0

Doesn’t matter what files I choose. Is there a way I can reset my preferences?

This happens with everything I do. Did you find a solution? The ā€œAudio Transcodeā€ on/off doesn’t seem to fix.

@yazi.saradest The stabilization ā€˜filter’ is still delivering sub-par results. I did a dropbox upload of a comparison of Adobe’s Warp Stabilizer, and the VEAI Stabilization feature. The VEAI version breathes in and out and many areas of the image wobble/change perspective, yielding an extremely unnatural result.

if my memory is not that bad, i remember suraj telling that the Warp stab from adobe was better, but the way stabilization is made in VEAI will lead to a better result in the future (but for that they need to train the model to improve it). that’s where the release of 3.0 quick is important. we’re close to almost a year without any models improvements (i forgot appolo !) don’t know about all of you guys, but i’m quite impatient :wink: lol.

1 Like

I fixed this by resetting the models (data) directory in prefs

Totally agree. It is not clear how the filters work, which ones are AI, and even what order they execute. I get that it is designed to be simple, but it is actually quite confusing.

Execution is in menu order, top to bottom.

in case anyone missed it, this has moved to early access and today’s build is posted here: https://community.topazlabs.com/t/topaz-video-ai-early-access-v3-0-0-0/33949

1 Like

is that version the same as this alpha version?

No, it was posted today

This topic was automatically closed after 17 minutes. New replies are no longer allowed.