Serious Project File Corruption in FCP 5.0 and FCP 5.0.2

[Walter Biscardi]

[Walter Biscardi] “Working on a DV-NTSC project and am suddenly getting the red Canvas Screen with the “Out of Memory” error. I’ll quit FCP, trash prefs, re-launch FCP and will get the “” error message when I try to launch the affected timeline. There is no way to open the timeline up. For some reason I can right click on the Sequence icon in the Browser and export the timeline as a Quicktime movie but FCP refused to allow me to open up the timeline at all.”

Whoops, left out that I get the “Not Found” error messgae when I try to launch the affected timeline after re-launching FCP.

Walter Biscardi, Jr.
Creative Genius, Biscardi Creative Media
https://www.biscardicreative.com

Now in Production, “The Rough Cut,” https://www.theroughcutmovie.com

“I reject your reality and substitute my own!” – Adam Savage, Mythbusters

[Walter Biscardi]

Looks like we found it. The Still Memory setting needed to be turned up so we upped it to 50% from the original 10%. I never figured on that one since there’s only 20 stills and 4 photoshop graphics. So there you go, make sure you have enough Still Memory allocated to your projects if you see something like this.

Hopefully this info helps someone else out there.

Walter Biscardi, Jr.
Creative Genius, Biscardi Creative Media
https://www.biscardicreative.com

Now in Production, “The Rough Cut,” https://www.theroughcutmovie.com

“I reject your reality and substitute my own!” – Adam Savage, Mythbusters

[Peter Wiggins]

walter,

I share your pain, I went through something similar in April, but I ended up getting the grey screen of death. 🙁

have you tried:-

Opening up a dummy project in the same resolution first, then opening up the project with the troubled timeline?
Considered running the 6.5.2. QT reversioner? (not too sure what what happen to your media)
Are you running a standard video card? My G5 was fine until I installed the ATI drivers, but that could have been coincidental.
Does it still happen if you duplicate the project?
Does it happen if you move the project & media onto another system?

Have to say the only thing that fixed it for me was an archive & install – I hope it doesn’t get that serious and it is something simple that fixes easily.

Good luck!

Peter

https://www.peterwiggins.com

Having a rest after working 6 weeks without a day off

[Peter Wiggins]

It was something simple! 🙂

Peter

https://www.peterwiggins.com

Having a rest after working 6 weeks without a day off

[Bret Williams]

I had the same problem a month ago. But it was version 4.5 running QT 7. I tried upping the still cached to 50, 80, 100, didn’t matter. The minute I placed the playhead in a particular sequence, the project was done for, wouldn’t open, etc. I had to do the same thing and export the seqeunce as a QT. Thankfully the project was simply a bunch of clips with slates between them and everything faded up and down from black. But it was the first 20minutes of a 3 or 4 hour project.

I think the issue was similar, but different. I was using a nested sequence for a slate that got repeated every clip. I figured if they change that slate I didn’t want to change it 40 times, just once. But after a certain number of uses, I guess the system just couldn’t handle it. I’ve got 1.75 gigs, but it didn’t matter.

I imported the QTs, started a new project, dragged the raw clips into a bin and quit the nested sequences. 40 hours of work later and I haven’t had an issue. I did however rebuild my entire system and upgrade to FCP 5 during the project.

[Walter Biscardi]

[Peter Wiggins] “It was something simple! :-)”

I really don’t understand this one and will have to delve deeper into this when I clear the project out. It’s only 20 still images and 4 photoshop files, all 72dpi so why does that cause an utter shutdown of a project even with the default Still memory cache? In 4 years of cutting with FCP I’ve never adjusted that setting and have had projects with several hundred stills in them.

I think it’s definitely some sort of a buggy still frame thing that has not been solve in FCP 5.0 and want to run some tests to see how easy / hard it is to set off this issue.

Walter Biscardi, Jr.
Creative Genius, Biscardi Creative Media
https://www.biscardicreative.com

Now in Production, “The Rough Cut,” https://www.theroughcutmovie.com

“I reject your reality and substitute my own!” – Adam Savage, Mythbusters

[Mitch Ives]

Clearly something that needs addressing. I’ve used lots of stills in the past, and generally have the still cache at around 25%, but I’ve never seen it do this. I’ve seen it take forever to open a project with many stills (in the past), but not refuse to open…

Thanks for sharing this…

Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com
http://www.insightproductions.com

[Tom Matthies]

I had a similar experience just tonight. I was going to post a query before calling it a day, and saw this post.
In my case, I’m editing the first “real” project on the new machine-DP2.3, Tiger, FCP5.02. I was literally putting in the last effect, a fade from color, onto a Psd that was on the top layer of my sequence. Upon applying the filter, I got the orange screen of death telling me to close and reopen this window to restore. I closed the canvas window, as instructed, and when I attempted to open my sequence I was met my an “Operation not allowed” screen followed by an “Out of memory” screen. Even after rebooting the computer, it refused to open that sequence. I restored from the last version in the AS vault, rebuilt the last series of edits and all was well. After saving the project, I again attemped to reproduce the problem. I added the fade to color transition to the top, Psd layer again and BAM! the exact same crash. It does it everytime.
I never thought I’d say that I miss the stability of my old G4 and FCP4.5.
Actually, that thing almost NEVER crashed. Very stable
FCP 5 and the new G5 is still a little too buggy for my taste.
But is IS faster! Guess it’s a trade off.
Calling it a night…
Tom

[Chris Tomberlin]

[Tom Matthies] “FCP 5 and the new G5 is still a little too buggy for my taste.
But is IS faster! “

“Faster” like a PC running windows is “faster?” Once you factor in the crashing and trouble shooting, FCP 5 on Tiger can’t possibly be faster at the moment. Plus, there are some real problems with the 10 bit codec right now. Do search in the After Effects and Blackmagic forums and you’ll see what I mean…

Chris Tomberlin
OutPost Pictures

[Bret Williams]

Well, my problems WERE on a dual G4 with FCP 4.5. 🙂