-
Memory and Error messages
-
Yes, I know, what would be the size of the 2nd harddrive?
-
South Video, your problems most probably (if not certainly) have nothing much to do with your hardware. The suggestions being proffered you will increase performance but most likely will not solve your memory errors. PPro is not yet an appropriate NLE for larger projects. It eats memory and doesn’t give it all back. Eventually as project size increases, it reaches a critical mass, and frequent crashes follow.
Please do yourself a favour and do a search on memory problems in this forum. You’ll find lots of threads. Many people have experienced this problem. Many have not but in all liklihood they’re just not running the large or complicated projects that cause PPro to reach the necessary critical mass.
About the only solution to this problem is to break you project up into smaller projects if you can.
David
AllinOneFilms.com -
Thank you for the input!!!
-
David, I’m not sure I completely agree with that statement about memory. I have been working on a two hours 1080i (not HDV) project without any major issues. The timeline isn’t as snappy as DV of course, but it’s definitely not giving me errors or constant freezing. A large amount of uncompressed footage will however take my system down, no doubt about it.
The problem here, is that most of the threads don’t mention memory speed, buffer, bus speed etc., so comparisons can’t really be made. Bad memory sticks aren’t uncommon either. Premiere definitely needs some work in the memory area, but I’m no advanced programmer, so I’m afraid I can’t criticize Premiere for the way handles files; but I wouldn’t give up quite yet on those issues. People also often mix different types of RAM, throwing of the timing, and that can be a no no for demanding apps.
Again Mark, let us know what the errors are when you see them, and email Adobe as well, that can also help them work out any possible issues in the future.
Cheers,
Vince
-
Vincent,
Uncompressed HD projects are not the issue when it comes to PPro’s resources problem. In fact, because the material is uncompressed it tends to be be less demanding on the hardware.
I’ve had DV projects that fold up within 15 minutes and require a reboot – 10 to 15 a day. They had lots of very large sub-timelines – sub-timelines are something that can quickly bring PPro to a grinding halt. Try scrubbing a few 4kX4k graphics with motion moves and lighting effects in a half complicated, otherwise, not demanding, project. Adios.
And in case you think it might have been my hardware, I’m running an HP9300 with dual dual-core Opteron 275’s and 3GB or ram.
The problem is almost certainly in the initial architecture of the program. For whatever reasons they made a terrible blunder (or a calculated risk, depending on how you look at it) in the way PPro allocates Windows XP resources. Simply put, at some point, as a project demands more and more resources, a critical mass point gets reached and once that happens you’re in deep doodoo. Without Adobe issuing any guidelines on what things to avoid doing in your projects, the best rules of thumb is to keep them as small as possible, avoid subtimelines with large source clips by rendering them out and pulling the render into your timeline instead, and be careful about complicated effects and large graphics.
Many users have been complaining about this problem since version 1.0. It especially effects the high end community as their project resource requirements are larger. I know many people who are spitting nickles mad about it. In my first project on PPro, at certain points, I would have strangled the architects of the program, had I but got my fingers around their necks. But I learned. I now routinely break my projects up by acts and follow the above guidelines. Though I still have crashes and memory warnings I only have to restart on average under 5 times a day, and most of them are preventative. They’re not of the ‘do five things and then restart or crash’ variety that I experienced then.
The fact that Adobe has not corrected this problem by version 2.0 indicates that it’s probably deeply imbedded in the architecture and they’re relying on a Vista version to solve the problem. Well, until that happy day, (and the addition of full blown media management, and the streamling of inefficient work processes) PPro will not make much headway against Avid and to a certain extent, FCP, in the high end arena. Do they care? Well, if they want to be taken seriously as an NLE player, they should.
David
AllinOneFilms.com -
Hi David, Thank you so much for the insightful input!!!
Mark
-
David:
I work in long form with typically thousands of clips, etc. in the bins and have experienced all the ‘joys’ you describe with PremPro 2. I would have been delighted to have joined you in strangling the life out of the person/people at Adobe who designed (and marketed) the app.
I recently built a 64-bit sys using win xp pro x64. Though Adobe ‘does not support’ x64, it works like a charm with x64. With only 4gb of memory currently installed, all the memory-related lockups/crashes are history. Not one, nada, crash/freezeup since doing so.
Bill Buchanan
Buchanan Film Co. -
Bill,
That’s very interesting. I wonder if it was more the 4GB of ram than XP64 that solved your problems. I also wonder how well the Axio drivers would work. Worth investigating between projects.
David
AllinOneFilms.com -
David:
No. Because with the 32-bit sys, I tried only 3gb of RAM, too, since the capture card folks (BlackMagic Design) suggested not using more than 3gb of mem. The new sys uses much faster memory/fsb speeds, so that may be a contributing factor.
Bill
-
Hi Bill, How much does it cost to upgrade to the 64 bit system?
Still currently limping threw my project, now trying my latest DVD burn (2nd attempt, made it 80.00% untill the error mesage popped up, (lots of fun, not!!!).
Any suggestions on how to try to export back to tape (1080)?
Thanks guys!Mark
Reply to this Discussion! Login or Sign Up