-
Corruption
I’m about to start the process of elimination regarding this problem but wanted to ask if anyone has had anything remotely like this. I’ll quote what I just wrote on another thread:
“Gotta say, my life in X has sucked since 1.0.3.
My problem is that I was setting up a new room at home and I added everything from 16GB of new RAM (OWC) to a new Focusrite interface and drivers, so knowing the cause is my new mission today.
Anyway I have had crashes, horribly corrupt files, and worse, for the first time ever, computer crashes from freezing to the dreaded dimming screen and death message from Apple.”
More to the point, I have one TV spot, a lot of design, that would take days to recreate. I found that all of the graphics needed re-rendering now that it was opened in 1.0.3, constant re-rendering.
So while working with it I had a crash. When I went back to it, dozens of graphic files were gone?
Through exploration, I found when I V’ed a clip in the Primary I could see all the associated graphics for that clip, buried under it IN THE PRIMARY – well that defies the laws of X (and 7 etc). And so it went for clip after clip.
Then as I tried everything to try and save the project from starting a new .3 project and copying files in and got nothing but 2 days of both program and system crashes.
The material was Pro Res but showed as h.264 in the inspector, the footage was 24p but showed as 30p in the inspector…a complete mess of a project, that was perfectly finished before the crash.
Oh, and after finally getting it all fixed (I had long ago deleted the previous project from the folder) and rendering it out as a 1080 Pro Res Master, I’ve got digital glitches, blocks, color crap etc. streaking the footage.
Haven’t seen that since I finished the Olympic documentary using all the 25 year old ABC 3/4″ footage.
Anyone seen anything like this kind of corruption in FCPX ?
Jim
-
8 Replies
-
If this is new RAM, that’s the first place I’d look.
Ouch.
-
In the best tradition of responding to one’s own post:
Did your run a Memtest Jim?
Yeah I just did and found a failure message in Terminal that would suggest bad or poorly seated RAM.
That makes sense, can’t think of anything that would cause both Kernel Panic crash and corrupt files and media like that.
I’ll start by resetting all the new RAM and running the Memtest again.
-
[Jeremy Garchow] “If this is new RAM, that’s the first place I’d look.
Ouch.”
Thanks Jeremy,
See my response to myself above.
Aside having to rebuild everything with a program that was working like Premiere 1 on a Quadra 840, and staying up till 8:00 AM to get it back together, I’m really glad to find it quickly.I’m anxious to get things flying the way I expected after updating X, adding 16GB of new RAM and new drives.
I wasn’t expecting to have to edit with a splicing block. -
Make sure you are installing the RAM correctly. I was having trouble with added RAM and discovered that I had not followed the instructions to the “t”. Is this a Mac Pro? Check OWC’s site for installation instructions.
NT
-
Just made the mistake off adding 8GB OWC RAM with current 1GB sticks. Had to ditch the 1GBs.
RAM is evil new or old when it acts up 😛 -
I ran a Rember test for each block, one by one, laborious but I discovered one bad module out of the 4 new from OWC.
So it’s all stable again and I just have to get that block replaced.
I can deal with anything but corrupt projects.
-
A couple of weeks ago I was cutting a piece with all 1080/29.97 footage from my Canon XF100 and I had complete program crash. Wasn’t doing anything too intense, just roughing in footage and some photoshop (single layer) titles. Relaunched and reopened the project and it just looked funny. Well, it had changed to 720p/25 and there was no options for changing it back.
Had to rebuild. No biggie as I was only a couple of clips into it. Haven’t had it happen again, but stuff like that just screams “beta”.
-
Yes it does sound like beta, but the Avid MC at 5.5 and from the sounds of it v6 is beta too 🙂
We’re holding on to 5.5 till the rest of the beta testers on v6 are calmed 😉
Reply to this Discussion! Login or Sign Up