ProRes 422HQ source files all crash

[Selur]

I uploaded a new dev which, can 'handle' those files, if you force the usage of Vapoursynth ("Filtering->Vapoursynth->Misc->Script->Always use Vapoursynth").

That said, I strongly advise not to use ProRes in Topaz if their outputs are all this broken.
The workaround I added basically:
a. handles the input as YUV
b. assumes the color matrix as Rec.709
=> you should report this to their support and this is something they messed up.

Cu Selur

[gittinit]

Thanks, I'll give it a try. I've been testing all the steps in my workflow, and it seems Topaz has trouble with the default Hybrid ProRes encoding. When I set VUI matrix as "bt709" rather than "auto" in step 1 (deinterlace and encode to ProRes from mpeg2), Topaz handles the file correctly in step 2, and Hybrid works without problems in step 3 (the final re-encode from ProRes to AV1/H265/whatever).

So until Topaz fixes the problem, users should be sure to select "bt709" as the matrix if they first deinterlace their source material in ProRes with Hybrid. I'm kind of surprised I'm the first to encounter this issue, because it seems that deinterlacing source material before feeding it to the AI models is the generally accepted best practice in the Topaz community.

[Selur]

Not using Topaz at all.
¯\_(ツ)_/¯

[gittinit]

Just tried the new dev, and it works! Sorry for coming here first when the problem is Topaz. It's incredible (and embarrassing) that the support for a one man free app is better than a $300 commercial product.

As for whether to use Topaz at all, I understand the purists who think even the higher qtgmc presets look too processed/ lose too much detail, but for me 2x upscaling with the right model and tuning can give amazing results that look significantly better on modern 4k displays. But it's easy to mess up and get weird textures in backgrounds and hair, waxy skin, and demon faces. And even if the visual quality is good, you apparently still get badly encoded files!