Installation worked out great in my case.
I tested the Android "preview on device" -option, using my Motorola Xoom. This worked out from the first time.
The only thing I didn't like (it's a detail, I know) is the folio panel doesn't say "motorola xoom", as a device name it gives me this 20+ long character number.
I tried looking up some info about this but wasn't able to change this anywhere. I figure it's just a device name I can change somewhere...
Bob B you are answering the easy questions not the hard ones! Get someone on this forum full time 24/7.
I am once again getting the "Cannot Connect...." message and this time updating a small stack has made no difference.
I NEED AN EXPLANATION!!!!!!!!!! I have a CEO in the UK and Executive Editor in the US both complaining that they too are now getting the same message.
Adobe your system is hopeless and your response pathetic, as Martin Ler said you are charging for third rate Beta software.
Is there a maximum stack size? I don't want some vague answer, I want you to say to me that you guarantee that under any circumstances that a stack size of ???MB will download to the iPad. In the prerelease program I had no problem downloading a 650 MB folio. GET IT SORTED OR WE WILL BE OFF TO WOODWING.
Graham,
Can you please clarify if you are talking about content which is being previewed from your Acrobat.com account vs. published on the fulfillment server? I'm unclear whether you might be using the workaround to publish privately. I am currently assuming the former. We can look at the specific activity for the users that are access the servers if you provide the user names to us at digipub-feedback@adobe.com.
Michelle
We have a modified Adobe Content Viewer waiting for Apple approval that will increase the timeout value when dealing with large folios. Until that viewer gets approved you will see timeouts in the viewer trying to display articles with large videos or articles greater than 80 to 90 mb in size. Feel free to vent on the forums if it makes you feel better but I'm pretty sure that isn't going to make Apple move any faster.
As mentioned before DPS customers currently have the ability to publish a private folio for viewing on device as a workaround for this problem.That serves the folio from the distribution service instead of via the ADC bridge.
The workaround doubles my work to proof and publish.
It means I upload and update all the articles in a test account until all revisions have been made, then I have to go and rebuild it signed-in to the actual provisioned account. Otherwise, even though it's being published "Privately" the proofing file will bet published to our existing app in the iTunes store.
When Matt Laun walked me through this workaround the first time, he said there was a bug that would cause it to actually be published to iTunes even though we were publishing "privately" so we had to get a test ID provisioned and use that to do the private publishing workaround.
If that bug has been fixed, I would love to know about it but I cannot take a chance that an issue that is still being proofed and revised shows up as a new issue in the iTunes app.
I thought I had followed up to let you know that the new account would not be necessary. My apologies if I did not. John M tested to confirm that the defect he had suspected would require those steps did not cause the content to appear for end users in a custom viewer app. So you can revert to using your standard publishing login to do the private/free preview method.
Please hang in there, we've worked hard to fix this and now are just waiting for Apple's approval.
Sincerely,
Matthew
John
Your response leaves me even more frustrated. As far as I understand it someone without a provisioned account will have to accept a second rate service. This will not encourage them to sign up; rather it will drive them into the arms of your competitors.
I have a large international client who has trusted my judgement in advocating ADPS which itself was based on my experience during 9 months of the prerelease program during which things were progressing well. They have signed and are waiting for their account to be provisioned but are having serious second thoughts about their decision to go with Adobe.
Why is your Acrobat.com server infrastructure so woefully inadequate? You have had so many warnings and yet you still do not seem to appreciate the seriousness of the situation. Why wasn’t the timeout value adjusted when the horrendous problems with Acrobat.com first surfaced? This forum is evidence that all is not well and using the excuse that it is Apple’s fault just won’t rub. Why did I have 10 days of trouble free downloading many of the same files that now seemed to have crashed the system, Even earlier this morning it was ok then having made some small changes to a to several articles suddenly I start getting the “Cannot Connect...” error message. None of my videos are larger than 65 MB although we have quite a lot of almost full screen images in Object States that I know are not resampled when the folio is created and so most images are a sensible size.
Although it pains me to say this about a company whose products have been market leaders in creative software for many years Adobe you have got to get a grip of this never ending sequence of calamities. Someone in the organisation isn’t listening, whoever it is maybe they should spend some time monitoring this forum.
Hi Graham,
I am fully agreed with you that Adobe's Guys is not listening or seeing the forum. Many DPS users grapple with this problem and me too. I had posted the problem many times but nobody solve the problem.
I am very desperate on this. However, I was the member of Pre-release programe of DPS since Drop8.
Looking forward to hear from Adobe.
Not exactly.
I had some problems with putting new version of beta software to work, while older, even much older version still stayed on the system. This is my speculation, that similar conflict may exist between beta and actual software.
I think it is worth trying to remove the beta stuff.
Finally at 10 pm last night out of desparation I decided to Archive the folio on the iPad and start over. Applying Bob B's bizarre workaround (Using View whilst download is in progress) I managed to get a couple of folios downloaded when I was again confronted with the Download paused message so I came out of the App, fired up the Content Viewer again and repeated the process several times but without sucess so I gave up. This morning I continued the process and the remaining folios downloaded without a problem. WHY????????????????????????? This hit and miss functionality is totally unacceptable and your explanations never offer any way of resolving the download problem.
Tomek - i have solution ![]()
you at least put me on the right way - delete something ![]()
First i deleted everything about older version on my computer - no luck.
Then i realized, that if tools are working under other user on same computer, and Adobe apps must work under newly created user, then i can safely remove EVERYTHING what have something to do with Adobe in my user folder. And that's exactly what i did. I deleted Adobe folders in Application Support, ALL com.adobe.* folders in Preferences, even invisible ~/.adobe
. Then i used Spotlight in Library folder to find any other traces of Adobe related files. Everything must go. Because only thing which i can lose are settings.
And this is what helped. Now is Folio builder working.
I think that today at evening i'll try to find which exact folder/file is responsible for this issue, because we have second computer with same problem. Then i'll sell name of this file/folder to Adobe
. For 355 €.
Good!
This solution (delete everything adobe) is no news to me. I've acustomed to it during 10 years of betatesting InDesign and Creative Suite. We were always warned not to mix the beta installs with production ones, but usually we always did.
NB. If you were on the Lion, you would start with looking for User/Library Folder itself. Apple decided to hide it from our eyes with this version of OS X...
Graham - John explained why this acrobat.com download problem is occurring and how Adobe is trying to fix it. Unfortunately, there isn't a quick fix. Briefly, the team made a fix on the server side that addressed part of the problem. The team also submitted a new version of the Adobe Content Viewer (1.9.1) to Apple with different settings that will put less stress on the acrobat.com server. Until this new version of the viewer is approved and used widely, these download problems will continue to occur intermittently, especially with files larger than 80MB. In addition, the team is working on other ways to make the acrobat.com workflow more stable. Making the acrobat.com workflow more reliable is the team's first priority.
Michelle asked you to send a message to dl-digipub-feedback@adobe.com with your account information so that the team can investigate your download problems. Please do so.
Bob Bringhurst - Adobe wrote:
Graham - John explained why this acrobat.com download problem is occurring and how Adobe is trying to fix it. Unfortunately, there isn't a quick fix.
How quick is quick? This problem has persisted more or less ever since the introduction of Acrobat.com into the worlflow. How long does it take to figure out you have a problem? Why was it and other new/revised features like the Folio Builder were never beta tested?
I have now sent our details to Michelle.
The "authoring" tools really mean the InDesign Digital Publishing plug-in. This is what determines the version of the folios that are authored, which is important as you need to have a viewer app that is compatible with the folio version. I have a chart and legend in this document which can help you:
http://kb2.adobe.com/cps/917/cpsid_91785.html
For the Folio Builder panel, you can logout and look for the build number in the bottom in grey letters. Any of the following are considered valid for the current release of the services:
11.3.3.20110819_m_663171 (initial post of 1.1.4)
11.3.3.20110824_m_663515 (silent update to 1.1.4 day after post, installer would overwrite hot fix version we provided to some customers)
11.3.3.20220825_m_663543 (deliver in 1.5)
Matthew
Matthew, i already mentioned it here, but please, start to name .dmg of your updates in some way, which makes sense. It's hard to find right update in download folder. You should distinguish between versions and of course between version for CS5 and CS5.5. It will make life MUCH easier for us. Thank you.
Have tried installing the latest DPS updates for the authoring tools and the Folio builder for InDesign CS5, (I uninstalled the older versions first) but nothing happened, nothing worked at all, normally would expect to see the tools in the extensions manager window, nothing there and no tools available to use. Have uninstalled everything and reinstalled an older version of the authoring tools and the latest version of the Folio builder. I now have authoring tools which crash the whole thing.
Any ideas?
Bob, this is very funny. There is my request exactly one year old, regarding naming of archives with tools. Do you know what happened? Nothing. I've just downloaded AdobeDigitalPublishingPatch-All.dmg (any idea which version and for which ID it is?). Just another small example, how you simply are not interested how to make your customers life easier.
http://www.adobe.com/support/downloads/detail.jsp?ftpID=5377
North America
Europe, Middle East and Africa
Asia Pacific