[BUG] - Pixelate causes strange behavior when set to 1px

[JDDoesDev]

Describe the bug Recently upgraded to 1.0.3. I use a move value transition to increase pixel size based on channel redeem, with initial setting of 1.00. After upgrading the filter creates a trail of the video. Only seems to be a problem when using chroma key. See image:

To Reproduce Steps to reproduce the behavior:

1. Go to create new composite blur filter
2. Select Pixel (Any variation works)
3. Set pixel size value to 1.00
4. Notice trail
5. Increase pixel size value to >1.00 (1.01 worked)
6. Notice trail disappears

Expected behavior No trail.

Screenshots If applicable, add screenshots to help explain your problem.

Environment

• OS/Version: [e.g. Windows 11]
• OBS Version: [e.g. 29.1.2]
• Composite Blur Plugin Version: [e.g. 1.0.3]
• Blur Algorithm/Type: [e.g. Blur, Area]

GPU

• GPU make/model [e.g.- nvidia RTX 3070]
• GPU VRAM [e.g.- 8Gb]

Additional context Add any other context about the problem here.

[FiniteSingularity]

Thank you for the issue. I will take a look this afternoon.

[FiniteSingularity]

Confirmed the bug, and it happens on all blur types. Working on a fix now.

[FiniteSingularity]

Please let me know if the PR fixes your issue. Even if not, it'll be merged in shortly as it could fix other potential issues as well.

[JDDoesDev]

@FiniteSingularity can confirm issue is fixed with new PR.

[FiniteSingularity]

Glad to hear it! Just merged in the PR. Thanks for opening the issue @JDDoesDev.