I've just had the opportunity to test my folio on the new iPad. First, I'm happily surprise by the quality. Honnestly, it's okay.
I've read a article with the PDF rendition, and here is the behavior:
- when you arrive on the page, the text looks very "aliased". It really looks like a classic JPEG rendition.
- then if you pinch/zoom-in just a little bit, you can start seeing the PDF. The text is rendered and it looks perfect.
I guess that it's the classic behavior of the viewer. First, it displays a JPEG and then if you zoom-in, it's using the PDF. I guess that it's for optimization reasons, smooth transitions, etc...
Can we imagine a new behavior ?
- the reader opens a new page, and sees the JPEG.
- once the page loaded, the DPS viewer starts rendering the PDF with high-definition text
- if the user taps the screen (to move to the next page for instance), then the reader displays the JPEG again.
That would explode the file size and defeat the purpose.
If it’s taking that long to pop into focus something’s wrong. Yes, there’s a slight delay but it’s certainly nothing that needs a workaround.
I think I need to attach two screenshots to explain what it the current behavior.
Of course, you need to open the screenshots at 100% with PhotoShop for instance to get the point.
Again, it's just an article withthe PDF rendition.
This is the screen when I arrive on my page. You'll see that the text is kind of blurry.
Then I zoom-in (pinch) just a little bit. Maybe by 1%, and I obtain this:
The quality of the text is MUCH better once I zoom-in a little bit. That's why I feel that the viewer is rendering the PDF only if you zoom-in. Otherwise, it looks like it's using something else (like a JPEG renditon of the PDF page).
My request is: Could the viewer just launch the PDF rendition even if the reader doesn't zoom-in ? Then I would obtain automatically the quality of the second screenshot.
PS: It looks like this forum will resize my images and that we won't be able to feel the difference. I've just uploaded the original screenshots here:
I know the effect but I have never needed to zoom in on the page in order to get the text to pop in.
It takes a second or so, and is much more noticeable on the original iPad than it is on the new one.
I don't think that's accurate -- I experience what Michael does. On a PDF folio, when you get to a page, the type looks a bit pixelized/jpeggy. It never "pops in." Enlarge it just a bit and the PDF/vector-ness pops in, segment by segment. When you pinch back out to 100%/full view, the text goes back to its slightly pixelized version. Boy it would be nice to have the text look crisp at 100%, when most people will see it.
So -- is there something we are doing wrong, that our text never "pops into" focus in a PDF folio? (this is on an ipad3, with v18 tools)
You know what? I think I need to take that back...partially.
Looking at this a bit more carefully (I have old tired eyes <g>) I think I do see what you're referring to in the Content Viewer.
The good news is that I don't see it in an app that I created using the viewer builder.
I've heard about this issue before.
My understanding is that the v18 viewer doesn't handle PDF folios right on
Only the v19 viewers built after release of the ipad3 are ready to go.
I haven't seen this failure of PDF pages to redraw before zoom since I installed the v19 viewer in which renditions work properly. I haven't tested 1024 folios on the iPad 3 -- just 2048 folios. I'll ask around to see if there was a fix.
I've noticed the same issue viewing 1024 PDF folios on the new iPad. We haven't tried any 2048 folios yet because all of our clients run on the iPad2. The text looks like it has choppy JPEG compression but even a slight zoom cleans it right up to how it should appear.
We have been testing on iPad3 using an IPA 2048 viewer
The test folio comprises:
Existing InDesign document that has been set to new size of 2048 deep.
All content has been scaled up to this new size
Rescaled images are now half the effective pixel value. For the next live issue they would be to the iPad3 resolution.
Folio has been exported in PDF format.
As yet there is no Adobe iPad Viewer to test our hires mag only this laborious sideloading method where single articles can be viewed but not the mag as a whole (folios have to be located in a hidden Temp folder). As the desktop viewer doesn’t display PDF folios as a workflow it is impossible.
Although the text looks great on iPad3, rext within interactive features (like the sliders) doesn’t zoom in high quality.
Also on pages with full page pan/zoom images moving to next page difficult.
We need a new Content Viewer and we need it fast! We want to be able to boast that our next issue (Photographers i Magazine) has been built from the ground up to support retina display.
Why haven't you used the Viewer Builder to create a custom Adobe Content Viewer?
That's what we have been doing Bob but we have a multinatuional team who need to collaborate on the development of our magazine and to do that we need a regular Conent Viewer with Cloud based folios.
I don't understand. The custom Adobe Content Viewer is a regular Content Viewer with cloud-based folios. The Adobe Content Viewer you custom build can do everything the store version does, plus it lets you use Preview on Device. You just need to make sure that you include the iPad UDIDs of your developers in your dev mobileprovision file, and you can give everyone the content-viewer.ipa file and have them sideload it to their iPads. They don't even need to remove the store version of the Content Viewer.
Europe, Middle East and Africa