FCPX 10.2.1 crashes

Well, I've just had my first crash with 2.1. I had thought that the Tbolt drive had come unmounted. But for whatever reason, I am seeing same as everyone else here, (without the text issue.)
I cannot open ANY backups of this particular project/Library. Crashes every time. Others on same HD open fine.
I have trashed prefs, repaired, and reinstalled from App store.
Would moving the Library via Finder to another HD do any good? Any other tricks to saving several months of work???

No way to repair/restore corrupted Library? OK, I will reedited the thing. Probably do a better job now anyway. I know the footage so much better. Not a big job anyhow.
Moving library has not effect. Same crashing.

Gretta wrote: No way to repair/restore corrupted Library? OK, I will reedited the thing. Probably do a better job now anyway. I know the footage so much better. Not a big job anyhow.
Moving library has not effect. Same crashing.

This looks very consistent with corrupted media, not a corrupted a library. Especially since the backups will not open as well. Try hiding the media and then see if the library will open without it.

Let me know how this goes.

How to hide media? I dragged the original media folder out of the pkg, but still crash on launch. Is this what you meant?
I would sincerely like to get to the root cause of this, and I am less concerned about reediting the piece.
Would this corruption happen, do you think, by leaving the project open untouched for a few hours and the Tbolt drive unmounting? Lately the computer has been rebooting itself (not while I am working–I hear it from another room!)
I think it is time to call in my AppleCare chips.

Gretta wrote: How to hide media? I dragged the original media folder out of the pkg, but still crash on launch. Is this what you meant?

If you have multiple events, there can be many original media folders. Also I should have specified as well that any media in the cache could also be corrupted.

One way to do this is to create a library with only that databases. To do this duplicate your library (might take some time if you have managed media), then in the duped library go in each event (folder in the package) and start deleting all your event Original Media folders, Render Files & Transcoded Media folders. Then in the root of the library package remove settings.plist, current version.flexolibrary, __Sync___ and __ Temp if they exist.

Now relaunch test this.

If this still doesn't launch you'll need to start systematically hiding events (move them out of the library) until you can get it to launch.

All this will do is help you isolate the issue. If writing was happening during the disconnection of your device, it is most likely to rendered media, but it could happen to original media as well.

Since you can, and it's not a big deal, re-edit, from scratch. Re-import everything into a new Library.

Thanx, TPayton, all that didn't do it, but I will save these instructions for the future.
Yes, Ben, spent most of today on it. I had forgotten all the notes and tags I have to redo. And the renaming I did in FCP, but actually easier and better now that I have already made so many decisions.
<sigh>

Gretta wrote: Thanx, TPayton, all that didn't do it, but I will save these instructions for the future.
Yes, Ben, spent most of today on it. I had forgotten all the notes and tags I have to redo. And the renaming I did in FCP, but actually easier and better now that I have already made so many decisions.
<sigh>

Well that is a first. Never heard of something causing even your backups to go bad.

Glad you can remake it.

So Mac Pro Maxed out, Thunderbolt Cinema And a Samsung on DVI with monitoring off my Matrox mini. FCPX Crashes repeatedly on audio editing and it is only fixed by removing the second monitor. Very Annoying.

JG

Pepper Rafferty wrote: So Mac Pro Maxed out, Thunderbolt Cinema And a Samsung on DVI with monitoring off my Matrox mini. FCPX Crashes repeatedly on audio editing and it is only fixed by removing the second monitor. Very Annoying.

JG

I have a very similar machine, 2 monitors and a Matrox Mini humm no problems like that. In fact super stable. Something must be up with the setup or hardware. Can you tell me a few things, I'll help you isolate the issue.

- MacPro Model & Year, how much Ram,
- OS version, FCPX version, Matrox MXO2 Mini SW Version
- How is your MX02 connected to your Mac? i.e. thunderbolt, pci?
- Are you using any third party audio plugins?
- How is the DVI monitor being connected, to a video card or adapter? If to a video card, what video card model is it?
- Can you describe the audio editing you are preforming? Is this reproducible?

- T.

Hi T

Mac Pro Late 2013 3.5 GHz 6-Core Intel Xeon E5 32 GB 1866 MHz DDR3 ECC AMD FirePro D700 6144 MB

OSX 10.10.3 FCPX 10.2.1

Martrox Mini 02 connected via Thunderbolt but via converter and its not the max version

No 3rd Party Audio Plugs

DVI connected via thunderbolt connector.

The crash has happened both on audio and video usually when trimming or rolling edit points. It is unpredictable but frequent.

Thanks - so where are you storing your FCPX library and where are you storing media? (drive names, brands, etc.)

Also can you give me a full list of your peripherals and how they are connected (USB, USB Hubs, Thunderbolt docs, etc.)

Also where did you get your thunderbolt cables?

Library on Pegasus 8TB RAID with all media connected via thunderbolt.
Wireless mouse USB keyboard and sound line out,

Thanks for the help

Turns out that MY problem was with the mirrored 2 disc RAID the Library was on. One drive failed. Still under warranty. Backups on the boot drive, so still a mystery why they are corrupted.

Pepper Rafferty wrote: Library on Pegasus 8TB RAID with all media connected via thunderbolt.
Wireless mouse USB keyboard and sound line out,

Thanks for the help

Just to clarify your Library and your media are both on the Pegasus?

No other drives? Only the keyboard on USB? You are using the 1/8 sound out?

Yes T that's correct the library and all media assets are on the Pegasus

What Matrox version? do you have broadcast out on all the time when the crashes occur? Any chance you are editing auditions?

Hey Pepper.

Have you tried to completely disconnect the Matrox? FWIW, I just sold my MXO2 Mini on Ebay, and I think that was one of the happiest days of my life! The only reason I got the Matrox in the first place was to be able to have a second monitor working with Final Cut 7, which I have not used in a year.

Final Cut X has a pretty nice "Show viewers on second display" command which made the price of FCP X worth the price right there.

Matrox is notoriously slow with their driver updates, and by the time they finally do come out with the current driver, there is either a new version of FC or OS X!!! But to their credit, they are good at working on solving issues.

I'm assuming you do have the most current drivers???

Jonathan

Btw. Without seeing the crash logs I am suspecting thunderbolt issue, bus overload of some kind, maybe a cable. So let's deal with that first. Of course it is also possible the Matrox software, or the Pegasus could have issues. When you trim, especially with the keyboard, fcpx is making small random reads and writes to the project timeline database file, therefore problems with the drive media itself of communication to that media could be the culprit. It is kinda Like a car with stop and go driving puts more strain on your engine that driving on the highway. Especially since disconnecting the second display resolves it, the issue seems to be thunderbolt bus related.

Since you are using 3 thunderbolt ports, do you have each one on a different bus? By moving things around you may be able to figure out if perhaps it is a bad bus or bus overload.

See here, for a little discussion on this. www.fcpworks.com/thunderbolt-bus-mapping-new-mac-pro/

A more likely situation is a bad thunderbolt cable, even a bad minidisplayport to dvi cable. If you bought those from apple just goto the Apple Store and they will swap all of them out for you.

Btw. On my iMac (with only one thunderbolt bus) I was having all sorts of drive disconnection issues and then a fellow fcpx editor recommended getting a thunderbolt doc (I got the caldigit t2 www.caldigit.com/thunderboltstation2/ ) and my issues went away. So I'm suspecting this is bus related.

Let me know how this goes.