My experience using stills with FCP7 is far worse than with Pr. Crash City. Very painful. Esp. with JPEGs.
I've seen issues with stills that are very large, scaled down in a sequence. From what you describe, it sounds like the stills are being loaded into RAM, leaving nothing for other operations. If this is so, you could try scaling down your images, perhaps by automating the process in Photoshop.
I don't know if it's normal to load images in the project (and not in a sequence) into RAM. That doesn't seem right. Another cause for the beachball could be corrupt source images. You could determine this by adding a few stills at a time, and waiting for the axe to fall.
I never used Pr 5.0.x, other than playing around. I didn't think it was ready for professional use until 5.5, so my experience. Maybe somebody else with experience on that version has more helpful info.
I have done a couple of "slide show" style projects in Pr, and other than suffering the occasional corrupt image, it's been pretty painless, and far better than my experience trying the same thing in FCP.
If you are using 'Icon View' in your project's bins, all of those thumbnail
images are generated on opening the project and are stored into RAM.
>2000 images into a Premiere project on a Mac Pro, Premiere CS 5.0.0
1-read these links
Photo Scaling for Video http://forums.adobe.com/thread/450798
-Too Large May = Crash http://forums.adobe.com/thread/879967
-And another crash report http://forums.adobe.com/thread/973935
2-PPro for Mac is now at version 5.0.4 which includes MANY fixes and improvments
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
Wasn't in icon view
Already installed the 5.0.4 update as I said above, thanks for the links but they don't really apply as I'd not placed any of the stills in the timeline yet, just video.
Yeah, it has felt horrible having to go over to FCP for first time in years, but it's stayed stable. I use 5.5 myself, but I'm in-house on another machine so not got much choice. I agree it is strange and would make sense if I had 2000 images in the timeline I could see how it'd be a strain, but not just sitting in their project folders. It'd have taken too long with all the different sources and formats to resize all the images, even with automating as they were a a bit of a mess, though I had weeded out corrupt files and the odd CMYK JPEG which just wouldn't import already. I guess I'll know for next time, but I had to rattle out a fast blocked out edit so was faster to jump over to FCP than trawl through the source files.
After applying the 5.0.4 update, try creating a new project and then importing the old project into it. Does the problem happen then?
Thanks Todd, I'll try this in the morning.