Proteus 3 black splotche blotting

[TicoRodriguez]

1. Black splotche blotches occur in Proteus 3.
2. DxDiag.txt (103.2 KB)
3. I use CLI.

"C:\Program Files\Topaz Labs LLC\Topaz Video AI\ffmpeg" -y -i %1 -sws_flags spline+accurate_rnd+full_chroma_int -filter_complex tvai_up=model=prob-3:scale=4:compression=0:details=0:noise=0:blur=0:halo=0:preblur=0 -an -c:v prores_ks -profile:v 3 -vendor apl0 -pix_fmt yuv422p10le "%~n1_xx.mov"

Several people have reported the same bug in the past.Seems to occur at 4x.

Seriously wrong blotting

I was using VEAI, Proteus 3, and got some very severe blotting in my Solaris movie I’m trying to upscale. At first I thought I had denoised too much, but even at default, minimal denoising, I get these very erroneous blots all over the place: [solaris] Those continue throughout the movie, making the process utterly useless.

https://community.topazlabs.com/t/veai3-creating-large-black-splotches-in-video-proteus-model-can-replicate-try-for-yourself/37357

[TicoRodriguez]

Other Video

[ida.topazlabs]

@TicoRodriguez If this is still occurring, please reach out to support and share the input and output file via
Submit File to Dropbox

[TicoRodriguez]

I haven’t resolved it yet, is it resolved?

[ida.topazlabs]

Hi! I marked as resolved, perhaps prematurely since I have not seen a reply from you, however, if you did reach out and Tony replied, please let me know

[ida.topazlabs]

We also had another thread open about this and the user there reported it as resolved.

[meimeiriver]

Oh, it’s definitely still occuring! I will prepare a sample for you.

[ida.topazlabs]

That would be wonderful, thank you! Please include the input file, exported file, and all reproduction steps as well as system profile and logs (if possible).

You can securely submit your files(s) to our Dropbox using the link below. Please be sure to send me a note to let me know you sent something.

Submit File to Dropbox

[ForSerious]

Mine is very much different than this.

[ida.topazlabs]

That is true! Still a similar issue with the same model

[TicoRodriguez]

Here are the test results with 3.2.2.
VEAI_error_input_lagarith.avi is a good test video because it is relatively reproducible.

CLI
“C:\Program Files\Topaz Labs LLC\Topaz Video AI\ffmpeg” -y -i %1 -sws_flags spline+accurate_rnd+full_chroma_int -filter_complex tvai_up=model=prob-3:scale=4:compression=0:details=0:noise=0:blur=0:halo=0:preblur=0 -an -c:v prores_ks -profile:v 3 -vendor apl0 -pix_fmt yuv422p10le “%~n1_xx.mov”

[meimeiriver]

logsForSupport.tar.gz (8.1 MB)

box-00.01.05.047-00.01.18.264.zip (30.8 MB)

Dropbox didn’t exactly work, but I attached the logs + a small sample of the movie I used. These were its settings:

As you can see, I tried a ‘pan & scan’ zoom (crop to fill), and started a preview at 24 seconds into the clip.

That is when things always go wrong: when you try to ‘enlarge’ the image. The process seems to run out of video memory somewhere.

N.B. This ‘enlargement’ is an issue by itself, btw. And Topaz is doing it wrong. No offense. Seriously. What Topaz appears to be doing (which you can deduct from the time needed to create the Preview), is that they upscale the image first, and only then ‘crop to fill.’ This is bad (regardless of blotches), as it means the resultant image, pre-crop, is way larger than 3840 x 2160 (both in height and width), and only thereafter is cropped to fit the 4k constraints. And processing that surplus area takes a lot of extra time. Best is just to pre-crop first. On a 1080p source file, with say typical 140px black bars, you’d start by cropping 248px (140x1.77) from both sides, plus 140px from top and bottom, and only then do you upscale to 3840x2160. By pre-cropping, you avoid wasting time (and memory!) processing a much larger image first. This is a bit beyond the scope of this post, though, but I thought it was interesting to already mention.

[ida.topazlabs]

Thank you! @meimeiriver @TicoRodriguez @ForSerious

This is all very helpful!

[meimeiriver]

Look at this one: v3.2.3 goes besers on ‘Auto’, even without any cropping;

Or

[ida.topazlabs]

Curious, if you do not use Auto does this still happen with this file?

[meimeiriver]

@ida.topazlabs

if you do not use Auto does this still happen with this file?

Yes, it does. I posted more instances of this occurance at:

new blotches weirdness

If you want, I can create a short sample again.

[ida.topazlabs]

Thank you, no need at this time. We are investigating this.

[sean.bires (seannyb)]

I’m enhancing some old DVDs and I noticed occasional large, black splotchy artifacts generated by the Proteus model at settings of 300% scaling or above. (I couldn’t reproduce it in Artemis or Gaia, or Proteus at 200% or 100% scaling settings. But 300%+ shows the artifacts.)

If you’d like to try it for yourself, here’s the input file. It’s a lossless AVI in the YUV420 colorspace using the free “Lagarith” codec.

VEAI_error_input_lagarith.avi

Thanks for looking into this. Proteus is the model I use 9 out of 10 times. I’ve seen other instances of these black splotches too, so this isn’t a one-in-a-million case.

[meimeiriver]

Looks like the exact same issue I had in 2.6.4: Seriously wrong blotting - #3 by meimeiriver

[TicoRodriguez]

I tried, but no error occurred.
What settings did you use to convert?
My setup is as follows: output to ProRes with CUI.

“C:\Program Files\Topaz Labs LLC\Topaz Video AI\ffmpeg” -y -i %1 -sws_flags spline+accurate_rnd+full_chroma_int -filter_complex veai_up=device=-2:model=prob-3:scale=4:compression=0.24:details=0.24:blur=0:noise=0.16:halo=0:preblur=0.08,scale=w=2880:h=2160:out_color_matrix=bt709 -color_primaries 1 -color_trc 1 -colorspace 1 -color_range tv -an -c:v prores_ks -profile:v 3 -vendor apl0 -pix_fmt yuv422p10le “%~n1.mov”