After doing a Proteus preview on Auto and then switching to Relative to Auto preview froze up, zero entries or not… It was necessary to exit VEAI, restart the app, then go directly to Relative to Auto in order to do a preview.
BTW: Considering the poor input I’m feeding Proteus, it is doing a remarkable job of enhanced resizing. There are still some problems, but the image in general is cleaner and clearer. 
People couldn’t understand it the way it was and kept complaining. This is what happens when there are too many voices.
I can confirm that changing from a 2-step stabilize to a 3 step stabilize with Rolling Shutter Correction and Reduce Jittery Motions both on, Auto-crop mode, stops the minor pixel repetition artefacts at the edges of the frame. They were most notably on the RH edge of mine. The stabilizer does a good job on severely bad footage (12 year old consumer cam at max zoom hand held on the back of a jeep with people moving about). The only remaining minor is a slow wave from movement of the camera’s IBIS. But the effect is minor and slow, and the subject of the footage (a cheetah up a tree) is now well observable whereas with the original you had to “imagine” a lot of it.
Now, just to put the deinterlace back in its own section so the best deinterlace can be selected AND enhancements can be applied after stabilization.
Processing with these settings is mighty slow, but for small clips that need savage correction, it’s doable.
Minor cosmetic problem: can’t reproduce reliably, but at some stage while playing a Preview, the RH pixel column of the video gets played in the vertical divider bar between the video and the controls on the RHS.
Don’t understand: When you select 2-pass stabilize, the Preview calculation status shows “1/2”. When you set it to 3-pass, it says “1/2” not “1/3”. Not sure what this means.
I can confirm in 2009b that not only does the Export button do nothing, but choosing Export As… and entering a file name / OK also does nothing at all. There is no indication of any processing and no output file is either created or even locked for writing. Task Manager shows that ffmpeg has NOT been launched.
seems this “issue” doesn’t affect everybody. 3.0.0.9.b is working here, export button work, export saved where it must be. Export As button is working as well. Intel H264 new codec export work too.
there is certainly a common point between you and the ones who have this issue. did you had the “model folder” issue like some other people ?
When you’re comparing Previews in Split mode (original on left, processed on right), when you click between one Preview and another, the split bar is reset to halfway across the screen. Also, sometimes but inconsistently, it repositions the video content centered in the playback frame. Can the split bar and frame position please stay fixed for each Preview?
Later feature request: (AFTER the app is made reliable) Implement a Preview LOCK button that sets all Previews to the magnification, frame position, and split bar you’re currently working with. That would make Enhancement parameter testing workflow much faster and easier, to achieve maximum enhancement with minimum artifacts.
3009b still is unreliable re GUI behavior and disappearing. It opens full screen even though the full screen window option is not selected. Clicking full-screen button results in no change, other than the Maximize icon changes to an Unmaximize icon. Clicking that does nothing at all. It says full screen.
Coupled with the GUI randomly disappearing even though it’s still running, and the fact that it also totally HIDES Task Bar, it’s VERY badly behaved. The Task Bar is pushed off screen whether or not it’s auto-hide or permanent. Seriously bad app behavior.
While testing this functionality, which required minimizing the 3009b window so I could use the Task Bar, after several minimizes, maximize now doesn’t work at all. Like 3006b (the last beta I tested), VEIA beta is now invisible and cannot be seen on screen AT ALL by ANY MECHANISM. Since 3006b, even the last resort, Maximize off the app’s shortcut menu in Task Manager, is no longer available. For some inexplicable reason, another completely different shortcut menu is now shown and it doesn’t have Maximize on it. It’s now WORSE, not better than before.
Right-clicking the app icon in the Task Bar and choosing Close does nothing at all. This is more seriously bad app behavior. You have to go kill of the app in Task Manager.
Now on relaunch, the GUI is still completely invisible and unusable. So I’ve uninstalled it and I’m not going to do any more beta testing until you fix this disaster properly. Please make the very basics play nice before toying with more nice-to-haves.
Please stop wasting your beta testers’ time. I vote that this is your one and only TOP PRIORITY for the next beta. Get the fundamental GUI stable: if you want us to look at it, make it reliably look-able at-able.
I also recommend that you write a small “cleaning” app for beta testers and users that thoroughly, reliably, 100%, uninstalls the Beta (but doesn’t touch 2.6.4 which is still working great) re ALL files (including dumps, configs, etc), folders AND Registry, so that we have clean machines to test a Beta install on without tons of manual labor and iterative comms with the devs or support.
Please advise directly if/when you have a stable GUI. THEN I will return to beta testing.
I see attempts to make the UI better, but sometimes they fall rather flat. like they are in need a good UI person. For example, the timeiline trim mechanism in 2.6.4 is great. The 3.x beta mechanism is far less intuitive, it’s clunky, harder to use, less accurate, and more jerky.
Re the Enhancement adjustment types, the labels are incoherent… “Auto”, “Relative to Auto”, “Manual”. ANYTHING that’s not full auto is manual! That is, “Relative to Auto” is also “manual” because there are controls (not present in Auto) and you manually twiddle with them.
These would be more obvious labelled “Full auto”, “Auto adjust”, and “Fixed”. Because that’s what they do, especially via the values on the sliders that show when you choose the mode: -100/+100 with 0 in the middle for “Auto adjust”, and 0-100% for “Fixed”.
I would also argue that there’s plenty of UI room to present these three options as a single row of buttons, active one highlighted. That makes the entire MENTAL SCOPE of the three forms of control immediately obvious, and changing is ONE click. A dropdown is NOT natural UI furniture for changing the current display (show/hide sliders). Tabs or buttons are the natural UI furniture for changing UI subspace (ie what’s presented under it). Given one of the options (Full auto) doesn’t have subspace, I’d argue that a set of buttons would look better than a set of tabs, one of which would be empty.
With a dropdown, first you have to NOTICE it, because only one item is shown and it doesn’t stand out. THEN you have to DROP DOWN the menu to see what’s available. THEN you have to examine the options and form a mental picture of their relationship (because it’s a vertical list of text floating in space rather than a horizontal row of buttons naturally FRAMING or HEADING the slider space below). THEN, having formed a mental picture, you have to click the option you want, or to dismiss the dropdown.
So, three well-labelled, permanent buttons visually and mentally scopes the options, frames or heads the following content (if any), and allows option selection with one click. That’s it. Most of the hard work is done at the design stage rather than by 1000s of users at run time.
(And the “Fixed” option includes a button [ Suggest settings ] that parses a bit of the input clip and sets the sliders to some useful values.)
Yes, I had major model folder problems like others.
Still in 2009b, the folder selector window is obviously NOT using regular OS calls to present drives (re SUBST and network-path ones not found), and it doesn’t properly select the folder when you click on it: you have to actually OPEN the folder for its name to be selected. I missed this and got Gb++ of models loaded onto a drive’s root folder before I realised and cleaned it up.
Never mind the bottom post, I fixed the problem, it was embarrassingly simple…
For me, I have yet to fix the install’s progress, as it’s always getting stuck at the “Removing shortcuts” section of the installation…
Any clues to what’s causing it? Thanks in advance for any insight you may have!
@gregory.maddra Some good testing tools:
Omni Scope
Remap
Display
False Color
Not Promoting these but These do well with color.
I got better results with v08 and below, when I could deinterlace and add artemis or proteus to it in one pass. Now, having to delinterlace, then add one of the other options requires me to send the 1st processed clip back into veia. I hope this was an error when moving the menu items around on this build, and we get back deinterlacing (dione 2x) with an enhancement.
And would really like to see the most recent video preview or export to appear back on top while we wait for an option to set it ourselves.
First.
I wrote display/overlay.
Second.
Since the ffmpeg filter is robust enough to do the heavy upscale, adding information about its parameters or adding Topaz logo is fine.
Hi
I try to use cli for video processing.
First of all i reproduced required actions with GUI and result is OK.
I was copied ffmpeg command and put it to a script convert.cmd for Windows.
@echo off
cd "C:\Program Files\Topaz Labs LLC\Topaz Video AI BETA"
set VEAI_MODEL_DIR="C:\ProgramData\Topaz Labs LLC\Topaz Video AI BETA\"
ffmpeg ^
-hide_banner ^
-nostdin ^
-y ^
-nostats ^
-i "C:/Users/paul/Desktop/render_src.mp4" ^
-vsync 0 ^
-avoid_negative_ts 1 ^
-color_trc 2 ^
-colorspace 2 ^
-color_primaries 2 ^
-filter_complex "scale=in_range=limited:out_range=full,veai_up=model=ahq-12:scale=0:w=1800:h=1800:device=0:vram=0.9:instances=1,veai_fi=model=chf-3:slowmo=2:device=0:vram=0.9:instances=1,scale=w=1800:h=1800:flags=lanczos:threads=0" ^
-c:v h264_nvenc ^
-profile:v high ^
-preset medium ^
-pix_fmt yuv420p ^
-b:v 7.5M ^
-map_metadata 0 ^
-movflags "frag_keyframe+empty_moov+delay_moov+use_metadata_tags+write_colr " ^
-map_metadata:s:v 0:s:v ^
-an ^
-metadata "videoai=test" ^
"C:/Users/paul/Desktop/render_output.mp4"
And the script are crash with error
[Parsed_veai_up_0 @ 000001C6583ADEC0] Failed to configure output pad on Parsed_veai_up_0
Error reinitializing filters!
Failed to inject frame into filter network: Invalid argument
Error while processing the decoded data for stream #0:0
Conversion failed!
The same configuration works from UI but CLI is crashed. Perhaps an error in the configuration of environment variables?
Shouldn’t it be
VEAI_MODEL_DIR=“C:\ProgramData\Topaz Labs LLC\Topaz Video AI BETA\models”
And check if the json files are there.
I tried with \models, it is not helps. JSON files exists. Same error.
Hi, could you try opening the CLI using the button in the Process menu? That option should automatically set both VEAI_MODEL_DIR and VEAI_MODEL_DATA_DIR correctly.
