We’ve also improved codec and GPU driver support. ![]() ![]() Video playback works fine, and the PowerMizer in the NVIDIA setting panel for my RTX 4090 shows that the GPU really works, but as soon as I try to do a preview (such as here, using the NYX denoiser on H265 video from a Sony FX30 having captured northern lights in slow motion, ISO cranked up to max), you get the error I have appended in the logs here. Topaz Video AI v3.0.7and all of the weekly updates since launching v3.0delivers many performance and stability improvements, including optimizations that improve model quality and make the app run more smoothly. Just testing so far, I open Powershell in the Windows VM, cd to C:\Program Files\Topaz Labs LLC\Topaz Photo AI and (with the path to jucify being set in the Path variable) runĪnd voila, my room gets hot testing Photo AI on old images from the archive without even really touching the CPU.įrom the C:\Program Files\Topaz Labs LLC\Topaz Video AI\ folder is another matter.įirst issue is that while I can log in and register the app just fine without the juicify container, Video AI will neither recognize an already registered login nor open a web browser so that I can register the app anew.Īnd while I’m not surprised that Video AI will throw an error when it cant find a GPU in a VM without the juicify container, the redirection-of-GPU-tasks-over-network-to-the-host-OS magic that juicify normally does can throw an error here. I run the Juice service to relay GPU jobs from the VM to the host OS in control of the GPU, and this runs fine with the Topaz Photo AI. ![]() I’m testing out the Topaz tools on a Windows 11 Virtual Machine inside Linux Mint.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |