Hello Everyone!
We have another beta for y’all. Please let us know if processing gets stuck and send us the logs.
Download:
Changelog:
Known Issues:
Thanks for testing
Please upload problem videos and logs here: Submit files
Are you able to elaborate on what sorts of issues? The model doesn’t work? The quality is degraded compared to Windows? Things like that.
It is just Apollo Sharpen has bad quality results on Macs.
The performance is much better. I know another issues must come first, but want to ask anyways. Will
more performance updates happen in the near future?
Yes, future performance improvements will be GPU specific on windows.
Cool, another beta!
Glad to see the apollo models are back, and seeing as the general release’s performance is great, I would love to compare the two as the general release is the perfect gauge for testing!
Yeah, it was wise to leave apollo out of the general release, as it was pretty ganked, can’t wait to give it a go!
Does ffmpeg now work on the command line?
Thank you very much…I hope that with the next updates, we can further improve the quality of the models, taking full advantage of the potential of Nvidia RTX 3 series cards like my 3070! 
TVAI FFmpeg is working through the command line for me. However on macOS I had to adjust the permissions of the models folder to work around an error on my system.
chmod 775 /path/to/models/folder
If you are having issues, reporting your issue might help the developers resolve it. Specifically with full logs with can be gotten by:
-loglevel debug to the end of ffmpeg, and uploading the output here (or somewhere private for only the developers to see as some more information that may be seen as personal may be included in the debug logs)@ suraj
It would be helpful that TOPAZ indicate the minimum/recommended specifications a GPU should have to perform adequatly with TVAI:
I think both Apollo Sharpen and Apollo Soft have issues. I’m getting a “stuttering” looking result as the final output when running Apollo Sharpen or Apollo Soft on macOS. This doesn’t happen with Chronos, Chronos Fast, or Apollo (Standard). There is no such issue on Windows.
So I’d recommend changing the known issues list back to including Apollo Soft issues on Mac
OS: macOS 13.1
Processor: M1 Pro (8 Core + 14 Core)
I use Windows.
Version 3.1 fully works if I use the Topaz Video AI.exe program itself.
However, if I run ffmpeg in a dos window, ffmpeg just finishes quickly with no error or result.
That is likely because either you already have a (common) ffmpeg in your path that takes precedence, or you have no set the TVAI environment variables correctly.
P.S. Might actually help if they introduced a new environment variable, like TVAI_FFMPEG_PATH, for their proprietary version of it.
99% stucked again.
2023-01-20-18-44-17-Main.tzlog (593.2 KB)
Definitely not.
I tried replacing ffmpeg with the full “c:\Program Files.…\ffmpeg.exe”. I made Topaz ffmpeg dir the current one in dos window. To no avail.
It seems that this behavior of ffmpeg is programmed intentionally.
That might be tricky. I know a person who bought TVAI on my recommendation to upscale and cleanup 10 second video clips from a trail cam. They’re using it on an older Mac doing CPU only and are very pleased. The use cases can be so varied for ‘adequate’.
I’m having issues with AV1 encoding and frame interpolation with select videos. In the UI all I get is “Unknown Error” but if I run TVAI ffmpeg from the command line I get this error after a few seconds of processing:
[av1_nvenc @ 000002A4D64C9880] Failed locking bitstream buffer: invalid param (8):
Error submitting video frame to the encoder
This is with NVENC AV1 as my export option.
If I use any other codec (Including NVENC H264 or H265), I have no issues.
Steps for me to reproduce:
GPU: RTX 4090 (Driver 528.02 Studio Driver)
CPU: Ryzen 9 5950X
RAM: 64GB
Windows 11
You might get useful error messages if you run ffmpeg with -loglevel debug
And just making double sure, have you made sure you’ve setup the path correctly?
If you open a command prompt and type in echo %TVAI_MODEL_DIR% and echo %TVAI_MODEL_DATA_DIR% you should get two paths. They should be be something like this:
echo %TVAI_MODEL_DIR% -> C:\ProgramData\Topaz Labs LLC\Topaz Video AI BETA\models
echo %TVAI_MODEL_DATA_DIR% -> C:\ProgramData\Topaz Labs LLC\Topaz Video AI BETA\models\
(Note: The paths may be different for you depending on where you setup the models folder when installing TVAI BETA)
If these don’t exist, then you will need to set them up.
Also, some adjustments were made between 3.0.12 and 3.1.X that you may need to account for. For example, the old AI filters were called:
veai_up and veai_fi
while the new ones are:
tvai_up and tvai_fi
This only applies if you are using commands from older versions of TVAI.
You might need to delete the models folder ( C:\ProgramData\Topaz Labs LLC\Topaz Video AI BETA\models - Actual location might be different for you) at some point if you continue to experience issues. After doing that, open TVAI, login again, and see if the command line works now.
If you still have issues, then you might need to adjust permissions on the models folder to get it working. Or you might have a more uncommon issue and will need to provide more information for the developers to help you out.
Again and again: The normal version 3.1 under Windows works as it should.
ffmpeg running in dos window does not work.
And there could be many reasons TVAI ffmpeg through the command line isn’t working while the GUI does. For example, an incorrectly setup environment, or an incorrect ffmpeg command, or incorrect permissions on a folder for running ffmpeg through the command line. So I’m just trying to offer some suggestions on things you can try to see if we can fix it.
