I recently upgraded my RAM from 4gb to 8gb using Kingston RAM. I looked at my activity monitor and premiere will only use like 3gb of memory and it will freeze up and get the beachball. I set in the preferences an allowance of 6.5 gb. I don't know if I just got bad RAM or what. My roommate has 8gb of RAM in his Mac and Premiere and after effecs runs smoothly
99% of the cases this is OE, Operator error, due to:
Hard to tell without details, but OE is the most likely cause.
The Version of Premiere I have is 5.0.0. It's the student edition, I got it in 2010.
Operating system Mac OS X v10.6.8
H.264 1920 x 1080
I'm not getting any error messages, just a ton of beachballs when I try and do simple tasks like drag a clip from one part of the timeline to the another place in the timeline.
I don't remember getting this many beachballs when I had the factory RAM in my macbook which was only 4 gb. I set the preferences to 6.5 gb of RAM allowance with the 8gbs of RAM but I look at the activity monitor and only 3-4 gb of RAM is being used except when I render and I get a ton of spinning beachballs.
I am running Safari and Spotify along with premiere
I have Magic Bullet Looks which runs fine
Processor Speed 2.66ghz
First, install the updates and then try again
All Adobe updates start here and select product, read to see if you need to install updates in number order, or if the updates are cumulative for the individual product http://www.adobe.com/downloads/updates/
Does your sequence match your video?
For CS5 and later, the easy way to insure that your video and your project match
See 2nd post for picture of NEW ITEM process http://forums.adobe.com/thread/872666
-and a FAQ on sequence setting http://forums.adobe.com/message/3804341
I looked at the articles and my sequence matches the clips. Everything is updated.
I always get the spinning beach ball when I select all of my clips in the sequence and shift them to the left or right, and instead of the clips all moving in the direction I want them to. I get the spinning beach ball, and it never stops until I force quit