Custom DPI
Moderator: peterZ
Custom DPI
The tutorial shows 6 lines = 1nch (usually) which turns out to be 180 in that case, but my book has just 3 lines in 1 inch, and if I select 3 lines in an image editor, it shows 240px (height), should I set that as my DPI?
Re: Custom DPI
It's possible that Arabic text uses different standard line sizes from Roman and Cyrillic characters. I'd recommend going with what you've actually measured on the page instead of the tutorial guidelines for your books.
The opinions expressed in this post are my own and do not necessarily represent those of the Canadian Museum for Human Rights.
Re: Custom DPI
Right, so I measured (physically) 3 lines to be approx 1inch. And using the marquee tool in an image editor, 3 lines are 240px in height.
I'm not sure what should I set the DPI to.
Thanks!
I'm not sure what should I set the DPI to.
Thanks!
Re: Custom DPI
You should enter the DPI as 240 in that case. DPI is the number of pixels divided by the number of inches. Since you've measured 240 pixels to be 1 inch, you can go with 240/1 which gives you 240DPI.
For more detail you can check my blog post on DPI, but you should be okay with the measurements you've done here.
For more detail you can check my blog post on DPI, but you should be okay with the measurements you've done here.
The opinions expressed in this post are my own and do not necessarily represent those of the Canadian Museum for Human Rights.
Re: Custom DPI
Misty is quite right. The number of pixels that corresponds to 1 inch is your DPI.
Scan Tailor experimental doesn't output 96 DPI images. It's just what your software shows when DPI information is missing. Usually what you get is input DPI times the resolution enhancement factor.
-
- Posts: 290
- Joined: 20 Jun 2009, 12:19
- E-book readers owned: SONY PRS-505, Kindle DX
- Number of books owned: 9999
- Location: Grand Rapids, MI
- Contact:
Re: Custom DPI
Does it make any sense to image a ruler then count the pixels between the 1" and the 2" marks? Then use that as your DPI estimate.
Re: Custom DPI
It's a chicken and egg problem. You don't know how far apart to draw you 1'' and 2'' marks until you know the DPI.StevePoling wrote:Does it make any sense to image a ruler then count the pixels between the 1" and the 2" marks? Then use that as your DPI estimate.
Scan Tailor experimental doesn't output 96 DPI images. It's just what your software shows when DPI information is missing. Usually what you get is input DPI times the resolution enhancement factor.
- daniel_reetz
- Posts: 2812
- Joined: 03 Jun 2009, 13:56
- E-book readers owned: Used to have a PRS-500
- Number of books owned: 600
- Country: United States
- Contact:
Re: Custom DPI
If we had people to hack on the code, we could make a "DPI page" with some markers on it to determine DPI automatically. You'd just print a copy of this page and shoot it once. As it is, this is in no way a feature request, just more blue-sky thinking.
I wish more people would specify their Scan Tailor wishes as blue-sky thinking. We can imagine anything... now we just need to recruit a talent pool that can implement it alongside Tulon.
I wish more people would specify their Scan Tailor wishes as blue-sky thinking. We can imagine anything... now we just need to recruit a talent pool that can implement it alongside Tulon.
- strider1551
- Posts: 126
- Joined: 01 Mar 2010, 11:39
- Number of books owned: 0
- Location: Ohio, USA
Re: Custom DPI
I read the original question differently. I always do a reference image where I lay a flat plastic ruler on the page. When I load my images I use gimp to count the pixels within an inch on the ruler, and then ImageMagick to set the dpi in the files (mogrify -density).Tulon wrote:It's a chicken and egg problem. You don't know how far apart to draw you 1'' and 2'' marks until you know the DPI.StevePoling wrote:Does it make any sense to image a ruler then count the pixels between the 1" and the 2" marks? Then use that as your DPI estimate.
Re: Custom DPI
Yeah, I got the question wrong. Seems like a good solution then.
Scan Tailor experimental doesn't output 96 DPI images. It's just what your software shows when DPI information is missing. Usually what you get is input DPI times the resolution enhancement factor.