[BUG] - Cannot set 0 value on Pixelate filter about obs-composite-blur

[FiniteSingularity]

Thank you for opening the issue. I can see how it would be a little confusing, however this is actually working as intended, as a pixel at size 1, is just the original pixel (so in terms of pixelization, 1 pixel is zero blur). We could allow the value to go to zero, as there is a check to see if the value is 1 or smaller, it just passes through the original frame. Is there any particular use case where having it go to zero is needed? Would it be less confusing to allow the slider to go to zero?

[JDDoesDev]

I didn't have anyone in chat answering when I was attempting to use the transition, but in studio mode when enabling and disabling at 1.00 it seemed that there was a bit of a blurring, although minor. Let me see if I can find it in the VOD.

[FiniteSingularity]

Its definitely possible. It may have something to do with the float error that comes in, where a value of 1.0 is actually 1.0000001, which is greater than 1, so it isn't passing through the source. If that is the case, I can set an epsilon value to catch float rounding errors.

[JDDoesDev]

https://www.twitch.tv/videos/1912841249 at 4:02:20 roughly.

There is some minor blurring, but after reviewing the VOD it is almost imperceptible. I'll let you take a look and decide if it's enough to put in a fix for, however I'm willing to close this as invalid after checking the VOD.

[FiniteSingularity]

I am going to close this one for now, as "works as expected." I am still considering allowing a "dummy" zero value for Pixelate and Dual Kawase, but that would come in the next feature release.

[FiniteSingularity]

@all-contributors please add @JDDoesDev for bug

[allcontributors]

@FiniteSingularity

I've put up a pull request to add @JDDoesDev! 🎉