Skip navigation
RCPilotMagazine
RCPilotMagazine Calculating status...
Currently Being Moderated

iPad 3 Performance is Poor - what to do?

May 27, 2012 12:37 PM

Tags: #dps #ipad #3 #slow

Hi Folks,

 

  We publish RC Pilot Magazine for Kindle, both iPad resolutions and Android.  We have found that the iPad3 version has issues with page turning inside larger articles and from one article to the next (but to a lesser extent).

 

  We have tried rendering in PDF, PNG and JPG (we test the same article with each) and we have tried creating the rendition in 2048 and then 1024 (except the images) and upsizing.  Nothing seems to work.  There is a 1-2 second deley from the time you swipe until the page actually turns.  The articles in question are roughly 25MB in size all in.

 

  This has to be either a processor issue.  We have no other apps running.

 

2907 Views   15 Replies   Latest reply: spin_dan, Jul 3, 2012 1:21 AM
 
Replies
  • Bob Bringhurst
    3,433 posts
    May 29, 2007
    Currently Being Moderated
    1. Bob Bringhurst,
    May 27, 2012 1:11 PM   in reply to RCPilotMagazine
    Report

    Can you try deleting and reinstalling the Adobe Content Viewer (or your viewer) app? See if that makes a difference.

     
    |
    Mark as:
  • mkranitz
    Currently Being Moderated
    2. mkranitz,
    May 27, 2012 5:25 PM   in reply to Bob Bringhurst
    Report

    We ended up reinstalling Content Viewer but that did not work. Then, we rebuilt and tested the issue one article at a time using PDF where possible and jpg where PDF could not support certain features.

     
    |
    Mark as:
  • RCPilotMagazine
    Currently Being Moderated
    4. RCPilotMagazine,
    May 27, 2012 10:30 PM   in reply to Bhaskar J Lahkar
    Report

    We've read these guidelines and they do not offer much.

     

    I do not understand why publishing the 2048 resolution first should help anything given the warning from Adobe to publish renditions of the same edition with EXACTLY THE SAME DATE.  If the reader software were working correctly, it would be able to determine the proper resolution without reference to the published date (which, again, you advise to be identical). 

     
    |
    Mark as:
  • Bhaskar J Lahkar
    Currently Being Moderated
    5. Bhaskar J Lahkar,
    May 27, 2012 10:56 PM   in reply to RCPilotMagazine
    Report

    If the device finds only the 1024 by 768 and no renditions on the first day of release, it will ask the both ipad2 n ipad3 to download the 1024 folio and later renditions will not help. Renditions do determine the device resolution but when it finds only 1024 folio, it is bound to offer both ipad2 n ipad3 to download it because there is no way dps will know whether 2048 is coming later or not. Best is to publish the 2048 first and then the 1024 as 2048 will not offer a download to iPad 1 n 2. 1024 with PDF for ipad3 is an option if you wish to reduce production time but IMO 2048 for ipad3 is the best option. Machines do always determine the best options without fail... We humans do not.

     
    |
    Mark as:
  • Nathan Marroquin
    Currently Being Moderated
    6. Nathan Marroquin,
    May 29, 2012 9:23 PM   in reply to RCPilotMagazine
    Report

    Were you able to resolve the performance problem? If so, what did you do? Did the article you show have any overlays on it? Were either of the adjacent articles smooth scrolling? Or did one of the adjacent articles contain very large overlays?

     
    |
    Mark as:
  • Johannes Eckert
    Currently Being Moderated
    7. Johannes Eckert,
    May 29, 2012 9:29 PM   in reply to RCPilotMagazine
    Report

    RCPilot,

     

    the exact date refers to the publication date in your metadata field (folio

    producer organizer).

     

    you then should publish these metadata-identical folios separately after

    each other.

     

    —johannes

     

    (mobil gesendet)

    Am 28.05.2012 07:30 schrieb "RCPilotMagazine" <forums@adobe.com>:

     

    **

       Re: iPad 3 Performance is Poor - what to do?  created by

    RCPilotMagazine <http://forums.adobe.com/people/RCPilotMagazine> in *Digital

    Publishing Suite* - View the full discussion<http://forums.adobe.com/message/4444192#4444192

     

     
    |
    Mark as:
  • Sushimania
    Currently Being Moderated
    8. Sushimania,
    May 30, 2012 6:34 PM   in reply to RCPilotMagazine
    Report

    I have a same problem. In my iPad3, the performance is poor, too. Please, help me and let me know how to fix it.

     
    |
    Mark as:
  • spin_dan
    Currently Being Moderated
    9. spin_dan,
    Jun 20, 2012 2:47 AM   in reply to RCPilotMagazine
    Report

    Any resolotion to this problem?

     
    |
    Mark as:
  • spin_dan
    Currently Being Moderated
    10. spin_dan,
    Jun 20, 2012 2:47 AM   in reply to Bob Bringhurst
    Report

    Any resolotion to this problem?

     
    |
    Mark as:
  • mkranitz
    Currently Being Moderated
    11. mkranitz,
    Jun 20, 2012 6:48 AM   in reply to spin_dan
    Report

    We have seen no resolution to this issue. 

     
    |
    Mark as:
  • spin_dan
    Currently Being Moderated
    12. spin_dan,
    Jun 20, 2012 6:59 AM   in reply to mkranitz
    Report

    Thanks for the reply. This is very frustrating!

     
    |
    Mark as:
  • PadraicWoods
    Currently Being Moderated
    13. PadraicWoods,
    Jul 2, 2012 2:40 AM   in reply to RCPilotMagazine
    Report

    We are suffering from the same problems.

     
    |
    Mark as:
  • mstebby
    Currently Being Moderated
    14. mstebby,
    Jul 2, 2012 4:20 PM   in reply to PadraicWoods
    Report

    We're experiencing the same issue. Flipping to the next page is very slow 1-2 seconds. The buttons have a 1-2 second delay. MSO run very slow.

     
    |
    Mark as:
  • spin_dan
    Currently Being Moderated
    15. spin_dan,
    Jul 3, 2012 1:21 AM   in reply to RCPilotMagazine
    Report

    Thanks for all the silence aodbe. Really helpful…

     

    Ok, so we somehow fixed the problem. By pure fluke, so this probably wont be of much use to the rest of you but I thought I would share anyway.

    You all have probably tried this, but it worked in the end for us. 

    —

    We deleted content viewer on the iPads (1&3), deleted our preferences in users/library/preferences (Mac), re-installed content viewer, opened then re-saved both folios following the guidelines (be sure to output in PDF format) and published. Then, BOOM, for some reason it started to work fine again. And has been fine since!

     

    No idea what the problem was and apart from the re-install and re-save, our process was exactly the same.

     

    Brings me right back to the old days of Flash

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (2)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points