I upgraded to the publicly released v3.0.0 today. I attempted to upscale a 720x480 progressive video to 1920x1080 using the Proteus AI Model when the following error occurs:
Passing a number to -vsync is deprecated, use a string argument as described in the manual.
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
With detailed logging enabled, the error becomes:
Setting 'pix_fmts' to value 'p210le'
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_up_0'
query_formats: 6 queried, 5 merged, 1 already done, 0 delayed
w:720 h:480 fmt:yuv422p10le sar:853/720 -> w:720 h:480 fmt:bgr48le sar:853/720 flags:0x0
SAR: 1.184722 scale: 2 x: 2.250879 y: 2.250000 v: 2.250879
Here init with perf options: model: prob-3 scale: 0 device: 0 vram: 0.900000 threads: 1 downloads: 1
2022-10-19 16-59-14 Thread: 0x10504c580 Info AIEngine mode: Normal 2.2.32
Output size set to: 1440 960
Here Config props model with params: up prob-3 2 0 1 1 720 480 0.000033 29.970030
2022-10-19 16-59-14 Thread: 0x10504c580 Info Model: "prob-3" Device: 0 VRAM: 0 threads: 1
Failed to configure output pad on Parsed_veai_up_0
Uninit called for prob-3 1
Error reinitializing filters!
Failed to inject frame into filter network: Invalid argument
Error while processing the decoded data for stream #0:0
Statistics: 0 bytes written, 0 seeks, 0 writeouts
Statistics: 4453798 bytes read, 3 seeks
Conversion failed!
Not sure how to proceed as VEAI 2.6.4 has never had this issue. For reference, this is the ffmpeg command:
ffmpeg "-hide_banner" "-nostdin" "-y" "-loglevel" "debug" "-nostats" "-i" "/Volumes/3TB 1/305_clips/305_prores-mov Comp 4.mov" "-vsync" "0" "-avoid_negative_ts" "1" "-sws_flags" "spline+accurate_rnd+full_chroma_int" "-color_trc" "1" "-colorspace" "6" "-color_primaries" "6" "-filter_complex" "veai_up=model=prob-3:scale=0:w=1920:h=1080:preblur=0.05:noise=0.05:details=0.26:halo=0.09:blur=0.35:compression=0.49:device=0:vram=0.9:instances=1,scale=w=1920:h=1080:flags=lanczos:threads=0:force_original_aspect_ratio=decrease,pad=1920:1080:-1:-1:color=black" "-c:v" "prores_videotoolbox" "-profile:v" "hq" "-pix_fmt" "p210le" "-allow_sw" "1" "-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=Enhanced using prob-3 with recover details at 26, dehalo at 9, reduce noise at 5, sharpen at 35, revert compression at 49, and anti-alias/deblur at 5. Changed resolution to 1920x1080" "/Volumes/3TB 1/305_veai_2/305_prores-mov Comp 4_358495367_tvai.mov"
Well Iām now getting after rm files at /Users/tatea/Library/Application\ Support/Topaz\ Labs\ LLC/Topaz\ Video\ AI
Last message repeated 3 times
nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 0
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)
Last message repeated 2 times
nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 0
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)
Last message repeated 4 times
nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 0
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: 1
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)
Output size set to: 2560 1920
Here Config props model with params: ad prob-3 4 0 1 1 640 480 0.000011 120.000000
Failed to configure output pad on Parsed_veai_up_0
Uninit called for prob-3 1
Error reinitializing filters!
Failed to inject frame into filter network: Invalid argument
Error while processing the decoded data for stream #0:0
Statistics: 0 bytes written, 0 seeks, 0 writeouts
Statistics: 2242687 bytes read, 2 seeks
That fixed it. VEAI v3.0.0 is now working as expected. Since this machine is only used for editing, I donāt mind having the Max Memory increased to 100% but I would like to know why this works.
I have seen, and apparently resolved, the same error on my system.
What appears to have fixed it (in Windows anyway) is two steps:
Make sure that any other ffmpeg install is NOT in your search path.
Put ā\Program Files\Topaz Labs LLC\Topaz Video AI\share\ffmpegā in the search path.
I have a custom build of ffmpeg that I normally use for videos that donāt need TVAI processing and it seems it was being accessed by TVAI under certain circumstances.
Also, once you have any of the mentioned ffmpeg errors, it seems you need to reboot to clear them.
I was unable to run any previews successfully, and was unable to get more than one export to work. Since making the above change, I have successfully run 3 SD to 4K upscales.
My rig:
Windows 11 Pro 22H2
Nvidia RTX-3080Ti (EVGA Hybrid - AIO cooled) (using driver version 522.25)
Intel I9-12900K (AIO cooled)
32GB DDR5-5200
Running 3 simultaneous 45 minute SD/h.264 originals to 4K/h.265 using Proteus Manual settings took a total of 7.5 hours. One takes 3 hours and 2 take 5 hours.
Iām generally getting the same error as everyone else when trying to use Topaz Video AI ffmpeg from the command line:
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
This is on a M1 Pro Macbook on macOS 13 with Topaz Video AI 3.0.1.
Sadly none of these helped:
Increasing the VRAM usable by Topaz Video AI ffmpeg.
Removing my system ffmpeg.
Reinstalling Topaz Video AI.
Attempting to simplify the ffmpeg command.
Logging out and back into my account.
Using a normal terminal rather than the terminal opened by Topaz Video AI, ensuring I setup paths to VEAI_MODEL_DATA_DIR and VEAI_MODEL_DIR.
Modifying VEAI_MODEL_DATA_DIR to follow similar behaviour as Windows. (On macOS, it defaults too /Applications/Topaz Video AI.app/Contents/MacOS/../Resources/models. Windows does something similar, but at the there is a extra slash. So I did that on macOS too. .../models/)
Tried removing ārelative directoriesā from the path for VEAI_MODEL_DATA_DIR and VEAI_MODEL_DIR. (This means removing the ā..ā from the directories)
Does anyone have any other ideas on how to fix this? Or is this a bug that will hopefully be fixed in the future?
Iām having no issues running Topaz Video AI ffmpeg on Windows. Just macOS.
The error message is just a generic āsomething failed with a filterā
Iāve not tried the built in ffmpeg but I have built my own so you get that to work I had to do the following
export VEAI_MODEL_DIR=ā/Applications/Topaz Video AI.app/Contents/Resources/modelsā
run the login app which is at /Applications/Topaz Video AI.app//Contents/MacOS/login in the App package, thereās also a copy in the redistribution files.
Iāve just done that and run the in built version without issue (M1 Mac Mini - macOS 12.6)
% "/Applications/Topaz Video AI.app/Contents/MacOS/ffmpeg" "-hide_banner" "-nostdin" "-y" "-i" "/Volumes/Sabrent Media/Documents/QA.mov" "-flush_packets" "1" "-filter_complex" "veai_up=model=thf-4:scale=0:w=640:h=480:noise=0:blur=0:compression=0:device=0:vram=0.9:instances=1" "-color_trc" "2" "-colorspace" "2" "-color_primaries" "2" "-c:v" hevc_videotoolbox -crf 20 "-pix_fmt" "yuv420p" "-map_metadata" "0" "-movflags" "use_metadata_tags" "-map_metadata:s:v" "0:s:v" "-map_metadata:s:a" "0:s:a" "-map" "0:a" "-c:a" "aac" "-metadata" "videoai=Enhanced using thf-4 with reduce noise at 0, sharpen at 0, and revert compression at 0" ~/SSD/test_topaz_ffmpeg.mp4
Which is a command I originally copied from VEAI with the extra TIFF creation removed and the encoding codec changed the version I found was x264, as its a command I use for testing my own build.
Thank you for that. I just assumed the Topaz Labs ffmpeg on macOS would behave the same as it does on Windows, but itās slightly different and your advice helped me figure that out.
Iāve raised a ticket with support on this and sent them logs etc.
While waiting i have been messing around with the FFMPEG command and found the VSYNC error you see in the GUI when the processing error occurs appears to be a red herring.
Copying the command and pasting it in the command prompt shows the actual error relates to the output file directory being invalid when I changed this and re ran the command the file is processing fine.
The FFMPEG command generated in my case by Video AI was:
ffmpeg ā-hide_bannerā ā-nostdinā ā-yā ā-loglevelā ādebugā ā-nostatsā ā-iā āfile://nsmnas01/nsm_media/Videos/DaVinciResolve Projects/Media/Video-eo/BBCChristmasVT1979ChristmasTape/BBC Christmas VT 1993 - Grim Fairy Tales.mp4ā ā-vsyncā ā0ā ā-avoid_negative_tsā ā1ā ā-sws_flagsā āspline+accurate_rnd+full_chroma_intā ā-color_trcā ā2ā ā-colorspaceā ā2ā ā-color_primariesā ā2ā ā-filter_complexā āveai_up=model=prob-3:scale=0:w=768:h=576:preblur=0:noise=0:details=0:halo=0:blur=0:compression=0:estimate=20:device=0:vram=1:instances=1,scale=w=768:h=576:flags=lanczos:threads=0ā ā-c:vā āprores_ksā ā-profile:vā ā3ā ā-vendorā āapl0ā ā-bits_per_mbā ā8000ā ā-pix_fmtā āyuv422p10leā ā-map_metadataā ā0ā ā-movflagsā "frag_keyframe+empty_moov+delay_moov+use_metadata_tags+write_colr " ā-map_metadata:s:vā ā0:s:vā ā-map_metadata:s:aā ā0:s:aā ā-c:aā ācopyā ā-metadataā āvideoai=Enhanced using prob-3 auto with recover details at 0, dehalo at 0, reduce noise at 0, sharpen at 0, revert compression at 0, and anti-alias/deblur at 0. Changed resolution to 768x576ā āC:/Program Files/Topaz Labs LLC/Topaz Video AI/file:/nsmnas01/nsm_media/Videos/DaVinciResolve Projects/Media/Video-eo/BBCChristmasVT1979ChristmasTape/./BBC Christmas VT 1993 - Grim Fairy Tales_38851643_tvai.movā
It errored on the output file location which is the last part of the command in this case āC:/Program Files/Topaz Labs LLC/Topaz Video AI/file:/nsmnas01/nsm_media/Videos/DaVinciResolve Projects/Media/Video-eo/BBCChristmasVT1979ChristmasTape/./BBC Christmas VT 1993 - Grim Fairy Tales_38851643_tvai.movā
changing this to the actual location i chose to save the file
āfile:F://./BBC Christmas VT 1993 - Grim Fairy Tales_698345734_tvai.movā
Has resolved the issue but of course requires manual intervention and for it to be run in the CLI so you donāt get the nice preview etc.
If you are having this issue it may be worth trying this to see if it fixes it for you although there appears to be varies issues/bug with this release so may not be a fit all solution and of course Topaz need to fix these bugs in what is meant to be a production release now!
FFMPEG fails on me on Windows 10; CLI output below:
C:\Program Files\Topaz Labs LLC\Topaz Video AI> .\ffmpeg "-hide_banner" "-nostdin" "-y" "-nostats" "-i" "R:/2022.10.15 FN Rameau Strauss Beethoven/Denoised/Strauss/Event_Version 1_0001_0141/KAM06_01_FN_Rameau_Strauss_Beethoven_2022.10.15.mxf" "-vsync" "0" "-avoid_negative_ts" "1" "-sws_flags" "spline+accurate_rnd+full_chroma_int" "-color_trc" "1" "-colorspace" "1" "-color_primaries" "1" "-filter_complex" "scale=w=3840:h=2160,setsar=1,veai_up=model=ahq-12:scale=0:w=3840:h=2160:device=0:vram=0.9:instances=1,scale=w=3840:h=2160:flags=lanczos:threads=0,scale=out_color_matrix=bt709" "-c:v" "prores_ks" "-profile:v" "3" "-vendor" "apl0" "-bits_per_mb" "8000" "-pix_fmt" "yuv422p10le" "-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=Enhanced using ahq-12. Changed resolution to 3840x2160" "R:/2022.10.15 FN Rameau Strauss Beethoven/Denoised/Strauss/Event_Version 1_0001_0141/./KAM06_01_FN_Rameau_Strauss_Beethoven_2022.10.15_923296773_tvai.mov"
-vsync is deprecated. Use -fps_mode
Passing a number to -vsync is deprecated, use a string argument as described in the manual.
[mxf @ 000001BE872FE500] Stream #0: not enough frames to estimate rate; consider increasing probesize
Input #0, mxf, from 'R:/2022.10.15 FN Rameau Strauss Beethoven/Denoised/Strauss/Event_Version 1_0001_0141/KAM06_01_FN_Rameau_Strauss_Beethoven_2022.10.15.mxf':
Metadata:
operational_pattern_ul: 060e2b34.04010102.0d010201.10030000
project_name : 2022.10.14-15 FN Rameau Strauss Beethoven
uid : 84cf23ca-7c88-634a-b205-cc1f831abf6c
generation_uid : 37dae3d9-c828-3845-8b95-1a2ed5ac46fa
company_name : Blackmagic Design
product_name : DaVinci Resolve
product_version : 18.0.4
product_uid : 057cd849-178a-4b88-b4c7-825af8761b34
modification_date: 2022-10-31T16:43:54.240000Z
application_platform: DaVinci Resolve
material_package_umid: 0x060A2B340101010501010D4313000000635FFB44EE840000060E2B347F7F2A80
material_package_name: KAM06_01_FN_Rameau_Strauss_Beethoven_2022.10.15
comment_Comment : Created by Resolve
Duration: 00:00:00.92, start: 0.000000, bitrate: 731728 kb/s
Stream #0:0: Video: dnxhd (DNXHR HQX), yuv422p10le(tv, bt709, progressive), 3840x2160, SAR 1:1 DAR 16:9, 25 tbr, 25 tbn
Metadata:
file_package_umid: 0x060A2B340101010501010D4313000000635FFB44EE850000060E2B347F7F2A80
file_package_name: KAM06_01_FN_Rameau_Strauss_Beethoven_2022.10.15
track_name : KAM06_01_FN_Rameau_Strauss_Beethoven_2022.10.15_v1
reel_umid : 0x060A2B340101010501010D4313000000635FFB44EE860000060E2B347F7F2A80
timecode : 05:08:43:11
Stream mapping:
Stream #0:0 (dnxhd) -> scale:default
scale:default -> Stream #0:0 (prores_ks)
[Parsed_veai_up_2 @ 000001BE89CAB980] Failed to configure output pad on Parsed_veai_up_2
Error reinitializing filters!
Failed to inject frame into filter network: Invalid argument
Error while processing the decoded data for stream #0:0
Conversion failed!
Frankly, inclusion of CLI was the only feature I wanted before deciding to purchase the software and it doesnāt even work.
This is exactly the command I get in the GUI after left clicking and selecting āFFmpeg Commandā.
Iām extra sure the ffmpeg used in above error is the one included with the software and not any other I might have downloaded earlier.
On the side note: My feature request would be to include libavcodec in the ffmpeg build, especially for its support of DNxHD which is my preferred codec. Prores_ks seems to cut any video data above 960 and below 64 bits, which is problematic since I use Topaz rendered files in color grading later.
