31 Replies Latest reply: Jan 27, 2012 2:29 AM by Frans van der Geest RSS

    Timing problem

    blackmountain-agency Community Member

      I have all the latest versions of everything so please don't ask me to update something.

       

      I set an MSO to appear after 1 second.

      On the iPad it appears after 2 seconds.

      On the Galaxy it appears almost immediately.

       

      Thinking about a cache problem, I change the values, create a new folio... same problem.

        • 1. Re: Timing problem
          blackmountain-agency Community Member

          It seems that overlapping timing is not possible in the latest ACV for tablets.

          In the previous ACV Tablets and Desktop I was able to make start various MSOs at different time and the run of slideshow could be overlapped.

          In the latest ACV Desktop it is OK, but not on tablets anymore.

          • 2. Re: Timing problem
            blackmountain-agency Community Member

            I did this

             

            Position 3, Up in the stack: black frame

            Position 2, Middle of the stack: MSO with a static image (dummy MSO)

            Position 1, At the botton of the stack: the video

             

            When played in ACV 2.2.0 and in the current ACV Desktop:

             

            For a split second there is a black screen (1),

            then the video (3) appears. This video lasts 3 seconds

            but at 2.75 seconds I make the MSO (2) start which contains a static image. It fades over the video which is ending.

             

            It works in ACV Desktop and it worked in the previous ACV Tablets but now it does not work anymore in ACV Tablets.

             

            Tomorrow morning I must show the presentation to the client and I can not reproduce anymore what he has validated two weeks ago!

            • 3. Re: Timing problem
              blackmountain-agency Community Member

              This DPS drives me crazy.

              • 4. Re: Timing problem
                BobLevine UGM-MVPs

                Here’s a tip…don’t expect anyone to assume you know what the latest versions are.

                 

                 

                 

                Always state exactly what version you’re using. I can’t count the number of times, I’ve heard, “I’m using the latest version” when they weren’t.

                 

                 

                 

                Bob

                • 5. Re: Timing problem
                  blackmountain-agency Community Member

                  This is not a positive reply. I'm in computer and graphic design over the last 22 years and I know what is an updated software.

                   

                  Is there somebody from the DPS team willing to accept a Connect session with my web cam so I show him what is happening on ACV Desktop and on ACV Tablets?

                  • 6. Re: Timing problem
                    BobLevine UGM-MVPs

                    This is not a positive reply. I'm in computer and graphic design over the last 22 years and I know what is an updated software.

                    Suit yourself...but troubleshooting 101 is to make sure everyone is on the same page. I wish I had a nickel for everytime somesome said they had the latest and greatest and didn't.

                     

                    Bob

                    • 7. Re: Timing problem
                      blackmountain-agency Community Member

                      I made another test on a fresh new file and a fresh new folio.

                       

                      It seems that if I have three MSOs on one page

                      if the first MSO lasts 5 seconds

                      the second MSO lasts 10 seconds

                      the third MSO lasts 20 seconds

                       

                      If I triger the first MSO to start only after 10 seconds, it should then start at the 10th second of the page but no, it seems everything is in the cue and waits its turn. Each MSO needs to pass in a time tunnel and there is no place for overlapping timing so two or three MSOs can not drive at the same time in the same tunnel side by side.

                       

                      My whole project is collapsing here.

                       

                      A colleague told me 30 minutes ago than everything he made with the previous tools is just scrambled in the latest version of the Viewer. But we need interactivity in MSOs to make this project work otherwise the client will kick our tail.

                      • 8. Re: Timing problem
                        blackmountain-agency Community Member

                        It is getting worse. A client sent me an email: he has also noticed that it is not possible to have more than two MSOs and each one stays on state 1. That's what he says and I can believe him, he's also an Adobe Instructor.

                         

                        Adobe, this is really a shame what we are living here...

                         

                        I close everything, fed up, and will show v1 to the client without interactivity in MSOs.

                         

                        Dropping DPS !

                        • 9. Re: Timing problem
                          Bob Bringhurst - Adobe Adobe Employee

                          Unfortunately, some of the changes that enabled embedded overlays caused the timing issues which you've discovered here. The bug has been logged, but it won't be fixed before the v19 release. Sorry about not catching this one.

                          • 10. Re: Timing problem
                            blackmountain-agency Community Member

                            Back from the meeting with the client: he's upset because he can't see what we have promised to him.

                             

                            He asked: "Is this at beta stage this DPS thing?"

                            I said: "No, Adobe screwed the whole thing with the latest update."

                            Client: "Use the previous version"

                            I said: "No interactivity in MSOs. It's like suddenly the new version of Photoshop can't do what previous versions were able to do it but it is hard to use these old versions because we need the features in the new version".

                            Client: "Can we export the Folio as a standalone app and tweak them to make them work"

                            I said: "No, a folio does not use open-source that we can access in its binary and we are not expert in programming. It's not like HTML and JavaScript. Also you don't have the budget. Adobe creates tools only for very rich companies, the ones who can spend at least € 5,000 a year for only 5,000 complimentary downloads and with no guarantee for us, the agency, that we will have enough projects to cover the cost of the DPS contract."

                            Client: "Well, or you find another way to do it, or I choose another service supplier"

                            I said: "There are three possibilites: 1. we wait that Adobe fixes the problem but it will be too late for your project. 2. We make an iPad only version of your interactive publication and we use iBooks Author. This is free, easy and even spectacular. 3. We make hardcoded iOS (and Android) apps. But this is far more expensive."

                            Client: "The presentation must run on iOS and Android"

                            I said: "Let us think about it"

                             

                            Thank you Adobe! It seems nobody in your team has real life files for testing apps before releasing them.

                            • 11. Re: Timing problem
                              ArcInteractive Community Member

                              I am having quite erratic behaviour ( actually non-functional ) MSO animation / slideshows with text.

                               

                              Anyway I'm looking into what the problem is before I call it Adobe's fault.

                               

                              As a general rule from experience, never promise a client something you haven't tested or seen to be working yourself, then you'll never be in this situation. Adobe employs humans, not all seeing robots. There are bound to be errors here and there. It happens everywhere.

                              • 12. Re: Timing problem
                                ArcInteractive Community Member

                                Oh and the 'general' rule applies especially to time sensitive projects ( which is pretty much everything ).

                                • 13. Re: Timing problem
                                  blackmountain-agency Community Member

                                  Please Read Bob reply juste before my January 25 message.

                                  • 14. Re: Timing problem
                                    BobLevine UGM-MVPs

                                    This is more than a timing problem. The whole MSO thing is a mess.

                                     

                                    Bob

                                    • 15. Re: Timing problem
                                      ArcInteractive Community Member

                                      Android works fine. I get the intended results ( with my text fade-in test ) in the Android Viewer. Can't test Playbook as there isn't an update for the viewer.

                                      • 16. Re: Timing problem
                                        BobLevine UGM-MVPs

                                        It’s looking like the bug is in the viewer, then.

                                         

                                         

                                         

                                        Bob

                                        • 17. Re: Timing problem
                                          Graham Davis Community Member

                                          I haven't updated the tools yet but I was sorely tempted as they would have enabled us to do things that we have previously had to compromise on. I am now glad I left it to you guys to feel the pain, sorry but that's the way it is. Adobe's policy of "continuous development" is a sham, in reality we are all still beta testers. As I have suggested many times in the past Adobe should continue to beta test each new version of the tools before releasing them. What Adobe are doing is using us the paying customers as guinea pigs and that is thoroughly unprofessional (please note John Metzger).

                                           

                                          This continues to be the worst experience I have had with an Adobe product despite the fact that it is probably the one I have been most enthusiastic about. When it works it is great but so often it doesn’t. Adobe’s reputation is taking a hammering with ADPS, if there was a viable alternative I would ditch it without hesitation. And watch out because Apple (or someone else) may well come up with a publishing solution that cuts the rug from beneath Adobe’s feet.

                                           

                                            The sad thing is that nearly all of us are fans of Adobe’s products. You should listen to these (and other critical) comments Adobe and change the way you develop this product. It has to work 100% before you release it to us, your customers.

                                          • 18. Re: Timing problem
                                            blackmountain-agency Community Member

                                            Graham Davis wrote: " in reality we are all still beta testers"

                                             

                                            Wel said.

                                             

                                            Will Adobe pay me my lost day yesterday from 4:00 PM to midnight when I have created at least one hundred MSOs, cursing, looking at the coming deadline, and making an unifinished project at 4:00 AM in the morning? I slept 3 hours.

                                             

                                            Yes you can check with my account that I have uploaded dozens and dozens tests in the Folio Producer.

                                            • 19. Re: Timing problem
                                              Bob Bringhurst - Adobe Adobe Employee

                                              In my testing, I noticed erratic behavior if I create multiple MSOs on a page and use the same state names in each MSO. If I change the state names (such as "State 1" to "Red"), the MSOs work as planned. I don't believe this addresses the timing issues, but it may affect some of the other issues reported in this thread.

                                              • 20. Re: Timing problem
                                                Graham Davis Community Member

                                                Bob Bringhurst - Adobe wrote:

                                                 

                                                Unfortunately, some of the changes that enabled embedded overlays caused the timing issues which you've discovered here. The bug has been logged, but it won't be fixed before the v19 release. Sorry about not catching this one.

                                                 

                                                We need some clarity Bob.


                                                 

                                                The announcement of v18 has disappeared. Does that mean it has been withdrawn?


                                                 

                                                  Are you recommending waiting until v19 is released before for we update tools and if so my view is that this should not be until the iPad Content Viewer has been approved by Apple as this has caused a major problem for many users (who admittedly didn’t read the announcement before rushing off and installing the new tools)?

                                                • 21. Re: Timing problem
                                                  Bob Bringhurst - Adobe Adobe Employee

                                                  The v18 tools are still available. That announcement just expired. To get embedded overlays to work, the program team rebuilt the overlays for slideshows and buttons. We expected to see bugs and limitations around nested overlays, but the team wanted to avoid introducing errors in existing areas. Unfortunately, a new slideshow bug prevents an autoplaying slideshow from stopping at the last image. It goes back to the first image on the iPad, This bug ruins fade-ins and other effects that rely on stopping on the last image. Other than using HTML, I'm not aware of a workaround.

                                                   

                                                  While we can post hot fixes for the web client and Folio Builder panel, we can't easily post a new set of Folio Producer tools. This bug and others should be fixed in v19 (February), but that's several weeks away. If your design relies on stopping slideshows on the last image and you can't find a workaround, you should roll back to the v17 tools.

                                                  • 22. Re: Timing problem
                                                    Graham Davis Community Member

                                                    Sorry Bob but that is simply disingenuous. You should post a new announcement explaining the problem with v18 rather than quietly withdrawing the original post. People will go own downloading the new tools without realizing that they have bugs and that there is no iPad Content Viewer. That is irresponsible!

                                                    • 23. Re: Timing problem
                                                      BobLevine UGM-MVPs

                                                      Graham, when announcements are posted they have expiration dates in them so they don’t sit forever.

                                                       

                                                       

                                                       

                                                      It just came off automatically. It’s not a conspiracy theory.

                                                       

                                                       

                                                       

                                                      Bob, are you saying this problem is in the tools? I thought it was the viewer.

                                                       

                                                       

                                                       

                                                      Bob

                                                      • 24. Re: Timing problem
                                                        Bob Bringhurst - Adobe Adobe Employee

                                                        I was under the impression that a fix needs to be made to both the tools and the viewer, but it might be just the viewer. I'll check.

                                                        • 25. Re: Timing problem
                                                          BobLevine UGM-MVPs

                                                          Thanks…if it’s just the tools I’ll roll back.

                                                           

                                                           

                                                           

                                                          Bob

                                                          • 26. Re: Timing problem
                                                            ArcInteractive Community Member

                                                            Thanks, please let us know.

                                                             

                                                            Perhaps an announcement or sticky about the MSO bug might be a good idea.

                                                             

                                                            I think I'll stick to v18 anyway, considered rolling back to v17 but I'd lose PDF Pinch & Zoom ( which incidentally reduced my folio size by almost half ). The text crispness is also of course far better than the bitmap alternative!

                                                            • 27. Re: Timing problem
                                                              Bob Bringhurst - Adobe Adobe Employee

                                                              Bob, if you roll back to the v17 tools, the "stop at last image" problem will go away. The v17 tools should work fine with the v18 viewers.

                                                               

                                                              The actual bug is in the iPad viewer. This bug should be fixed when the next viewer is released (currently scheduled for February).

                                                               

                                                              Again, sorry for the inconvenience.

                                                              • 28. Re: Timing problem
                                                                BobLevine UGM-MVPs

                                                                I think I’ll just deal with it for now.

                                                                 

                                                                 

                                                                 

                                                                Bob

                                                                • 29. Re: Timing problem
                                                                  Frans van der Geest ACP

                                                                  I have a folio in my library build with v1.7 that has a MSO and stops at last frame (fade in effect) that works and displays FINE on my iPad with viewer 2.3.

                                                                  But newly build folios with 1.8 do not work fine.

                                                                  So how come you think its a viewer problem? Looks like a builder problem (again! I mean: again!) to me!

                                                                  Are we clients now considered your beta-testers...?

                                                                  • 30. Re: Timing problem
                                                                    Bob Bringhurst - Adobe Adobe Employee

                                                                    It may appear to be a tools problem, but it's a viewer problem. The MSO code in the v18 Folio Producer tools changed. The new AIR viewers handle it properly while the iPad viewer does not. The new viewers handle the previous MSO code just fine, as you've seen.

                                                                    • 31. Re: Timing problem
                                                                      Frans van der Geest ACP

                                                                      Oke, I see. The new builder displays 'old code' but can not display 'new' code, but Desktop Preview is oke. Well, that will go down well coming monday during my training session for a big company here in the Netherlands...