View Single Post
Old 01-28-2016, 06:11 PM   #828
badbob001
Fanatic
badbob001 ought to be getting tired of karma fortunes by now.badbob001 ought to be getting tired of karma fortunes by now.badbob001 ought to be getting tired of karma fortunes by now.badbob001 ought to be getting tired of karma fortunes by now.badbob001 ought to be getting tired of karma fortunes by now.badbob001 ought to be getting tired of karma fortunes by now.badbob001 ought to be getting tired of karma fortunes by now.badbob001 ought to be getting tired of karma fortunes by now.badbob001 ought to be getting tired of karma fortunes by now.badbob001 ought to be getting tired of karma fortunes by now.badbob001 ought to be getting tired of karma fortunes by now.
 
badbob001's Avatar
 
Posts: 556
Karma: 1102020
Join Date: Sep 2009
Device: Kindle Keyboard (rip), Kindle Voyage, Fire Tablet 10 '17, iPad '19
Testing the dev branch version...

For --croppingpower and --croppingpowerpage, what do the input numbers mean? Are they percentages from 0.0 to 100.0? So lower = less cropping; higher = more cropping?

When cropping margins/page numbers, it looks like it will stop cropping once the image dimensions is within the device dimensions. This can result in margins/page numbers remaining in the page, despite crazy high croppingpower/page settings. I thought if I use the -upscale option, it would continue to crop all the margins/numbers and then upscale the image, but it doesn't. Anyway I can override this?

Also, what does High Quality Panel View do? I thought Panel View just tells the device where the Panels are and not related to the image size but the resulting file is almost double in size.
badbob001 is offline   Reply With Quote