I downloaded 5.0.3.8 patch and installed... same problem.
I have OSX 10.6.6 with 2.66Ghz Dual Xeon, 8GB of memory.
What's in the bin? Are they RED clips?
Must think of something clever to go here...
this is a problem that's been happening since at least 4. 05, if you have a lot of bins with lots of edits / media in them you're memory will eventually max out forcing a restart.
I believe in Mc 5 the move to automatic keyframes has exaggerated this problem, as the keyframe information builds up to cause greater memory.
I for one have mentioned this to various AVID representatives over time but have not received any explanation as yet....
Dear Larry,
I've Patched some of my Z800 qualified Systems and i have still the same Memoy Issues. I first thought it's only on XDCAM HD 50 mbit Projects. But actually this morning the memory is raising on every Projects SD or HD. 5.0.3.8 is more stable but still the worst version I have worked with.
Greets Phil
Post Production Supervisor / System Support Engineer
Phil.IP: Dear Larry, I've Patched some of my Z800 qualified Systems and i have still the same Memoy Issues. I first thought it's only on XDCAM HD 50 mbit Projects. But actually this morning the memory is raising on every Projects SD or HD. 5.0.3.8 is more stable but still the worst version I have worked with. Greets Phil
I don't believe we will get anywhere now with any resolution on MC v 5.0.xx.xx. Avid have virtually not made any official comment on the memory issue. It's as if it never existed.
It seems the only way out of this mess is to fork out more cash to buy v 5.5 despite the fact that we paid for v5.0, a product that never ever worked properly. It's a travesty and extremely unethical.
This does not seem right nor fair. Avid are being very arrogant here. I feel we should be compensated for the unrecoverable editing hours and money lost due to all the problems with v5.0. MC5.5 should be FREE as a professional gesture to all the stressed out loyal Avid users!!
Wouldn't that be a major PR boost for Avid at NAB?? (pigs will fly - as they say)
Howard Kramer
Avid Editor / System Support Engineer
AV Intelligence - Auckland, New Zealand
I happy to report that Marianna is back with us again, and I've pinged her asking for a status update.
Larry Rubin
Senior Editor
The Pentagon Channel
www.pentagonchannel.mil
It normally happens when I edit something with multiple layers with PIP, matte key, 3D Warp, text, etc. I found out that memory usage jumps up about 1% everytime I open effect editor, even though I don't make any changes. I guess it has to have something with effects.
I imported .psd, .jpg, .tiff, quicktime media, .aif files etc. for the project. And I didn't use AMA, I imported all.
That's pretty much identical to my experience except I had no graphics when this bug nailed me. Multiple 3DWarp PiPs with spectramatte. I had a bunch of compositions set up and when I got about halfway through applying the keyer to the layers, it started crashing. A day and a half of my life I won't get back, and a reminder why I usually do this kind of stuff in AE.
It seems I have the same problem. I can not find any apparent cause. It can start when I open a very simple project. When I open the "memory info" the indicator bars are going up and down. Total memory seems to make the most radical changes but the "objects" number can jump very high and then go back down. It doesn,t seem to have any correlation with the complexity of the project and/or the effects or plug-ins I use. Eventually I get the warning of low memory and then the crash. I have just updated from MC5 to MC5.03 andrunning it on a MacPro Intel Harperstown and OS 10.6.4
BustedFlush
Larry Rubin: I happy to report that Marianna is back with us again, and I've pinged her asking for a status update.
Does Marianna have the power to compensate everyone? As much as I respect her/everyone's input and grateful of all the knowledge gained by everyone here, I've not heard an "official" peep from anyone at Avid, only the good people who participate in these forums.
I (like everyone else who uses MC 5) have lost some of my life to this issue both in terms of time lost and stress gained. My time is very important to me, not only in the professional sense, but this is time from my life I will never get back. We only have a finite amount of time on this earth. The fact that it costs money to upgrade from MC5 to MC 5.5 is the ultimate insult. Not only have I had a portion of my life (and still ongoing) taken from me, now they want more money.
What beggars belief is that Avid don't have the respect for us, their customers to even admit a mistake. By not addressing this issue, they are only losing customers and ultimately, money. Send this to the suits pointing at pie charts.
Yes, this is a gripe, a rant, call it what you want. I guess the answer to my original question would be a no, then. I am livid.
I think this MC5 Memory Issue is a Java Problem. Actually MC5 comes with JRE 6 update 6. Anybody tried JRE6 Update 7 ? I will update Java on a test machine and give feedback here
Not had a chance to see if V5.5.1 fixes the memory leaks but V5.0 was horrid.
The only solutions we found were to use Windows 7 64 bit and have 6GB or more RAM.
And even then we had to tell editors to shut down at lunchtime and restart to restore performance.
Otherwise by 3pm the machines became dogs (even in a training environment).
Not a great advert for Avid to all the editors and clients who sit and watch this happen but we have no oater official answer or solution.
Broadcast & Post Production Consultant / Trainer Avid Certified Instructor VET (Retired Early 2022)
Still offering training and support for: QC/QAR Training - Understanding Digital Media - Advanced Files * Compression - Avid Ingest - PSE fixing courses and more.
Mainly delivered remotely via zoom but onsite possible.
T 07581 201248 | E pat@vet-training.co.uk
I haven't had this particular issue (& I have Java installed, up to date), but I will +1 to ChrisH's thoughts & experiences. I had several big issues with MC v5.0.X that were never resolved & are still active topics on the forums.
It's always ridiculous to know that a company's been busy working on new features & new version for more $ instead of putting resourcse into making their product work correctly & fix what's already broken. And yes, specialized customer support attention to those customers--customers, who paid money for a stable product--that have been having ongoing issues and have been cooperative enough to essentially beta test Avid's software for them, would be a great investment on Avid's part to give them a new version for free, especially if it fixes the issues they are having. I mean really, it's going to hurt Avid's pockets to take care of 20 or 30 paying customers privately? Not in the long run if they make people happy.
Anyway.. it's been bad enough that I had to downgrade back to v4 for any of the projects I worked on in Avid, and quite frankly due to MC's lack of basic features (while boasting 1 or 2 things they finally caught up to Apple or Adobe on several years late) leaves me to almost always choose something else for new projects. The only exception would be long form editing & anything more narrative film where all I need to do it cut; otherwise, the robustness & flexibility that competition has is just light years ahead, & that's fine.. Avid's primary market is films & television that only needs to be cut, and it's the best at that. But with v5's bug, even some of these projects, I've been taking them to something I know is more reliable.
& It's not at too surprising anymore when I find Avid houses running MC v3.X or read about some big motion picture that "cut the film on Media Composer v3.X"; or when I hear that they are considering other software when they upgrade.
I'm taking a new project, reluctantly, into 5.5 trial just to see what happens.
Here's to hoping I guess :) .
- wb
ChrisH: Larry Rubin: I happy to report that Marianna is back with us again, and I've pinged her asking for a status update. Does Marianna have the power to compensate everyone? As much as I respect her/everyone's input and grateful of all the knowledge gained by everyone here, I've not heard an "official" peep from anyone at Avid, only the good people who participate in these forums. I (like everyone else who uses MC 5) have lost some of my life to this issue both in terms of time lost and stress gained. My time is very important to me, not only in the professional sense, but this is time from my life I will never get back. We only have a finite amount of time on this earth. The fact that it costs money to upgrade from MC5 to MC 5.5 is the ultimate insult. Not only have I had a portion of my life (and still ongoing) taken from me, now they want more money. What beggars belief is that Avid don't have the respect for us, their customers to even admit a mistake. By not addressing this issue, they are only losing customers and ultimately, money. Send this to the suits pointing at pie charts. Yes, this is a gripe, a rant, call it what you want. I guess the answer to my original question would be a no, then. I am livid.
ChrisH...
I hear you.... yes I am back and working like a one arm paper hanger to answer emails and forum posts. Unforunately, during my time away there wasnt much posting activity from Avid on this topic. There was movement inside Avid to fix the memory problems but no one communicated this to the community. All I can do is apologize for that.....
I did post today after having a comversation with continuation engineering and the product champion. There were additonal memory issues resovlved in the 5.x patches and one in the recent 5.5.1.
We know we havent gotten it all.... Could you send me a email off forum with the following:
Specifications, OS, QT and MC version you have this issue on and a crash log or 2?
Give me a day or 2 to see what the scoop is and Ill report back.
Marianna
marianna.montague@avid.com
I posted this t the other Out Of Memory (OOM) Thread....
Another fix for OOM errors is to turn off Airport. Could a few of you try this and report back to me via email?
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller