-
PP 2.0 Not Ready for Large Number of Source Clips? Hardware or Software Issue?
Is it me????????
It’s typical in many of our jobs to have 1000’s of source clips especially working on programs that are two hours long. While PP 2.0 doesn’t crash like 1.5, there are still problems as you work with page memory. We get the message that expresses you are dangerously close to a crash, so you better save your project, close down PP2.0, and reopen. This can take up to 10 minutes. Now doing this once a week wouldn’t be an issue but two or three times a day?
There are other situations that causes a temporary freeze on the machine as it catches up to where you are.
For reference we have 2gigs worth of memory on a dual 3.6 xeon dell 670. We take in dv material via firewire and have no add-in cards like axio or bluefish. All the material is on one 7200 rpm drive.
Is anyone else having problems with large number of clips?
-
18 Replies
-
It’s not you! I’m working on a project with over 5,000 shots in the bins. Starting the project in PPro1.5, was a nightmare, and before 2.0 was released I was afraid I was going to have to break it up into any number of separate projects. But with PP2, I don’t believe that will be necessary. On the other hand, I’m only about 20 minutes into the timeline.
A couple of things. You definitely need more memory, at least 3gb, probably 4. And you need to enable the PAE (3gb) switch (see http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx).
I’m currently running 3gb of memory and am about to add 1 more.
I was very disappointed that PPro2 was not a 64-bit app. Even though it did correct some of 1.5’s notoriously awful memory issues, there are still some, as you mentioned, that will give us long-form folks the blues. Good Luck.
Bill Buchanan
Buchanan Film Co. -
Hi Guys…
no an solution, but a work around…
could you keep the sources in smaller project sets and somehow use Adobe Bridge to access stuff as needed?
Alex
-
Bill,
Thanks for the info. Come Monday, I will explore.
-
Alex,
I’m not familar enough with Bridge’s capabliities to know if this would work or not.
thanks,
Richard
-
The 3GB switch is fine but you will still get problems with RAM. The extra GB will do nothing for Premiere, in fact it may make things worse.
I am running an Axio with 2 and can see the same problems, what appears to be a lockup which then comes back and large project files (mine is currently 43MB) and they take about 5minutes to open. However they are more stable than they were with 1.5 and like Bill, I can now work on projects that I couldn’t do under 1.5 (I had to split them up).
However despite the amount of RAM Premiere gets, there is an underlying problem with another aspect of memory allocation that is causing the crash warning message. I can not discuss this issue here but I would recommend lobbying Adobe at NAB.
Paul
-
Hey Paul:
I can’t tell you how delighted I am to know that “there is an underlying problem with another aspect of memory allocation that is causing the crash warning message…”
The last time I heard something that encouraging came from an Adobe support guy I talked with about a year ago. I was going through hell trying to get 1.5 to work with a large project and called tech support.
With the chest-beating confidence only a guy emboldened by the appearance of his first pubic hair could have, he instructed me that “Premiere wasn’t really designed for large projects like mine” or something to that effect. I wanted to ask him why that information wasn’t included in Premiere’s marketing hype, but I could no longer stand the sound of his little voice.
Since you are apparently an insider and/or beta tester with Adobe–and I can’t attend NAB, all of us working in long-form would appreciate your getting in someone’s face and making it clear that there’s quite a few us that no longer enjoy standing around braying like donkeys while our projects reload or whatever they do when the GUI goes white.
Please know I’m not going off on you, as I appreciate your candor about this memory thing. I’m sure you can appreciate the frustration this issue has caused for so long.
Bill Buchanan
Buchanan Film Co. -
Bill
I’m using the /3G switch with 4 Gig, do you know if the PAE switch works with Opterons? Or is it only an Intel thing.
The error I get with Premiere and large jobs is something about the system getting low on resources and to save. I’ll have to write it down and call Adobe next time to find out what it means.
Shane
-
Shane:
I don’t know if it’s just an Intel thing. Also, I’ve never gotten the message about “low resources.” You should pull up the MS web page(s) that discuss the 3gb switch to see if it applies to Opterons.
Bill
-
The 3GB switch is an OS issue, unrelated to Intel vs. AMD.
(BTW, Intel CPUs nowadays are AMD-compatible, meaning Intel had to add AMD’s added instructions, after Microsoft and several other major vendors told them they wouldn’t accept an incompatible Intel alternative).
For the deeper scoop on the 3GB switch, see Tam Tam on The oft-misunderstood 3GB switch.
The user has to enable the switch, and the application has to request the additional memory. Even then the memory the application receives may not be contiguous.
I’m also longing for the next step beyond the [in]famous “Why would anybody ever want more than 640K?XXXX64MB?XXXX256MB?XXXX2GB?”
-
Hi Bill
How much did you pay for Adobe tech support? Here in Australia I think we pay $3.00 a minute to have someone read the manual back to us. I suppose this teaches peaople to read the manual (not that it helps with these issues).
Have a look at RAM usage when you get the low system resources message, I’ll bet it’s hovering just under 2GB despite the 3GB switch.
As you said things are a lot better since v2. Does anyone know what other NLE apps are like with large projects?
Paul
Reply to this Discussion! Login or Sign Up