-
VERY SLUGGISH Pro 1.5 whenever timelines about 1 hr or longer
Projects with longer timelines (1+ hr) get progressively — and noticeably — more sluggish in Pro 1.5 as the timeline grows…
Not really noticeable in short pieces (< 15 min), but it started being apparent when the timeline grew to about 45 min. I began noticing that operations like Extract (from IN to OUT point, on all tracks) was taking some 7 seconds -- something I had never seen in Premiere Pro 1.0, even with much-bigger projects. To further amplify this effect, I created a timeline about 3 hours in length (simply by repeatedly cutting-and-pasting a short edit over the timeline.) It simply uses two DV .avi files. It's a project I first created in Premiere Pro 1.0. When I open it in Pro 1.0, the extraction happens in about 1 sec. But when I open it in Pro 1.5, it takes about a whopping 2 MINUTES!!!!! If I open it in Pro 2.0, it takes about 2-3 seconds. What happens during those 2 minutes? Well, the CPU spins at 100%! Most bizarre... It's NOT an issue with memory. From the operating system task manager, it appears that the total memory used ("Total Commit Charge") is no more than about 700 MB, and I have 1 GB of memory. In Pro 1.5, if the timeline is long enough (say, > 30 min), even SELECTING everything on it (CONTROL-A) is a lengthy operation! It just gets BOGGED DOWN when the length of footage grows.
Anyone had this problem?? Thanks very much 🙂
-
4 Replies
-
You need to dump V1.5 and get V2. Most if not all the issues you’re dealing with have been addressed and fixed.
I’m currently working a complex 90 minute timeline with about 5,000 clips in the bins with no slowdowns or interface white-outs or crashes…knock on wood.Bill Buchanan
Buchanan Film Co. -
I agree, ug to V2!!!
I did an hour & half with PPROV2 on a 2.2Ghz with 1Gb ram, and it worked pretty good, and I was using a large number of 2560×1920 stills in the project. I was concerned about the ability to do such a large project considering what I’d heard about V1.5, but V2 really worked good!(I encountered an slowdown issue with a plugin, Steadymove Pro, but that has since been fixed!)
Looking for 1939 Indian Motocycle
-
I have found this in P 1.5 as well as 2. This happen from time to time but I don’t think is due to project lenght. Could be by the filters and the slow motions, etc.
Sometimes I make a cold reboot and problem goes. Other times remain.
But this in only in the playback. Nothing to do with final product. -
I upgraded to Pro 2. Initially, the problem disappeared, but it came back with a vengence as the project grew.
It’s NOT a playback issue. It’s a simple “Extract” from the timeline operation: set IN point, set OUT point, Extract!
It’s now taking (in Pro 2) a mind-numbing 22 seconds to do that miserable little operation!! Even the “un-do” for that operation takes a comparable amount of time. During that time, the CPU is going crazy spinning around at 100%
Reply to this Discussion! Login or Sign Up