I tried again with my Ryzen, and …no way with 3 on parallel when output is *.mp4! But, surprise surprise with one going to *.mp4 I can run 2 more in parallel going to *.TIFF. So, please look into resource management of VEAI to fix this mp4 deficiency.
For the past several builds of this I am not able to change the frame rate at all. It immediately throws an error on any video. This is on a Mac Studio. On my windows machine it seems to work fine. This is the error. Any ideas?
w:720 h:480 pixfmt:yuv420p tb:1/30000 fr:30000/1001 sar:8/9
Setting ‘pix_fmts’ to value ‘yuv420p’
Setting ‘pix_fmts’ to value ‘yuv420p’
w:iw h:ih flags:‘’ interl:0
auto-inserting filter ‘auto_scale_0’ between the filter ‘graph 0 input from stream 0:0’ and the filter ‘Parsed_veai_fi_0’
w:iw h:ih flags:‘’ interl:0
auto-inserting filter ‘auto_scale_1’ between the filter ‘Parsed_split_1’ and the filter ‘format’
w:iw h:ih flags:‘’ interl:0
auto-inserting filter ‘auto_scale_2’ between the filter ‘Parsed_split_1’ and the filter ‘format’
query_formats: 7 queried, 6 merged, 3 already done, 0 delayed
Output size set to: 720 480
Here Config props model with params: chr chf-3 1 -2 1 1 720 480 0.000033 29.970030
w:720 h:480 fmt:bgr48le sar:8/9 → w:720 h:480 fmt:yuv420p sar:8/9 flags:0x0
w:720 h:480 fmt:bgr48le sar:8/9 → w:720 h:480 fmt:yuv420p sar:8/9 flags:0x0
cur_dts is invalid st:0 (0) [init:0 i_done:0 finish:0] (this is harmless if it occurs once at the start per stream)
nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 0
Process frame 0.000000 on current 1 at 0.000000
2022-09-24 09-26-36
Added frame at pts 3003 0.100100 1
Process frame 0.499501 on current 1 at 0.499501
My Windows 10 Pro 64bit desktop has only one user logging in - me and I have administrator status.
However, I just found that I needed to change security permissions on
C:\ProgramData\Topaz Labs LLC\Topaz Video AI BETA
I added my username to have all security permissions but those permissions were already there for all users and admin etc.
Before changing folder security;
Model Not Found for Theia
2022-09-24 14-34-25 Thread: 22808 Debug Updating video info {“sar”:1,“framerate”:29.96853645059674,“startNumber”:1,“frames”:300,“progress”:0,“status”:2,“frame”:0,“procStatus”:{“status”:2,“eta”:0,“fps”:0,“message”:" Model Failed",“pass”:1,“error”:“”,“progress”:0,“frame”:0,“priority”:3,“requestPos”:5,“processorIndex”:0}}
2022-09-24 14-34-25 Thread: 22808 Info OUT: 8 2022-09-24 14-34-25 Thread: 29288 Critical Loading default error reading file: “C:\ProgramData\Topaz Labs LLC\Topaz Video AI BETA\models/thd-v3-gnet-fp32-288x288-4x-ox.tz”
:AIERROR: Model Failed
2022-09-24 14-34-25 Thread: 29288 Critical Unable to create or load model of type ONNX from path: “thd-v3-gnet-fp32-288x288-4x-ox.tz”
2022-09-24 14-34-25 Thread: 29288 Critical BackendRunner cannot be initialized for model: “thd-v3-gnet-fp32-288x288-4x-ox.tz”
2022-09-24 14-34-25 Thread: 22808 Debug Updating video info {“sar”:1,“framerate”:29.96853645059674,“startNumber”:1,“frames”:300,“progress”:0,“status”:2,“frame”:0,“procStatus”:{“status”:2,“eta”:0,“fps”:0,“message”:" MODEL NOT FOUND",“pass”:1,“error”:“”,“progress”:0,“frame”:0,“priority”:3,“requestPos”:5,“processorIndex”:0}}
2022-09-24 14-34-25 Thread: 22808 Info OUT: 8 2022-09-24 14-34-25 Thread: 29288 Critical Model Runner init failed for index: 0
2022-09-24 14-34-25 Thread: 29288 Critical No usable backend available
:AIERROR: MODEL NOT FOUND
After changing folder security ( before restarting VEAI );
Model Failed for Theia
2022-09-24 14-42-16 Thread: 22808 Debug Updating video info {“sar”:1,“framerate”:29.96853645059674,“startNumber”:1,“frames”:300,“progress”:0,“status”:2,“frame”:0,“procStatus”:{“status”:2,“eta”:0,“fps”:0,“message”:" Loading Model",“pass”:1,“error”:“”,“progress”:0,“frame”:0,“priority”:3,“requestPos”:7,“processorIndex”:0}}
2022-09-24 14-42-16 Thread: 22808 Info OUT: 10 2022-09-24 14-42-16 Thread: 27184 Info PARAM DEVICE: 1
:AIINFO: Loading Model
2022-09-24 14-42-16 Thread: 27184 Info MEM TOTAL: 63.8338 AVAIL: 48.9381
2022-09-24 14-42-17 Thread: 22808 Info OUT: 10 2022-09-24 14-42-17 Thread: 27184 Critical Invalid model file or file is corrupted “C:\ProgramData\Topaz Labs LLC\Topaz Video AI BETA\models/thd-v3-gnet-fp16-4x-ov.tz” “gnet4-HiDe.bin”
2022-09-24 14-42-17 Thread: 22808 Debug Updating video info {“sar”:1,“framerate”:29.96853645059674,“startNumber”:1,“frames"Model Failed:300,“progress”:0,“status”:2,“frame”:0,“procStatus”:{“status”:2,“eta”:0,“fps”:0,“message”:” “,“pass”:1,“error”:”",“progress”:0,“frame”:0,“priority”:3,“requestPos”:7,“processorIndex”:0}}
2022-09-24 14-42-17 Thread: 22808 Info OUT: 10 2022-09-24 14-42-17 Thread: 27184 Critical Loading default error reading file: “C:\ProgramData\Topaz Labs LLC\Topaz Video AI BETA\models/thd-v3-gnet-fp16-4x-ov.tz”
:AIERROR: Model Failed
After changing folder security and after restarting VEAI, Theia model runs ok.
I tried a different way and it got even weirder. I let the installation run without changing the default data folder, then I changed it on the first run. Now I have models in “my” location, and json files in the default location. So far all the models are in “my” models folder, none in the root at either place, but the jsons and the models are completely separated from each other. I don’t even know if the program is fully functional that way, but man, what a mess.
Update: Scratch that…the models are in the root of “my” location, not in a “models” folder as they should be. The jsons are all in the default location, in the models folder.
Stabilize with Jittery Motions on crashes with this beta also. Although I
2022-09-24-07-18-35-Main.zip (5.5 MB)
made a new record and got up to 24%.
My question is why the “Preview” versions appear (as by someone from Topaz explained a few weeks back) to be released with newer versions of the modules, GUI, etc. than the weekly betas. That’s bassackwards. Especially as previews are supposed to the release level follows the beta stage. Normally, it does not parallel it.
It can also happen if you’ve pick a destination (preview) file format that is somehow incompatible with the input format. I’ve had this problem for a long time. It appears that there’s and mpeg “rewrap” problem.
I agree, it reflects a completely unprofessional handling of the testing phase of this product more focused on drumming up public interest than getting it right, in my opinion. I don’t consider this product to be out of alpha yet…there’s far too much wrong to be beta, let alone “preview”.
5 Likes
Haven’t even tried this. Clean installed Windows the other day & refuse to gum the registry up with all their insanity again until it’s somewhat sorted…see y’all in 2028
3 Likes
I also get the model not found when trying to enhance. I hope they don’t go the same way as with Photo AI that AVX2 support for CPUs gets mandatory…
Also the manual rectangular / square pixel option is not available for all formats.
It is there when I load a .mxf, but not when I load a .mov file.
There also need to be more options for the most common input pixel aspect ratios (or a field where a custom pixel aspect ratio for the input can be manually typed in).
Common pixel aspect ratios:
1,0000 (Square)
1,3333 (HDV 1080) 16:9
0,9091 (NTSC DV) 4:3
1,2121 (NTSC DV Widescreen) 16:9
1,0926 (PAL DV) 4:3
1,4568 (PAL DV Widescreen) 16:9
Same here, as soon as enhance is selected → Model not found when trying to preview.
1 Like
Strange, I’m not having a problem with it.
Are you using the default data folder or have you specified a custom one?
@Nipun.nanth
With every new beta, VEAI is getting faster, but there are two glaring problems. The first has to do with video quality. The other is just to resolve what is a pain-in-the neck.
Two requests. Firstly, since multiple passes through a video are necessary to get many videos into the best shape before enhancement, at least one lossless video format should be made available, (And many QuickTime modes on a PC can be very problematic.)
Secondly, please make an option for whether the latest Preview gets put into the list as ascending or descending into an option. Personally, I find that having it at the bottom of the list as being a problem as it becomes necessary to always scroll down to find it.
Thank you.
1 Like
Couldn’t that issue be solved by Video AI automatically scrolling down to the bottom row? Basically, whatever it does to show the top left video in the list, but “reversed.”
Typically with the English language, the order of objects from first to last or earliest to latest is left to right and top to bottom, following written English.
But yes, I agree that there should be an option to order the videos in ascending or descending order.
And by the way, why can’t we reorder videos in the source pane?
the dev already replied to this request, it will be possible soon to choose betwen the two possibilities using a switch button (like the frame one in Preferences).
For anyone trying to change the default installation locations, why is this so important? What are you trying to achieve?
Not saying that it doesn’t need to be fixed/work properly if the option is there, just curious why some people are hellbent on changing the defaults…
1 Like
When VEAI 3-8.b inserts a new preview into the list, it automatically displays a scroll bar if the video list is too long. Currently it puts the latest files at the bottom of the list. This behavior would be OK, if it also ‘automatically’ scrolled down to it. This not only adds a extra step to looking at it’s options, but is not intuitive and I personally often find myself opening the wrong preview file. - It would be best to push the list down and have the latest at the top. - Much easier and more intuitive.
Usually on a computer screen, file lists are sorted either by date or alphabetically. If sorted by time and date, the preference for most users is to have the newest at the top.
IMO, it should be the same in VEAI.
That will be a welcomed improvement. And, as you said, if at the bottom, it should automatically scroll down to it.
I’m adding the version number of the beta to the installation and data directories during installation. However the default folder in the installer is always the last manually choosen foldername if you install a new version, even if the old version has been uninstalled (it gets uninstalled anyway by the new installation without asking).
Estimate does also not work with Proteus in 3.0.0.8.b (nothing happens when pressing estimate)… last working version for me is 3.0.0.7.b
