View Single Post
Old 02-19-2015, 11:28 PM   #1009
willus
Fuzzball, the purple cat
willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.willus ought to be getting tired of karma fortunes by now.
 
willus's Avatar
 
Posts: 1,303
Karma: 11087488
Join Date: Jun 2011
Location: California
Device: iPad
Quote:
Originally Posted by wdq4587 View Post
I have tried (under resolution 699x1006)

-m 0.122s,0.144s,0.122s,0.81s

before my last post. It did not work as I expect, I mean the result has more area included than I expect compare to:

-m 74p,145p,74p,81p

I have not test more to see if I've made a mistake.

...
I made a mistake in my example of the -m option using the 's' unit (three posts back). I have edited that post and fixed it, but let's say your source file is internally rendered at 700 x 1000 pixels using your specified input dpi value and you want to crop it as above (74p,145p,74p,81p). Then the equivalent 's' values would be 74/700,145/1000,74/700,81/1000, e.g.

-m .106s,.145s,.106s,.081s

The advantage of specifying this way is that the crop margins are independent of the resolution at which the source file is rendered.
willus is offline   Reply With Quote