Marcus Hardy
Forum Replies Created
-
Greetings all, been a hell of a week.
We figured it out. With the gracious assistance of T. Payton I might add.
After learning about the SQLite error, I researched it and found a couple forum posts complaining about a similar issue. They claimed that they were able to open it after a long time, say 8 hours. So following their advice, I did the same and sure enough it did indeed open, albeit incredibly slow, and laggy. Took me 5 minutes between each click. But here is what I did that helped me over come the dreaded offline compound clips.
Once open, I first made a new Event, on a separate hard drive, then, in my problem event I made a smart collection, and set it to find all compound clips in the event. Then after 20 minutes of beachballing, all my compound clips popped up, offline of course. Then I selected each of them and dragged them to the new event. once they appeared in the new event I quit final cut.
Then using event manager x, I moved all events and projects offline. And then proceeded to boot final cut immediately with a new event. Then I located all my media attached to the problem event and dragged it into the new event. But only as references, to keep down on space. Finally keeping my problem event offline, I proceeded to launch FCPX, and in three minutes flat, it launched and to my marvel, all my media and those damn compound clips came back online.
Now I don’t know how this fixed it exactly, but its what worked for me.
As maintenance I’m now in the process of eliminating the compound clips that are no longer in use, which also is helping bring down the database size.
Also, be warned that certain plug-ins store their data inside the event database, mainly coremelt products. This doesn’t mean they are bad products, the opposite exact, but just be careful with how heavily you use them.
Thank you again for everyone to help out with this, I don’t know if I would have been able to figure this all out if it weren’t for the cow. Thanks everybody! If you are ever in Calgary Alberta Canada, I’ll buy you a drink!
Cheers,
Marcus Hardy
-
Okay, thank you to everyone for the replies!
Don, thank you for that, I have in the past freaked out at my media being ‘offline’ due to proxy mode, but alas, that is not the case here. Though they really should have a different colour for things like that…
Loren, I’ve tried that tactic, repairing the event file and removing all the media located therein, but this too only results in the program to hang on loading the event.
T. Payton, my first thought was third party plugins especially those from Neat Video and Coremelt, two that I use heavily in this project. However after cleanly removing them, and pretty much every other plugin I have, this still doesn’t get me past the pinwheel.
This is the problem I discovered and will lead me to NOT use compound clips as often in the future for feature work. Compound clips being virtual clips and not actual physical clips, results in anything in FCPX that was in a compound clip and associated and located in that event becomes unreachable. You are unable to open the compound clip and peer inside, and because their is no physical media as far as FCPX is concerned, you cannot relink it to an event that DOES have all the media.
More details regarding the actual event, it is the main event that I started with this film and as a result has about 90% of the media associated with it. The others were created for ADR,VFX, and compound clips. However, and much to my dismay, most of my compound clips actually ended up located in the initial event. The film we made is a small budget sci fi, with ALL of its vfx being done in FCPX, as a result LOTS of compound clips were made to store composites. And then compound clips were made of scenes, OR later on, segments of the film. This is where we ran into problems. Our main, finished timeline is all compound clips, with compound clips inside each of them. In hindsight this was stupid, and in the rush and thrill of working on this film I neglected to realize how many compound clips were being ‘created’, I always did like it the way it was before…
Anyways, straight details: Event in question is 395.5 mbs in size with lots of compound clips inside it.
I’ve tried creating a new user (what i’m writing on now) and its still hanging at the load screen.
The only bright gleaming note in this is that Charlie’s advice provided potential pay dirt with revealing this little detail:
2013-05-20 10:53:55.591 PM Final Cut Pro[8230]: CoreData: error: (1) I/O error for database at /Volumes/RAID/Final Cut Events/Cold Lights/CurrentVersion.fcpevent. SQLite error code:1, ‘too many SQL variables’
Now I have no idea how to read this, but my guess is that my project has too many compound clips for FCPX to measure and as a result it freaks out and doesn’t load.
Any ideas on what I can do?
-
Thanks for your response. I’ve run diagnostics on the hard drive in question numerous times, and its always reported clean and good. So I don’t think its a hardware problem. I have numerous back ups of the event and media, I’ve tried the FCPX created ‘backup’ and it still hangs on loading, and I’ve tried opening one of my own created backups, one even as far back as october, still won’t load it. I’m not sure what to make of it, I have dozens of other events on this hard drive, and they all load lightning fast, its literally this singular event that causes the problem.
Is there any way I can ‘trick’ FCPX into relinking my project to a separate event? So I can avoid having to deal with this headache all together?
-
I picked up Diskwarrior and it indeed did save my bacon so to speak. haha, it took all night but I managed to salvage everything except the event files, which is fine, cause I just created a new one and relinked the project media. Time consuming, but the project was saved. Now to tell my client his misfortune of having to buy another hard drive haha
Thanks for everyones help!
-
Yup, disk utility just confirmed it:
-
Nope, it just ‘prepares’ but doesn’t actually copy anything over.
Also it hangs Disk Utility when I try and repair it…
-
And this is what happens when I leave it alone…
Does this mean its corrupt?
-
That’s what I thought, but whenever I try and copy the Event and Project for that matter from the hard drive to a faster drive it starts then stops at 3.5 MB, again this is only a 19 GB Event… it shouldn’t be that hard…
-
No need to get aggressive, I wasn’t trying to defend FCPX in its ability to handle media, the guy asked if it could handle a feature length project, and from a timeline standpoint it can. That’s all I was saying, I wasn’t advocating for him to use it. Purely trying to be helpful.
No flame wars.
And lest we forget I did state that CS6 and for that matter Avid are excellent options as well.
Sorry if I offended.
-
I’m editing one this summer, and I plan to edit it entirely in FCPX. We are shooting all on 5D’s so this shouldn’t be a problem. We are currently doing VFX tests seeing how FCPX handles them. So far so good.
As a stress test I imported and merged Kill Bill Parts 1 and 2, adding up to a 4 hour project (timeline) it stuttered quite a bit, but once rendered it was perfectly fine. Edits caused a little lag. But not too bad. I even exported it and it turned out great!
Case in point, FCPX as it stands now is capable of handling a project of a feature’s length.
Hope your feature goes well CS6 is pretty awesome too. 🙂
RED support has been promised by the end of the year. So fingers crossed its sooner than that.
