Bug 412981

Summary:	Not possible to apply the pixel filter to a second region
Product:	[Applications] kdenlive	Reporter:	postix <postix>
Component:	Video Effects & Transitions	Assignee:	Vincent PINON <vpinon>
Status:	RESOLVED MOVED
Severity:	normal	CC:	fritzibaby, postix, snd.noise
Priority:	NOR	Flags:	fritzibaby: timeline_corruption+
Version First Reported In:	19.08.2
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	New automask is replaced by previous one.

Description postix 2019-10-15 16:24:12 UTC

SUMMARY

It is not possible to add a second rectangle to pixelate a second area,
but instead the first filter is just moved.

Comment 1 emohr 2019-10-29 19:29:31 UTC

Do you work with automask. If so you can put a second automask on the clip to have a second region to pixelate.

Comment 2 postix 2019-11-04 19:22:27 UTC

(In reply to emohr from comment #1)
> Do you work with automask. If so you can put a second automask on the clip
> to have a second region to pixelate.

That did not work for me, it always replaced the previous one for me.

Comment 3 postix 2019-11-04 19:24:03 UTC

Created attachment 123721 [details]
New automask is replaced by previous one.

Comment 4 postix 2019-11-04 19:27:20 UTC

(In reply to Postix from comment #3)
> Created attachment 123721 [details]
> New automask is replaced by previous one.

Ah, the issue about automask is that the previous selected area cannot be changed or deselect anymore once a another automask region has been set. All individual automask regions should stay controllable.

Comment 5 emohr 2019-11-04 19:32:54 UTC

For 2 pixelate fields you have to apply 2 times the automask effect on the same clip.

Comment 6 farid 2021-03-24 18:21:34 UTC

Hello and thanks for your report. 

The automask effect if being rewritten for the next major release of MLT (version 7). We are tracking progress of this task here in case you'd like to follow up: https://invent.kde.org/multimedia/kdenlive/-/issues/991

Will close this issue here. Do test after the release and let us know if it still happens.