a model that properly handles compression artifacts
I found Proteus handles this well. It depends what your source is, of course. I work with low quality SD footage regularly and I’ve been impressed with Proteus – manually tuned with about 50-70 on revert compression, and maybe 10-20 on improve detail, sharpen, and deblur.
I have had a random issue sometimes in lots of versions of VAI, similar to your “remaining times of 12 days”. I run VAI on a laptop and whenever I get the above issue I see my laptop is under the impression that it is no longer plugged in to the mains. I have it plugged in permanently. When this happens the processing time remaining keeps increasing and it seems no processing is taking place. I resolve it easily, just switch the laptop off at the mains and back on again. The charging icon repairs, the processing continues and the time remaining drops as everything gets underway again.
Yes How is this tested why 2 updates in a week and one was useless.
Nothing is more dangerous than changing a GUI
My God Tony listen to us it is simply not good and it does not make sense to change a GUI radically nowhere
Processing videos using 2x Upscale, Stabilization (default), Motion Deblur (default) and Enhancement->Iris->Medium Quality->Auto
I see (repeatedly) loading model, processing, loading model then it appears to stop. The video playing on the right side shows “not processed”. I know the first processing step is for stabilization. Not sure what is going on after that. End result is no processed video on the right hand side.
This file is extremely important. In the event of a crash, this file can still be used so that no “progress” is lost – you simply crop the original video from where the _temp file left off, then continue rendering.
Also, on Mac, you can hit the spacebar and get a preview outside of Topaz’s player by using Finder.
Topaz team, any word on if this feature will return?
Hello,
Could you send us an email at help@topazlabs.com with the full log files from the app?
To gather logs, please select Help > Logging and make sure that there is a check mark next to File Logging. Next, recreate the issue and then return to the Help menu and select > Get Logs for Support and attach the “logsForSupport” file to your reply.
I was so excited for version 4.
But now I’m absolutely disappointed with the new interface. Actually (for me) it’s a disaster.
Those who know Topaz will eventually come to terms with this. But every new user who doesn’t know Topaz will despair. I think you will see this in the sales figures over the next few months.
Crap, I thought it was a beta placeholder, I didn’t think it would make it to the final release, makes me worried that we STILL won’t be able to input frame rates over 120!
NOTE: I haven’t installed it yet, so I don’t know if the manual frame rate input has been truncated or not, will report back…