omkar-tenkale / PicTools-IssueTracker

1 stars 0 forks source link

Optimize tool give option to set quality #8

Open omkar-tenkale opened 4 years ago

omkar-tenkale commented 4 years ago

ACDSEE recommends 85% for example. It depends of the library version.

Submitted on behalf of Bakli

omkar-tenkale commented 4 years ago

It compressed with 80 quality by default and results look good for camera images Also the blog recommends 80 as a good tradeoff betwen quality and size http://regex.info/blog/lightroom-goodies/jpeg-quality

Attach a few samples with poor quality results

Adding a slider here will make things more complex for this tool But moreover it'll just be another compress tool with automatic folder import option

JonDous commented 4 years ago

I don't understand the case. The point was in the tool's description says the all photos will be compressed using 70% jpeg.

I've offered to let user choose the quality coz if I convert photo with lots of small details, jpeg can't compress without glitches. The ACDSee by default compress to 85, dashchan to 90%.

JonDous commented 4 years ago

Choose folders are make sense. Coz Xiaomi phones add screenshots to dcim and Google photos backup them as photos.

Different photo apps use different folders. You can add the option to "show more". By default shows user the folder which will be scanned.

Or something like this Screenshot_2020-09-22-00-05-59-250_com.google.android.apps.photos.png

omkar-tenkale commented 4 years ago

The point was in the tool's description says the all photos will be compressed using 70% jpeg.

The optimize tool description says its 75% not 70. In code its 80,strings issue,

And 80 is good

I'm planning big improvements for optimize tool. eg name change to something like FOLDER COMPRESS Optimize seems misleading and confusing Custom folder selection option or even multiple folders Custom quality selection option Replace original option Cancel process option, as its a lengthy process with 1000s of images

But this is not planned in next version

This issue will be closed when that's done