PPro2 sucking up memory then crashing

[Pat Mcgowan]

We went with Adobe because of the promise of a truly integrated toolset that could allow us to service broadcast HD and SD, corporate and web-based assignments.

So far it has been extremely frustrating and unpredictable. It’s kinda like driving a car with 3 wheels. If you balance the load you can actually get somewhere but you’ll never get up to full speed and every once in a while the whole thing tips over and grinds to a halt and you have to spend a bunch of time figuring out how to get the blasted thing rolling again.

Adobe seems to be content, sagely watching us squirm and moan, confident that there is no other viable alternative on Wintel boxes. All I can say is that we, like many others, will wait to see if PPro 3.0 is, in fact, a professional product that allows us to work at full speed with minimal gyrations. If it’s not, we’re gone to Avid or FCP.

[Lance Bauerfeind]

You and me both

One Good Eye is all you need!

[Tclark]

You will have problems no matter what you go with. Don’t think just because you switch all your problems will go away. I work on both FCP and PPro and FCP has more problems!! So much has to do with hardware configurations. Once you have those problems worked out you will have a better editing experience.

[Pat Mcgowan]

Yes, there are problems with NLEs in general. However, there were never the types and severity of problems with Media 100, Discreet Edit* and Avid as there are with PPro and FCP.

What if these softwares were used to run banking systems, nuclear plants, air traffic control, or 911 systems? Imagine the outcry.

[Tclark]

Then you would be spending a hell of a lot more money and then I gurentee it would be a whole different situation

[Pat Mcgowan]

Ah yes, the old “you get what you pay for” argument. Why then does Adobe not advertise it’s PPro offering as “Cheap software that may not be reliable, but it’s cheap!”?

Obviously they don’t, they advertise it as a professional toolset that works.

I own power tools that are not high priced and top of the line, I also own a car that is not high riced and top of the line. I can drive screws and go to the mall with little difficulty with those products.

[Tclark]

” What if these softwares were used to run banking systems, nuclear plants, air traffic control, or 911 systems? Imagine the outcry. ”

Sounds a little extreme!

You get what you pay for does not really apply here.

[Pat Mcgowan]

So you’re saying that having a bunch of agency clients breathing down your neck is not “mission critical” and it’s OK for the software to freeze, kick you out or simply not load the project?

Give me a break.

[Tclark]

Give me a break! “Air Traffic Control” Yea, that’s the same!

[Timothy Eaton]

We are longtime users of Adobe products on the Wintel side and have generally been very supportive of Premiere. It is a marvelous product for relatively small projects. As for Apple, competition is great when it improves products, but I haven’t been much of an Apple fan over the years because I think they’ve done all they could to inflame an unhelpful (from the end user’s viewpoint) war of words over the platforms, and I’m sure FCP has its own problems. That being said, I think Pat, Marisu and others (on an earlier thread) make an important point. They are only asking Production Studio to operate in the real world of post production. It’s not unreasonable to digitize 30 or 40 hours of footage for a documentary, import a few hundred stills and then expect Premiere to operate as advertised, with dynamic link, multiple sequences, nested sequences (when useful), and the ability to import projects from another workstation and access sequences from them. Those features are all in the Adobe literature. We are working on two such documentaries with very tight deadlines and have hit the same wall as others. We’ve tried to manage our assets reasonably well, and are now deleting sequences and avoiding any use of the offending features while keeping an eye on Task Manager (thanks for the tip), but we’re still in a jam. At some point, when you are unable to use the features that would otherwise make Production Studio great, or even manage the basics without crashing, you begin to think about other solutions. I’m afraid we’re in agreement with Pat. If 3.0 doesn’t address these issues and soon (how about NAB?), then we’re looking for another vendor. Furthermore, I don’t give a rat’s “a” about Premiere on the Mac. I need Production Studio to work well on the Wintel boxes it was designed and marketed for.