Video AI 3.0.0.9.b

david.counts · October 6, 2022, 5:02am

It actually doesn’t work for me when attempting to output to TIFF or PNG other outputs are fine

paulwinex · October 6, 2022, 10:48am

I solved it!

env variables is not works.
I added paraneter “-v verbose” to ffmpeg command to see more error details. Main error was: “model not in list”
I copied all json and all tz files to main installation dir: [VIDEOAI_INSTALL_DIR]\models and remove readonly attribute. Create this dir if not exists. Source files are located in c:\ProgramData\TopazLabs...
Make sure the work directory is Topaz Installation dir (with ffmpeg.exe file)
Run the command

TicoRodriguez · October 6, 2022, 12:55pm

Considering that even VEAI 2.6.4 was supplemented by Avisynth and others, I am not sure how much is required in the basic functions of 3.0.
I think it’s okay to delay updating the GUI somewhat if it can be solved with the CUI.

I’m concerned about is that they are only advancing the GUI enhancements and not making much progress in updating the VEAI core and AI model.
I even suspect that they are leaving bugs in the GUI on purpose to buy time because they can’t update the VEAI core

sbstn · October 6, 2022, 4:12pm

When I move the program window to the top of the screen then the window does not maximize. I always have to click the maximize button in the upper right corner.

And a setting for the amount of created keyframes would be good for lossless cutting in avidemux.

lee.keels · October 6, 2022, 4:16pm

It doesn’t use the standard Windows controls, it’ll never work that way.

ssbroly · October 6, 2022, 4:24pm

Ce serai cool que qtgmc sois intégré avec un réglage personnalisé de dehalo aussi

pdwhite · October 6, 2022, 4:53pm

Ida,

I would like to test this new GUI. However, I am awaiting an answer. Is this Alpha version going to cause version skew problems when installed on the same machine as VEAI 3.0.0.9.b?

Please let me know.

Phil White

gregory.maddra · October 6, 2022, 5:34pm

Hi,

The alphas are versioned separately from beta and EA builds. However, the changes being tested in that alpha have already made it into the newer 3.0.0-7 early access build.

pdwhite · October 6, 2022, 5:43pm

Can the latest beta and an EA build co-exist on the same machine?

Martyprod · October 6, 2022, 5:44pm

YES !!!

pdwhite · October 6, 2022, 5:44pm

OK.

myerpj · October 6, 2022, 8:33pm

@ida.topazlabs

I really agree with what @neil.francis-2548 said (also below), The Dione 2x deinterlace was doing really good with the DeInterlace and then some Enhancements. I managed a quite good export in .07, from SD 3/4" to ProRes to VEIA to HD-1080p ProRes and h264. I was quite happy with it. Now, I get significant artifacts with just deinterlace to ProRes, and then that ProRes enhanced to 1080p on a second pass. ProRes is visually lossless, but it’s getting hammered in the second pass.

Please put back the DeInterlace WITH enhancements.

neil.francis-2548:

The Dione processes do deinterlace but do NOT improve the image. Up to Beta 6 (I missed 7 and 8), I could happily Deinterlace well, stabilize, AND apply some Enhancements. (Just that the stabilization itself wasn’t great at the time.) Now I get great deinterlacing and stabilization but not better image quality. I don’t want to choose, and I’m not using CLI to do it, nor multi-pass lossy file runs. If it’s interlaced, stabilizer does NOT work effectively because of the motion tooth-comb effect. So I’m not sure what your remark “too many issues with both processes” means because they ought to be sequential pipes (without lossy file saves in between). If stabilizing interlaced source, then good deinterlace must ALWAYS be first, piped to stabilizer, piped to Enhancements (piped to Chronos if you’re doing that too).

myerpj · October 6, 2022, 8:44pm

BTW: The interface does last better in alpha thanks!

myerpj · October 7, 2022, 3:22am

I have a 10 sec clip in ProRes that I use test. The preview didn’t appear in an h264 test, but displayed when about 2 seconds of video was completed exporting to ProRes LT

void778 · October 7, 2022, 11:47am

I can second that. Neither “Export as”, “Export” or “Ctrl+E” nor the dropdown menu “process → Export” results in any output. I can easily preview and fill my preview job list all I want, but I cannot get 3.0.0.0.b to create any exports, not even a listed job in the Export queue or a file on a drive.

Also, if I choose “Show Preview command” i get the pop-up window containing the FFMPEG command line, but if I choose “Show Export command” there is not even a pop-up window

Martyprod · October 7, 2022, 1:11pm

it seems your issues have been fixed in the last Early access version (3.0.0.7) as said by the change log posted tuesday.
As the new 3.0.0.10b beta will be released today, best suggestion is to wait it as it will have all the fixes from the last Early Access.

bramachandran · October 7, 2022, 3:26pm

Hi there:

Hope you are are doing well. We are facing performance issue in Foundry|Nuke13 when loading .mov file generated using GUI and .mov generated using ffmpeg from cmdline. We noticed that .mov file generated using GUI load much faster than .mov files generated from ffmeg from cmdline.We were able to narrow it down to metadata length .

FFMPEG command where -metadata length=“00:04:05” does not work, but at the same time, when we simplify the command, the same -metadata length=“00:04:05” starts to work. It has to be something very simple. Maybe something like addition of “use_metadata_tags”, “–map_metadata:s:v”, etc

ffmpeg -y -i source_file -metadata length=“00:04:05” -map 0 -c copy output_file

Any help as to how to add this metadata length would be much appreciated.

Thanks
/Biju

void778 · October 7, 2022, 8:43pm

If 3.0.0.10b is to get out today, I’ll just wait and test my luck. Otherwise, I will have to reinstall 3.0.0.7 again it seems

Martyprod · October 7, 2022, 8:51pm

just wait, all betas are released each friday. it will be available in a couple of hours more or less.

Martyprod · October 7, 2022, 10:20pm

10b is available.