AV1 videos dropped by drag&drop or opened still show only black image, whereas 2.6.4 doesn’t have this problem, why?
Also, I noticed that sometimes drag&drop doesn’t work (I drop files from Total Commander as Admin to VEAI 3 beta also opened as Admin), when there are, for example two spaces or non-Latin characters in the folder name. The same goes for Topaz Photo AI, by the way. Stable VEAI 2.6.4 doesn’t have this issue.
Use Treesize Free edition to look for large files or folders.
Look at the source though. There’s honestly not much it could have done with that.
there is 4 diferent views. a button for each of them is the best and quicker. one click instead or 2, 3 or 4 click is better. and there are still a lot of space for more buttons.
Request
For Proteus “auto” display/overlay values calculated.
vote for this.
I couldn’t find the video, however, My hard drive got back the 50GB that the C drive somehow lost after updating Windows 11 (there were apparently issues with the previous release and possibly that was one of them?).
1 Like
I suddenly wondered, what does the planned future HDR support mean in terms of features?
1: Enhance of an HDR source without losing the HDR information.
2: Conversion of an SDR source to HDR.
Excellent point!
there is a fourth one , the full screen in the menu !
Hi Lee,
an “intelligent” system should recognize when it should not “improve” bad input. In above example I tried to avoid enhancements by setting all parameters manually to “0”, and expected just size increase from 630 to 1920.
One caution about vanishing VEAI GUI on Windows. If it has happened, hanging task resources may prevent a full shutdown, so be sure to wait until the system fully shuts itself off before walking away.-
Exception: If it’s ffmpeg, and you know you’re still exporting video, leave it running. Otherwise, click shut down anyway.
I believe that the values in “auto” mode keep changing as the frames are being processed. *Manually making changes" in auto mode simply biases the auto process to emphasize a setting by more or less than the default. The job of doing the rendering is being handed off to ffmpeg. - I’m not certain that the current interface between the GUI and ffmpeg being robust enough to support all that. - It would be nice someday.
I’ve seen that too in order versions.
See if the same thing happens using different input/output formats.
Most of the stuff generated by VEAI is (intentionally) done by default in the temp file areas. As such, (in Windows at least,) opening a specific drive’s properties, and selecting “Disk Cleanup,” making sure that Temp files is selected and (obviously) Recycle bin, should get rid of most of it.
You could also terminate the ffmpeg process from task manager.
All the processing is done by ffmpeg including any enhancement filters that you might have selected before the GUI crashed. ffmpeg doesn’t really need anything from the GUI as all the GUI does is generate and pass parameters to it. So if you selected Proteus Auto, ffmpeg will continue to process your source while applying that enhancement.
1 Like
… and what the hell is VEAI doing (CPU Load: VEAI 12%, ffmpeg 5%)
2 Likes
There is a way to use Topaz Video AI 3 in VirtualDub2 as an external encoder (CLI), so you can load any avisynth script or use VirtualDub filters as pre-process
You will have to configure and create external encoders profiles. Example with Artemis V13 and H264 NVENC stream output with no sound.
Open Notepad and copy this text
{
"description": "VirtualDub external encoder profile collection",
"externalEncoders": {
"sets": {
"TOPAZ VIDEO AI (video)": {
"videoEncoder": "FFmpeg TVEAI",
"audioEncoder": "",
"multiplexer": "",
"description": "(MP4 - H264)",
"extension": "",
"processPartial": false,
"useOutputAsTemp": false
}
},
"profiles": {
"FFmpeg TVEAI": {
"name": "FFmpeg TVEAI",
"program": "C:\\Program Files\\Topaz Labs LLC\\Topaz Video AI BETA\\ffmpeg.exe",
"commandArguments": "-f rawvideo -s %(width)x%(height) -r %(fpsnum)/%(fpsden) -i - -filter_complex veai_up=model=alq-13:scale=2:device=0:vram=1:instances=1:threads=0 -c:v h264_nvenc -profile:v high -preset medium -pix_fmt yuv420p -b:v 180M \"%(tempvideofile)\"",
"outputFilename": "%(outputname).m4v",
"type": 0,
"pixelFormat": "yuv420p",
"inputFormat": 0,
"checkReturnCode": true,
"logStdout": true,
"logStderr": true,
"bypassCompression": false,
"predeleteOutputFile": false
}
}
}
}
Save this as TVAI.vdprof in the VirtualDub2 folder (or anywhere else, it doesn’t matter)
Open VirtualDub2, go to ‘options’ — ‘External Encoders’
A popup window will open, click on ‘import…’ and choose the vdprof file just created and voila ! Click OK
Then when saving a video : File > Export > Using External Encoder and choose TOPAZ VIDEO AI
You can just create several profiles with any model or output desired or just edit the command arguments directly when needed.
Of course you still will be limited with the defaults encoders available in V3 unless you have build your own FFmpeg with veai.
1 Like
salut, j’ai trouvé un petit bug d’artefact lorsque j’ai convertit ma vidéo, avec les versions beta par rapport à la version 2.6.4. Je ne sais pas si ça a été mentionné déjà mais en utilisant artemis aliasing or moire, le nom CEZANE du bateau est flouté sur quelques images successives :
1 Like
There is a new setting that may be confusing you.
You have to choose “relative to auto” or “manual” from the dropdown.
On relative to auto, 0 is auto and the sliders are a percent adjustment up or down.
On manual, 0 is 0 and nothing will be done with anything set to 0.
