-
Will upgrading to FCP 6.0.2 stops the crashing of FCP?
Hi,
just wanted to ask if updating to FCP 6.0.2 would solve the crashing on our current FCP we are running 6.0.1 almost all of my FCP machines MACPRO with 4GB of memory everyday will crash, and I done everyting from repairing disk permission, zapping pram, running FCP6 Rescue. tried reinstalling the whole system. I just crashes, I dont know why.
here are the logs of 4 macpro units and are all the same
PID: 298
Thread: 0Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000console:
Final Cut Pro Malloc: cannot allocate region,
——-
dont know if this is FCP problem of our system
and by the way all of our macpro units are connected to xsan doing xdcam format running QT 7.2 nad FCP 6.0.1
will upgrading to QT7.3 and FCO 6.0.2 solve the crashing problem of ours.
please help thanks…
-
12 Replies
-
Considering that error contains “bad access” in the error, sounds like an xSan issue. We have three systems running FCP 6 and all have been stable since last June when we installed the software. We’re not running shared storage.
Sounds like you need to address your Xsan rather than updating FCP. Especially since you say all foru machines get the same “bad access” error. That xSan is the one thing connected to all four systems.
Walter Biscardi, Jr.
Biscardi Creative Media
HD and SD Production for Broadcast and Independent Productions.STOP STARING AND START GRADING WITH APPLE COLOR
The new Color Training DVD now available from the Creative Cow! -
yes all are connected, im not sure where to start in the xsan system,i tried checking the log of xsan seems to be normal, i can’t find any mysterious log.
for a month and a half it was perfectly working fine, with no crashing at all, i dont know what happen after last last week FCP begun to crash a lot 4-5 times a day, when you try to look at the logs it pertains to allocating memory, and the logs also doesn’t say about xsan. im completey unaware right now of what’s is happening.
i cannot think of other options right now but to upgrade.
-
Did anyone have a bad crash that resulted in having to do a hard power down of their Mac? That can easily cause corruption to the media array.
Have you tried running with the systems one at a time? Turn on one system, edit with it for 30 minutes. Then turn on another system, edit with it for 30 minutes and so on. If you’re able to edit ok until one of the systems comes online, then you probably have a culprit to the issue.
It could be a problem with the media on that one system or that system has something going on to cause the xSan to become unstable.
Another thing to try, if you have enough backup capabilities, move all the media off the xSan and try wiping it clean, then move all the media back. That would remove any corruption internal to the array.
You can update all your systems, but I don’t think that’s going to do anything to solve your issue. I really think there’s something corrupted on the xSan and maybe just one of the systems.
Walter Biscardi, Jr.
Biscardi Creative Media
HD and SD Production for Broadcast and Independent Productions.STOP STARING AND START GRADING WITH APPLE COLOR
The new Color Training DVD now available from the Creative Cow! -
We had a huge problem with XSan once we upgradaed the machines to Leopard. It was weird, actually, as it worked fine for a week, then suddenly we lost connections and weird problems all around. Soon after, the fibre cards to the fibre switch lost connection, and firewire drives were randomly dropping out and it would take a day or two before they would come back.
Our solution was to reinstall (fresh) 10.4.x and rebuild the array. Once downgraded, everything has been working like a charm. I am not at all thrilled with the new OS. –And, to my knowledge, there isn’t a stand alone installer for XSan on 10.5. (at least I couldn’t find anywhere) -Have to install on 10.4 and “upgrade” all. But that’s just my humble opinion…
–And we are running 6.0.2 which had been running like a charmTim
-G5 Quad PPC
-G4
-Macbook Pro’s (G4,G5)
-XRAID
-XSERVE
-iMac -
hmmm, it seems like the culprit is the xsan, but i dont know im at lost now. What i have observed though is that when adding 5 or more sequences in the project file and you let it play for the whole day directly thorugh xsan it just works fine it will just play the whole day. the crashing happens in the middle of their editing or in the end of editing, when you leave final cut pro open it will not crash, though i tested only two macpros, the only application running in the editing machines are FCP, xdcam transfer software and some photoshop.
is FCP capable of handling many Timelines and files?
this is how editors work, bare with me cause im not an editor, in one project file, they will create a new sequence and named it material, and in these sequence they will import a folder and in this folder around 40-50 .mov files these files are not heavy the format is xdcam and each file around 2-3 mins maximum 10mins of footage stored in xsan, after these they will create another sequence and named it final, from the material they will just copy and paste footage to the final sequnce until they arrive a final output. seems like a good workflow, they dont use fancy plugins or filters just native plugins of FCP since this is a news business.
currently i change the memory two RiserA-2GB and RiserB-2GB as the documents in apple suggested that memory should be symmetrical, same brand, same speed, same all and it lessens the crash, but still crashing persist.
rebuilding the xsan is not my option right now since they are using the xsan directly playing the news live on air. morning, afternoon and night.
editors complain a lot cause it disturbed there work on finishing at schedule.
here are my systems
xsan 1.4.1
Server 10.4.10
FCP 6.0.1
QT 7.2apple really does a weird thing.. hope anyone could enlighten me if what i’ve done wrong.
-
Do you have your PCIe slots set to option #2?
What PCIe cards do you have in your machines?
-
two of them have AJA and the settings of the slot PCIe are set to #3 as recommended by AJA and the other two which donot have I/O cards are also set to PCIe #3
which PCIe settings would i set?
-
[maccebu] “this is how editors work, bare with me cause im not an editor, in one project file, they will create a new sequence and named it material, and in these sequence they will import a folder and in this folder around 40-50 .mov files these files are not heavy the format is xdcam and each file around 2-3 mins maximum 10mins of footage stored in xsan, after these they will create another sequence and named it final, from the material they will just copy and paste footage to the final sequnce until they arrive a final output. seems like a good workflow, they dont use fancy plugins or filters just native plugins of FCP since this is a news business.”
copying and pasting footage from one sequence to another has never been a good workflow in my experience. FCP seems to cause a lot of issues when you do this. Having multiple timelines open is fine, but when you just copy / paste footage across timelines, there seems to all sorts of issues.
We always edit through the Viewer to set In / outs and then move the footage into the appropriate timeline.
Walter Biscardi, Jr.
Biscardi Creative Media
HD and SD Production for Broadcast and Independent Productions.STOP STARING AND START GRADING WITH APPLE COLOR
The new Color Training DVD now available from the Creative Cow! -
ah you given me a hint, this is what im thinking also that copying through sequence is not a good idea. well try to talk to our editors to create in and outs in the viewer directly and not in the sequences and well see if this will cause crashing again.
-
[maccebu] “two of them have AJA and the settings of the slot PCIe are set to #3 as recommended by AJA and the other two which donot have I/O cards are also set to PCIe #3 “
Option #2 is recommended by AJA. I am not talking about which slot the PCIe is in, I am talking about the PCIe Slot config Utility which can be found In the System > Library > COre Services > Expansion SLot Utility.app. Select option 2 and restart.
https://www.aja.com/html/support_kona_rec_sys.htm#
https://www.aja.com/html/support_xena_boards/exp_large.htm
Jeremy
Reply to this Discussion! Login or Sign Up