Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Timeline takes ages to respond

  • Bruce N. goren

    March 18, 2010 at 11:45 pm

    Since you are not using effects transitions, delete all your render files, you have enough horsepower to preview on the fly.

    I had this problem too, it started after the most recent point update.

    As my project grew very large I was getting windows delayed write failed errors. Deleting my render files worked for a while, then I had to take more drastic action.

    So if deleting the render files does not bring you relief, try a web search for and download cacheset.exe . In working set maximum, I use a value of 655360 before starting up CS4.

    https://technet.microsoft.com/en-us/sysinternals/bb897561.aspx

    I don’t remember where on the web I first found this temp fix but it seems to work for me.

    Good luck . . .

    Bruce N. Goren
    “If you don’t have time to do it right, when will you have time to do it over?”
    John Wooden, Basketball Coach

  • Kaye Abbott

    March 19, 2010 at 9:48 am

    Interesting. Deleting my render files didn’t help, so I downloaded that utility. My working set maximum is, by default, considerably larger than the number you used, though. Does your fix involve increasing or decreasing it?

  • Bruce N. goren

    March 19, 2010 at 4:31 pm

    Wow, my working set maximum was defaulting to only 24, and upping it to 640 was tripling what the web posting I read recommended.

    What I did to arrive at 640 was trial and error, I suggest you increase the number, try to edit, if fail, re-boot, increase the number, repeat. Remember to multiply by 1024. In example: 640 is 655360, 768 is 786432 .

    Can your system accommodate more RAM? Buy a ton more memory and I’ll bet all will work smoothly.

    I only have 3 GB of RAM, and am running Windows XP on an aging dual Xeon with a 500GB G-Raid. I also turned off indexing on my system drive as another posting on the web noted it was a resource hog.

    Recent point updates seem to have made CS4 a bit fragile, I’ve also seen suggestions that you roll back to a previous version if possible, never tried that myself. Good luck!

    I’m guessing Adobe will tell us it will all be better when we switch to 64bit Win7 and CS5 running only on their officially blessed hardware configurations.

    Bruce N. Goren
    “If you don’t have time to do it right, when will you have time to do it over?”
    John Wooden, Basketball Coach

Page 2 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy