Actually I didn't get why masks are getting copied when I ask only particular module settings. But anyway I hope it will change soon, opening every file (especially when they are so slow) is just so time consuming. It should be 'all at once' action :)
On Tue, 2018-04-17 at 18:27 +0200, Ulrich Pegelow wrote: > You don't need to do this manually. Just go into the mask manager > (left > hand panel in the darkroom view), press the right mouse button. On > the > menu that appears you select "cleanup unused shapes". > > In your case the huge number of invisible shapes comes from the spot > removal tool. The root cause lies in a combination of two facts. > darktable does not delete shapes automatically and spot removal > shapes > do not appear in the mask manager. So even if you reset the spot > removal > tool all shapes created will still exist in the data set and you do > not > even know because the mask manager does not tell you. We should > consider > how to change this behavior. > > In the time being you can manually clean up unused shapes with the > method described above. > > ulrich > > > Am 16.04.2018 um 10:55 schrieb Timur Irikovich Davletshin: > > Well, I was able to edit them with sed script to remove all masks, > > but > > parsing XML to find used/unused masks is beyond my skills (I'm not > > familiar with XMP standards). I believe future DT releases should > > sort > > this out in some way. At least for this issue is very critical, it > > slows down opening/closing files in my library multiple times. > > > > On Mon, 2018-04-16 at 10:19 +0200, sturmflut wrote: > > > Hello, > > > > > > I can confirm this for the latest version in the darktable-2.4.x > > > branch > > > (commit edf1168371be288f071986d93a47fb3e082573de). The sidecar > > > files > > > seem to contain an awful lot of masks, but I can't seem to see > > > which > > > module even uses them? > > > > > > cheers, > > > Simon > > > > > > > > > On 15.04.2018 20:28, Timur Irikovich Davletshin wrote: > > > > It looks like I was able to find what action causes this > > > > problem. > > > > > > > > Steps to reproduce: > > > > > > > > 1. Download, unpack and import as folder — https://drive.google > > > > .com > > > > /ope > > > > n?id=14sZLgnpZSV5W3pw1K_8owHW29Heq9EWz (don't pay attention to > > > > content > > > > and settings) > > > > 2. Choose second picture and click (in lighttable mode) copy > > > > history > > > > stack and choose, let's say, 'shadows and highlights' settings. > > > > 3. Apply it (paste) to first picture, open it, compress history > > > > stack > > > > and close DT. > > > > 4. Now compare XMP files, first one is twice bigger than second > > > > one > > > > (in > > > > my case ~700kB vs ~1400kB). Meanwhile in darkroom mode history > > > > stack > > > > looks the same. > > > > > > > > Can anyone comment, what is going on here? > > > > > > _________________________________________________________________ > > > ____ > > _____________________________________________________________________ > ______ > darktable developer mailing list > to unsubscribe send a mail to darktable-dev+unsubscribe@lists.darktab > le.org > ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
