Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Start Up Delay

  • Start Up Delay

    Posted by Daniel Schloss on October 4, 2005 at 6:23 am

    Been searching and other have this problem, just wondering if any has found a solution. My 1 hr 15 min project takes 25+ minutes to load. If I minimize or fire up anything else the program goes to a white screen and rebuilds slowly. I have 2 Gigs RAM and using SATA drives with P4. Never had this problem before. Now all projects delay as they get longer. Any thoughts?

    Dan Schloss
    in**@*******ia.org

    Redgum replied 20 years, 7 months ago 3 Members · 6 Replies
  • 6 Replies
  • Aanarav Sareen

    October 4, 2005 at 7:07 am

    25 minutes is extra-ordinarily long. Do you have a lot of background processes running on your system?

    Aanarav Sareen
    Adobe Certfied Expert, Premiere Pro

    https://www.asvideoproductions.com/video

  • Redgum

    October 4, 2005 at 9:22 am

    Defrag your video drive regularly. Prem Pro will always slow down as its project size increases but not usually to that extent. I currently have a one hour hdv program on the timeline with plenty of overlays etc and about 400 clips. It takes about three minutes to load. I defrag after every edit session. Also make sure your scratch disks are set up properly.

    Redgum Television Productions
    Broadcast & Corporate Documentaries
    Brisbane, Australia

  • Daniel Schloss

    October 4, 2005 at 2:37 pm

    No I’ve shut down everything. I am now at a 30 minute load mark. I know this is strange and not normal. I use 2 removable SATA drives and have tried switching them. No luck. I noted this started after my reinstallment of Windows XP. All drivers are in and I defrag constantly. Nothing helps. Eveything else loads and runs fine, it’s just when I fire up this project.

  • Redgum

    October 5, 2005 at 6:06 am

    You best explain your setup. Are your Sata’s in caddy’s or USB/Firewire? Why and how are you swapping the SATA drives? Are they identical in setup? FAT/NTFS? What’s your O/S. Explain your “scratch disk” setup?

    Redgum Television Productions
    Broadcast & Corporate Documentaries
    Brisbane, Australia

  • Daniel Schloss

    October 5, 2005 at 3:33 pm

    Satas are in removeable bays so I suspect they are not USB or Firewire. Scratch disks are set up with Adobe on C, the project data name on C in a root folder. Four directories are on the video drive (one of the two satas) as a videocapture, video audio, videopreview, audio preview and audio conform. All are NTFS. Running XP Pro, current drivers for satas, Adobe. Running SP1, Capture card is Matrox RT100 extreme.

    This just started when the windows was installed. Prior to that and currently with small projects, all runs fine. It’s when I get a large project. The current one has old video clips taken from VHS and DVD via the Matrox. As soon as I do anything, open a window etc the C drive starts massive reading for 30 minutes then the project frees up and the time line srubs and all is ok. My CPU use skyrockets to 80+% while all this crap is going on. And rendering has a slight delay about every 20%. Seems like the CPU is being over taxed on. At a certain point while moving clips, rendering, laying in transition, etc the system freezes or Adobe just disappears. But it is the the system accessing the SATAs that causes the 40+ min delays when starting up. Thats the show, hope someone has ideas. Going back to Commadore 64’s soon!

  • Redgum

    October 6, 2005 at 6:19 am

    No doubt this exercise is giving you a pain in the butt. Often the best way to sort out these sort of problems comes down to elimination. I suspect there could be one of two problems. Sata drives in caddy’s are not common (they should work) but I’ve seen some funny stepdowns and configurations. To eliminate the Sata problem try connecting one of your Sata drives directly to the Sata bus (in other words, eliminate the caddy connection).
    The second suspect is the Matrox card. Capture cards add another element to the edit suite. They need a “driver” between the card and the system and when you introduce new elements like SP2, Sata Caddy’s etc., the “driver” may need changing. Search the Matrox site for more info on this.
    But first, try the Sata drive connection, this may well be the bottleneck.

    Redgum Television Productions
    Broadcast & Corporate Documentaries
    Brisbane, Australia

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