Avoiding doing lpc-...
 
Share:
Notifications
Clear all

May 27 2026 APP 2.0.0-beta45 has been released !

Fully Multi-Threaded LNC, many improvements for the registration engine, platform upgrade, and further tuning of internal memory consumption and memory release back to OS.

Apr 14 2026: Google Pay, Apple Pay & WeChat Pay added as payment options

Update on the 2.0.0 release & the full manual

We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version.

Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.

 

Avoiding doing lpc-cbg again if cropping a second time...

3 Posts
2 Users
1 Reactions
1,155 Views
(@col)
Neutron Star
Joined: 5 years ago
Posts: 127
Topic starter  

Not a big issue, but is an annoying one from time to time.

After cropping an image to remove stacking edges, I usually do light pollution removal to get the crop-lpc-cbg after the filename.

However, if I decide to crop again it becomes filename-lpc-cbg-crop. Here, it seems APP only sese the last entry, i.e. -crop, and asks again for lpc to be done when there is no need*.

Can this be changed/modified so that APP sees the previous history of the file processing to avoid doing LPC again?

* EDIT: I can appreciate if cropping a second time changes the overall background so that lpc a second time is prudent, maybe you can confirm? In some cases, I see no need. 

image

 

Best wishes, Col



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5308
 

Hi @col,

Yes, that is a valid request. The metadata should not be removed with cropping, I have made a ToDo on my list to fix this 😉 Thanks !

Mabula



   
Kullumm reacted
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5308
 

Hi @col,

It has been a while, but this issue will definitely be fixed in the next release 2.0.0-beta33 🙂

Mabula



   
ReplyQuote
Share: