I hope this message finds you well. I am writing to discuss some concerns and observations regarding the use of multiple GPUs with VEAI.
As a long-time user of VEAI (since version <1.0), I have been an advocate for CLI and multi-GPU support. In fact, I have purchased several licenses to circumvent the multi-GPU issues. With these changes, I am concerned about the future of CLI support.
In previous versions of VEAI, I noticed that the multi-GPU functionality was not working as expected, which led me to use multiple instances of VEAI as a workaround. I am pleased to see that this issue seems to have been addressed in the recent updates.
However, I have some concerns about Standard version losing multi gpu to the PRO license model, which appears Topaz are targeting studios/teams engaged in mass conversions. I am curious to know if this change implies that support Standard version conversion with CPU, integrated GPU (iGPU), and discrete GPU will be discontinued. Users are missing out on maxing out there desktop/laptop for the conversion.
The move to limit usage to a single GPU could be quite restrictive for some users. Given the high cost and computational demands of faster, for newer GPU models. A desktop users 16-32Core CPU, with IGPU and two gaming GPUs a limit of three GPUs for the standard version might be a more balanced approach.
Lastly, could you please provide information on the cost implications of upgrading from a standard to a PRO Multi-GPU license?
Please note I gave up on multi GPU in the VEIA 4 Series after trying for a year, and beta testing under VEIA 3 series.
To drop multi GPU from Standard, your price must also be dropping for that licence
I look forward to your response and appreciate your attention to these matters.
Rhea has some big issues with depth of field preservation. I’ve noticed several scenes where it tries to bring the background, which is purposely not sharp/in-focus into focus and it looks very wrong.
This model needs to be adjusted or perhaps retrained to not deblur what should be blurred.
Also not for nothing, but there’s gotta be a model sooner than later that stabilizes noise. Neat Video 5 can do it to a degree, but obviously could be vastly improved (I notice ghosting at times). It’s been a little over a year since I brought this to Topaz’s attention: Transformer for Video Denoising
Btw seeing these pop-up here n’ there in the processed video:
Looks like you have a 1050 Ti with 4GB of VRAM that is below the System Requirements for Video AI. Rhea needs a lot of VRAM to run and it looks to be overwhelming your card.
it does recover the details much better but for old VHS to MP4 progressive converted MP4s Iris was not good in handling noisy unsharp parts or had artificial irisses then I had to protheus then I used both but this does NOT read NOT improve the output. I am happy that ths model is sufficient enough to renew my subscription I can make any movie from Interlaced to Progressive with ther tools. It is a bit softening, but that will it make more appealing. My 30 years marriage Video 25 P looks good my 50 p from my son as a baby now 30 especially in the darker phases much better than the original
The 5.2.0.2b with the edit properties is SOOOOO MUCH better than 5.2. even better than the alpha version in speedI set it to FULL no Version has this it used to be MPEG
Fixed missing swap views button.
Restored colorspace selection.
Ensures colorspace correctness for input videos with complete colorspace tags.
in the latest Beta it says this. Does that mean its going to stop giving everyone yellow skin tints? If so, how do you use this tag feature? (assuming they dont mean LUTs)
A very general summary: Improve details tends to make dark lines more pronounced. Sharpen does more what the name implies, but turning it up too much will start to add dot patterns to things.
When I select “Close all inputs” the related files remain locked by Video AI so tht I am unable to delete them unless I quit Video AI and open it again.
