Not mentioned but you can see cuda activity on your GPU in your task manager on windows.
I check for Gaia model on 2.6.4 cuda have no activity and on 3.0 cuda have activity.
temporary work around : adding your share as a network drive. I have a 414j Nas Synology and have no problem with working that way since the beginning. Itās not what you want, i understand, but there is at least a workaround until this feature is added at some points.
The license issue arises from the use of the Avisynth reader, which is distributed free of charge under the GPL, and if Topaz were to create its own Avisynth reader and import it into ffmpeg, I do not see a license issue.
Donāt you think it is just an excuse to say that you canāt support proprietary software because you canāt get a free ride on Avisynth Reader 
2 Likes
GPU-Z is a better tool to see real GPU usage. Not sure if it shows CUDA scores specifically, but its better than the Windows task manager.
https://www.techpowerup.com/gpuz/
UPDATE:
It shows CUDA information too.
Easily done with MKVToolnix GUI, depending on your source file.
1 Like
Hi, what are doing with the metatags when outputting an enhanced x265 file from an original mp4? (I used copy audio if this makes any difference)
When I inspect the output file afterwards in "MediaInfoā all the metatags appear to have been copied from the original file into the new output, however none of the programs I have are able to read the tags, including Windows Explorer & MP3 tag editing software like TagScanner.
When viewed in āMediaInfoā the tags in the output file are identical to the original file except they have lower case headings.
I did also notice a tag āvideoaiā that has information about how the file was enhanced, which is great so thanks for that (except that when you edit tags using any tag software, this tag disappears bummer!)
I noticed untagged color info after 4K upscale:
Artemis LQ Strong Dehalo v2 (alqs-2), 2x upscale (no filters other than alqs-2 in 3.0.0):
(Right click ā āView Imageā for original size.)
Itās arguable which is better, but I feel in 3.0.0 it loses textures and has too much sharpness / edges.
In any case, this is clearly not the same model.
If Topaz or anyone wants to test for themselves, hereās the same video file (18 frames):
test_sample.zip (745.1 KB)
3 Likes
I donāt expect you to have read all the posts before. This is because the generated command sets the scale to 0. If you copy the command and change that 0 to 2, you will get the exact same result as what you get in 2.6.4.
In my opinion, 3.0 is still beta in ārelease version clothingā. But, the premise of the new approach to the program is a good one, and it is destined to be much better than 2.6.4, in time. I would give it a few months to get there.
1 Like
What you say makes sense. Question is, is it this way in error or intentional on Topazās side? Have they commented on this point yet?
1 Like
No, they have not. There are only a lot of posts in here. Maybe if I make a new topic outlining the whole thing Iāll get a reply. I also donāt know if itās true for every base model, but I tried generating a command for the specific model and scale mentioned by @Chase and it did indeed set the scale to 0 instead of 2.
1 Like
Golf clap, Iāve attempted to update from v2.6.4 about 5 times now, VEAI downloads the update package, seemingly applies it, but opening VEAI Iām still on v2.6.4 with update prompt. Youre just wasting my data man, tired of the bugs and bullshit with your software.
1 Like
Stop trying to update from v2, uninstall it, and install v3 from the links at the top of this post.
1 Like
What? Copy command and change to 2?
Are you talking about the command line interface?
So I set the scale to 2x, but, it doesnāt scale it properly unless I run a command line?
And thisā¦ is the final published version of the program?
1 Like
Whoops, I must pay another $300 to update as my original version expired in May of this year. Trying Dione and Gaia, I see no improvement with the main problem with VEAI, that it desatures the image, Iām talking about how it pulls out crimson sub-surface scattering from skin-tone, so I wonāt be paying the $300 update tax. Golf clap once again.
Yes.
Be very careful when installing 3.0:
- Be sure to specify a different location for the software
- Be sure to specify a different data/model location
- Be sure the checkbox is clear to uninstall 2.6.4.
They will co-exist fine.
2 Likes
I just tried running a Video AI encode from the command line (using the copy ffmpeg export command).
I ran it in the Video AI encode install folder and got this:
[swscaler @ 0000020CD2C8C5C0] [swscaler @ 0000020CD2E23D00] No accelerated colorspace conversion found from yuv420p to bgr48le.
[Parsed_veai_up_0 @ 0000020CD15C4C40] Failed to configure output pad on Parsed_veai_up_0
UPDATE: I see the problem, environment variables arenāt set (didnāt open command prompt from Video AI)
@Topaz
Your ffmpeg command line building is quoting a lot of things that donāt need to be quoted.
"-hide_banner" can be just -hide_banner.
Also:
-vsync is deprecated. Use -fps_mode
Passing a number to -vsync is deprecated, use a string argument as described in the manual.
1 Like
This is me just guessing, but in 2.6.4 setting the scale determined what version of the base AI model to use. (Like from DVD resolution to FHD or 4K or what not.) They seem to have implemented that same logic in 3.0.0, but left out that part when generating the command. For example, hereās the offending section of the command:
..."-filter_complex" "veai_up=model=alqs-2:scale=0:... should be:
..."-filter_complex" "veai_up=model=alqs-2:scale=2:...
They at least tried to make it easy to run it from the command line. Says I can press Ctrl+t to open it. Then in the output panel I can click the [ā¦] button and select FFmpeg command. Then I can copy that and paste it directly into the command line or a text editor and change it. (Oh, you might have to set an environment variableā¦)
Final is a strong word here. Everyone who doesnāt want to play with the command line is doomed in that case. Iād give them a few more months to release what was actually supposed to happen with this version.
I am suffering 2 issues with version 3.0.0:
-
Audio saving. When processing video with multiple audio tracks (e.g. english, german, comments, etc), only first audio is being copied/transcoded (the rest are discarded). The version 2.6.4 used to copy all audio tracks, saving appropriate track names in the metadata too.
-
Making the bitrate dropdown rather than quality level for H264/H265 is awkward idea. Not sure what was the rationale behind. The H265 codec settings are producing extremely āfatā files for me.
Although version 3 looks better, GAIA processing is faster, there is support of parallel processing and multiple filters can be applied at single pass, the audio discarding and weird setting for bitrate are forcing to post-process TVAI 3.0.0 output files, which is waste of time. Previously output files were good enough to be used as final versions.
Hope this is something that can be fixed soon. Looks like minor issues, but Iāll stay on 2.6.4 for now
Thanks!
