View Single Post
Old 06-04-2008, 02:59 PM   #9
alex_d
Addict
alex_d doesn't litteralex_d doesn't litter
 
Posts: 303
Karma: 187
Join Date: Dec 2006
Device: Sony Reader
Quote:
Originally Posted by lovebeta View Post
I support you. I think anyone who visits this forum and use your software will not be bothered by installing an api library.
well really, microsoft's automated that pretty well. the rasterfarian setup file will just download and install the right version of .net if it has to.
Quote:
Featurewise, I would like see the support of more formats. At lease mobipocket since I am a Kindle user too. This is not hard to implement and the key, I think, is still finding a high quality raster algorithm that is custom-made to the E-ink display. The current thickening is still as crisp as the native rendering. Are there any subpixel smoothing tricks?
More formats is something I was planning on. In terms of input, the ones most relevant to myself are PDF, CHM*, DJVU, and picture formats like JPG or TIFF. People should suggest what formats they'd like. The trick to support any input format is to have an easy way to render it to a picture. (Ie a command-line program or a library.) For output, I would obviously support the Reader and as many other devices as I could. The file formats are a question. Since each device usually supports several (the Kindle does too, right?) it might make sense to just offer a generic format (tuned for the device) instead of the proprietary one. This isn't too clear an issue, because not all formats will work as well. On the Reader, for example, PDF, even if it's just used to bundle images, is slower and crops the picture vs BBeB. If anyone is knowledgeable about their device please share what you know.

For the Kindle, the currect post-processing should work just fine. It's just using the same one as the Reader, right? For an LCD device, I'd definately have to tweak it. eInk is a bit blurry and low-contrast, so I found that an especially harsh filter looks best. (This is why I warn, in the preview, not to judge the picture by how it looks on your monitor.)

Subpixel smoothing is only for color screens. I do use anti-aliasing.

*(ms help files... it's weird, but a lot of books come in this format since it's basically a compressed single-file website with a simple ui)

Quote:
Originally Posted by athlonkmf
The LRF-format has an option to use one thumbnail-image. Bookdesigner can set something like that.
It won't be viewable in the sony reader, but it's available in the readersoftware. And who knows, maybe in the future a firmware would be out which would display the coverthumbnails for each book.
Oh. Yeah, i've wondered what that was in the lrf sources. Never realized what it does since I don't use Connect. Ok, I'll see if I can put that in.

Quote:
I've set my version to run at 8 cores, but img-processing isn't even the real slowdown. It makes optimal use of the CPU, but eventually creating an LRF could take hours and another queued item can't start before that lrf is created.
Right, the dumb lrs2lrf bug. Actually, I've already got MSH_LRSparser working and it shouldn't have this problem.
alex_d is offline   Reply With Quote