It would normally be easy to fix with for example -vf “colormatrix=bt470bg:bt709” for SD , but the problem is that you can’t mix -vf with -filter_complex in ffmepg it will just throw an error.
The “-filter_complex” is a combination of “-vf” (Video Filter) and “-af” (Audio Filter) and means the same thing.
If you want to chain to veai filters, simply set them separated by commas.
VEAIfilter Example
“-filter_complex veai_up=device=-2:model=prob-3:scale=2:compression=0.24:details=0.24:blur=0:noise=0.12:halo=0:preblur=0”
VEAIfilter → bt470bg to BT709
“-filter_complex veai_up=device=-2:model=prob-3:scale=2:compression=0.24:details=0.24:blur=0:noise=0.12:halo=0:preblur=0,colormatrix=bt470bg:bt709”
bt470bg to BT709 → VEAIfilter
“-filter_complex colormatrix=bt470bg:bt709,veai_up=device=-2:model=prob-3:scale=2:compression=0.24:details=0.24:blur=0:noise=0.12:halo=0:preblur=0”
Hi Ida, happy to report that this is MUCH more stable. I was not able to make the GUI disappear irretrievably even after 15 minutes of min/max/move across screens, etc. Also, choosing Close from the Task Bar button does indeed now close the app. Nice.
Still a few smaller glitches:
- Doesn’t play nicely with auto-hide Task Bar. Prevents it from arising via mouse pointing at bottom of primary screen as per normal Windows behavior. It DOES play nicely with a permanent (non-hide) task bar now.
- Some odd min/max behavior. Sometimes and I haven’t been able to work out the pattern triggers:
a. You have to click the Unmaximize button twice to actually unmaximize… the first click does nothing. Other times it works on the first click.
b. Clicking the app button on the Task Bar when the app is minimized does restore the GUI on screen, but always in Unmaximized mode. It should restore to the previous display mode, which might be Maximized as per standard Windows behavior.
c. When the GUI is on screen, clicking the Task Bar app icon does NOT minimize the GUI as it should per standard Windows behavior.
I can confirm that the normal shortcut menu for the app off the task in Task Manager is also now back to its normal self.
I also just updated my RTX 3060/12Gb NVidia video drivers from 512.15 to 517.48 (released a few days ago), and confirm exactly same behaviors as above.
Thanks.
I know thin scroll bars are fashionable in UI-land these days, but atm the RH scrollbar active width is about 5 pixels on my 4K monitor and when the GUI is unmaximized, you almost always get the window resize control, not the scrollbar control. Really hard to get hold of it.
Also, neither the pointer nor the scrollbar change appearance when you are correctly pointing at it, so you can’t reliably tell if you are or not. Standard UI behavior is for the “selected” portion of the scroll bar to change brightness (up or down), when the bar is pointed at.
1 Like
I can also confirm that the Export button now works in this alpha, producing output files.
@ida…
-
Oh, I was doing modest trims and didn’t see that behavior. It makes sense, thanks.
-
I’m proposing (for later) a zoom lock button that locks ALL previews to the same zoom, frame positioning, and split line position. This is because you want to COMPARE various Previews and they keep jumping around when you move from one to the other. Especially hard when you’re trying to balance improvement versus artefact in specific areas of the clip.
-
I confirm that the x2 models do a MUCH better deinterlace job, but I still don’t want to wait four times as long while it UPFRAMES to a fps I don’t want and then DOWNFRAMES it to my original.
-
Can’t remember what that was…
-
Thanks.
-
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).
2 Likes
Hi! That alpha version was only built to make sure the fix for the GUI crash is working for everyone running into that issue.
Hi
I still stuck with this error: Video AI 3.0.0.9.b - #109
Can you help me? This happens even from the shell opened through the gui 
[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!
@ida.topazlabs are we past Alpha?
Can VEAI add meta inform info. photo AI and other Topaz Photo to use to process like the raw and Jpeg files found in cameras?
Helllo,
I am currently testing in VEAI 3.0.0.9.b beta. It was suggested that I test TopazVideoAIAlpha-3.0.0.69a1 in regard to seeing if the GUI in that version was more stable.
I have no objection to doing so but have a few questions first.
- Can I have both of these installed on one system at one time without creation difficulties due to version skew?
- Are the other modules used in TopazVideoAIAlpha-3.0.0.69a1 newer or older than those in VEAI 3-9b?
Please RSVP so I can proceed accordingly. - Thank you!
you’re late ! the early access 3.0.0.7 has already been released this night !
I’m attempting to upscale 720x480 to 1440x1080 using “select width and height”. Everything looks good until I hit the export button, then my original video resolution changes, it shows up as 568x480.
I don’t think you can x2 one side and x2.25 the other. Even if you could, you’re going to stretch the video.
I agree that the GUI cannot do as much as you can by running FFMPEG directly from the command line. What the GUI is supposed to do is compose a command line to run the job through (VEAI’s) special FFMPEG. - The problem as I see it is that the GUI doesn’t have a robust set of rendering options available. - That is a weakness that makes the GUI less useful than it should be.
In my opinion: The number of rendering options in numerous categories available directly from the VEAI GUI needs to be filled out significantly.
Sure, we could always copy the basic ‘command line’ settings that the GUI creates, and edit in our preferences and then run it from the command line, but that really diminishes the usefulness and value of the GUI which, in effect, defeats its primary purpose.
4 Likes
Doe the resize option you’re using allow you to specify black bars? If not, you’re using a resize option that won’t fly. - The rescale using “width and height” is potentially problematic from the outset.
Thanks for the suggestions. I just dropped the 720x480 file in and selected a straight 225% increase, and it once again changed my 720x480 to 568x480. The input stays correct until I hit ‘export’, then it makes the change and begins exporting. Weird.
1 Like
I have seen this with a lot of 4:3 videos and I think it’s just the software giving more specific info about the size of the video, as some videos are usually given what I think is a more generic size (ie 720x576 or 720x480, etc…) when in fact the size isn’t always as exact as that?
Sorry if some of that might sound confusing but I’ve just woke up and not got my thinking cap on yet to be more specific with my worrds.
1 Like
I deinterlace in hand break in handbrake then enhance upscale in Topaz. Good results.
“Export” and “export as” work for me with every output but TIFF and PNG-nada nothing. I"m on a beefy intel Mac.
It works for my on my intel Mac but not for TIFF or PNG export
