Currently Being ModeratedOct 30, 2011 4:32 PM (in response to macjabber)
I've been following the post for some weeks given my own difficulties with Lion and Keynote (embedded videos and files of 8 Gigs or so) with the program invariably freezing even when I try to save a small text change. In reality for a "surface" user like myself with neither the talent nor time for system adjustments I have no choice but to revert to PowerPoint, which is a bit sad for a user committed to Macs for 22 years. I hope a fix can be found, but until then I don't feel there's any other option.
Currently Being ModeratedOct 30, 2011 5:13 PM (in response to walkinginthecity)
Sorry to say that anyone running a Keynote of 8GB likely on a MacBook maxing out with that much RAM or less is asking for trouble no matter what OS/Keynote version combo you're running.
Oh, you're heading back to PowerPoint. Yep, that'd be asking for trouble. ;-)
Currently Being ModeratedOct 31, 2011 5:29 PM (in response to William C.)
You have indicated that "Keynote is where the problem is..." Would be helpful if you could provide the steps you have taken to reproduce the issues that point to Keynote as the problem. Would like to see if I can reproduce this. You use the medical analogy to say that the knee aches but the problem is in the spine. So Keynote is the spine according to you. Love to see the evidence so we can get back to work.
Currently Being ModeratedOct 31, 2011 5:33 PM (in response to macjabber)
BTW since QT plugins have been taken care of had completely no issues with Keynote on Lion. It was hanging prior. Also two developers applied this to their machines and they have had no reoccuring issues. Seeing absolutely no memory leaks with devloper tools. For those who are **** bent on makeing Keynote the issue keep up the debate.
Currently Being ModeratedOct 31, 2011 5:54 PM (in response to macjabber)
In my medical analogy, Keynote was the aching knee, Lion was the bulging disk causing the aching knee.
I don't believe Keynote is the problem. I think the problem is Lion's Autosave/Versionsfeature. The problem manifests itself in Keynote docs with embedded videos. What have I done to verify this? I ran a dozen or so Keynote files, both existing ones and newly created ones, with and without embedded videos. Keynote 5.1 presents the spinning beachball of death with even trivial changes to the document. Keynote 5.0.5 does not. There are no such problems with small Keynote docs with no videos. I've tried all sorts of video formats. As I understand it, Autosave/Versions is an OS feature not a Keynote feature. So the problem appears to be with OS 10.7 and manifests itself in Keynote docs with embedded video.
I've been happily producing content and presenting with Keynote 5.0.5. In fact, I've downgraded all my computers to iWork 9.0.5 to avoid the Autosave/Versions feature altogether. It's a much happier world without it.
Are you saying that the problem has been solved with 10.7.2? Are the QT plugins part of OS 10.7.2? I've been hesitant to update back to iWork 9.1 since I lost a bunch of valuable time and was waiting to see some confirmation that this problem was solved. There really isn't much to debate here. Either Keynote 5.1 runs properly on OS 10.7.2 or it doesn't.
Currently Being ModeratedOct 31, 2011 7:22 PM (in response to William C.)
I was able to recreate what you have been seeing with Keynote and I did manage to get the patience wheel. I recreated the condition in 10.7.1 and 10.7.2. What codecs and versions do you have in your /Library/Quicktime directory? Also would you take one of your decks and run it (one that hangs) and also run Activity Monitor see what are the process that are taking up the most CPU memory. Like to know what you are seeing.
Currently Being ModeratedOct 31, 2011 10:55 PM (in response to macjabber)
I'll run the Activity Monitor tomorrow on a computer that has iWork 9.1. All my computers are iWork 9.0.5 at the moment.
Here is the QT information:
file://localhost/Library/QuickTime/AppleIntermediateCodec.component/ (version 2.0)
file://localhost/Library/QuickTime/AppleMPEG2Codec.component/ (version 1.0.2)
Currently Being ModeratedNov 1, 2011 2:22 PM (in response to macjabber)
Here is a screen shot of Activity Monitor while Keynote is hung. I hung it quite easily with a deck containing 8 embedded short videos, total doc size is 922 MB. I'm running OS 10.7.2 and Keynote 9.1. It has now been hung for over ten minutes. At the time Keynote hung, no other applications were running.
Currently Being ModeratedNov 1, 2011 2:45 PM (in response to macjabber)
I was also able to hang Keynote 9.1 on OS 10.7.2 by running one of the embedded videos in Play mode. Since I couldn't get out of Play mode during the event, I'm not able to show the Activity Monitor. While the event lasted only 30 seconds or so, it would have been catastrophic in an actual presentation. I'm guessing that only locked files should be played for presentation. This emphasizes why Autosave/Versions needs to be a toggled feature in OS and why I will continue to use Keynote 9.0.5 or PowerPoint. Fortunately, my pre-Intel road laptop runs Keynote 9.0.5 on OS 10.5.8 with no problems whatsoever.
Currently Being ModeratedNov 2, 2011 6:07 AM (in response to fuzzydog)
I read through this whole thread to look for solutions. I, too, have a larg (600M) presentation with videos that stutters and crawls. I tried most of the things in this thread and then found the one that worked. Hopefully my experience will assist others.
1) I tried unchecking the "Back up previous version" checkbox in Keynote Preferences. While some people reported that this worked for them, it made no difference for me.
2) I tried unchecking the "Lock documents 2 weeks after last edit" item in Time Machine Options. This also did not work for me.
3) I tried duplicating the file and then opening it in Keynote. This would seem to work at first, then deteriorate. Why? My thought is that when you duplicate a file you get rid of it's "version history" that Lion and Keynote are using instead of save, but once you start actually going through the presentation it starts a new version history and has problems again. In theory if you don't change anything in the presentation it shoudn't happen, but this only helps if your goal is just presentation. I need Keynote to work so I can edit, too.
4) Finally, I followed fuzzydog's instructions on how to uninstall Keynote 9.1 and reinstall it from my iWork 9 DVD, then upgrade to 9.05. THIS WORKED. I did NOT need to go back to Snow Leopard.
The older version of Keynote doesn't use Versions and once Versions is disabled the problem went away. Thank goodness I actually had the DVD. I'm repeating fuzzydog's instructions below, with a couple of additions in places where I had trouble:
1. Find your iWork 9 DVD.
2. Remove iWork 9.1 using the script supplied by Yvan Koenig. Just deleting iWork is NOT enough - you need to clean up all the iWork files or this won't work. The script is here:
Look in the folder called "For_iWork", then "iWork '09" and then download the file called "uninstall iWork '09.zip". When that has downloaded and opened, click RUN. Wait several minutes while it gets rid of iWork.
The script does not remove your personal templates stored in your user/library/application support/iworks folder.
2. Reinstall iWork from your disk.
3. Next you'll want to update iWork to version 5.05. You can get this here. http://support.apple.com/downloads/#iwork.
There are FOUR update packages: 9.0.1, 9.0.3, 9.0.4 and 9.0.5. Download and install them in order. Yes, I know these are version 9.0.1 and we're upgrading to 5.05 - who knows what's with that.
4. The first time you open any iWork app it will ask you to upgrade to 9.1. Do not do this and check the box indicating not to be reminded again.
If it did not work, check the version number on Keynote (go to Keynote > About Keynote). If it says version 5.1 then you didn't properly uninstall the old iWork. If it says version 5.0.5, then it should be working. If it's not, then this fix didn't work for you (though I don't know of anyone, yet, for whom this is true).
Finally, Apple does NOT read these discussion groups. If you have downgraded your version, then let Apple know by visiting the Keynote feedback page and providing information here:
Currently Being ModeratedNov 2, 2011 7:58 AM (in response to therivers)
Thanks for renewing the summary of the one solution that works across the board. In a long thread like this, it's helpful for folks searching for a solution.
I would add one more step.
5. Be sure that your Software Update does not download automatically or you will be back to iWork 9.1 before you can say "spinning beach ball of doom." You need to manually uncheck the iWork update every time Software Update runs. It's happened to me twice. I keep a folder with all the downgrade stuff handy just in case.
At this stage of the game, I'm content with iWork 9.0.5 and don't intend to upgrade until I see an all-clear. I can't afford the time troubleshooting essential productivity software.
many many ppl have this problem. i have been dealing with it for months. latest updates resloved none of it. still get spinning wheel EVERY SINGE TIME i make even one change. Each time I have to wait 3-5 minutes for the wheel to stop spinning to make next change and then have to deal with it again and again. This is insanely frustrating. Supposedly Apple knows of the problem and has yet to fix it with any updates. Having to downgrade seems insanely wrong.
Currently Being ModeratedNov 3, 2011 4:44 PM (in response to mtevans126)
And to add insult to dysfunctional injury, Software Update begifted me with iWork 9.1 this morning, in spite of my deselecting said option before hitting Install. Not being a conspiratorial type, I will conclude that a slight twitch on the relatively new touchpad caused me to select it again without noticing. I would not want to conclude that Apple is insisting I upgrade iWork in order to force me to use the useless Autosave/Versions feature. And so for the third time, I must do the downgrade shuffle.
Just to make the point, I was intentionally hanging the one machine I have that runs iWork 9.1 so that I could generate multiple crash reports to Apple. It's kind of a fun thing to do on a coffee break.