Premiere 1.5 Annoyance

[wwaag]

Does anyone else experience this? After I open a project, the first time I click on the File tab, nothing happens for about 15 seconds. It just freezes. Afterward, it eventually becomes highlighted and everything works OK. I have Premiere installed on 2 separate XP installations and it does the same on both. While not a showstopper, it is truly annoying. Any help would be appreciated.

Thanks.

wwaag

[WhoisGeorgeBush]

Its OK you proberely just need upgrade you computers RAM

[edDV]

Yup. Probably dumping RAM to page files.

[wwaag]

Thanks, but I kinda doubt it. First, I've got 1GB of RAM. And second, 15 secs to dump ram, seems a bit much. I've posted this problem on the Premiere PRO forum and I've got no solutions there as well. I'm suspecting that its a hardware issue. Again, after I open a project, I can do whatever until I click on the File tab. It highlights and then "freezes" for 15 sec. After this initial 15 sec freeze, it's OK with no problems until I open another project file. Then the same thing. Again, thanks.

wwag

[edDV]

Maybe autosave is triggered? Who knows.

These complex programs have so many modes, you almost have to talk to an Adobe software designer to answer this one.

[WhoisGeorgeBush]

This really seems like a problem within either the software or the hardware because the only paramaters you are mentioning lie within the processing of your command. Check the usual things like space, you are right you RAM speed is up to date, but check the software try reinstalling it, the problem is directly related to either the software you are using or the hardware.

[wwaag]

Problem solved (I think).

Just finished archiving a major project that I'd completed. After saving all of the assets to a backup hard drive, I decided to clean-up my "video" drives by "reformating" and starting over fresh since I'm beginning a new project.

Premiere now works great without that annoying 15 sec delay I discussed. Don't know if it was erasing all the temp files that had been created or de-fragging the HD that did the trick, but the problem appears to be solved. (I'm keeping my fingers crossed.). Again thanks for the suggestions.

wwaag