DISASTER!!! FCPX Corrupt Project: 'too many SQL variables' error?

Question

Level 1

0 points

DISASTER!!! FCPX Corrupt Project: 'too many SQL variables' error?

Hi,

I'm desperately tring to repair a corrupt project file, if I can't I'll have lost a week of work and I have to release the final project (a 2-hour feature!) in less than 2 weeks, with about another 9 days of solid work ahead of me (or so I thought).

I've pored over forums all over Apple Support and elsewhere, tried EVERYTHING, trust me, you name it, I've tried it. FCPX hangs when it gets to the 'load (my) project' screen if I'm scrolling to it in the Project Library. After moving my Events, trashing render files, trashing prefs, reinstalling FCPX, booting in safe mode, using the Digital Rebellion Project Repair tool, logged in as a different user, tried to open it on a different machine... (like I said, I've tried everything), still hanging, same way everywhere.

I've consistently received this error message from console as soon as FCPX attempts to load this project (note that it's already opened fine, loaded every other project fine, it's just when it gets to this one):

6.17.12 12:17:40.401 AM Final Cut Pro: Core Data: annotation: -executeRequest: encountered exception = I/O error for database at /Volumes/PROMISE PEGASUS/Final Cut Projects/MASTER BUILD/CurrentVersion copy.bak.fcpproject. SQLite error code:1, 'too many SQL variables' with userInfo = {

NSFilePath = "/Volumes/PROMISE PEGASUS/Final Cut Projects/MASTER BUILD/CurrentVersion copy.bak.fcpproject";

NSSQLiteErrorDomain = 1;

}

If anyone can help me solve this I will be eternally grateful, this is near catastrophic for me!!!!!

Posted on Jun 17, 2012 12:25 AM

Reply

Answer 1

Jun 18, 2012 10:13 AM in response to TheFlaneur

I can't guarantee anything, but if you send me your project file I'll take a look at it. You can contact me here:

http://www.digitalrebellion.com/contact.html

Reply

Answer 2

TheFlaneur Author

Level 1

0 points

Jun 18, 2012 10:39 AM in response to Jon Chappell

Thanks, Jon.

Luckily, I have a good friend who is savvy with SQLite, so he dug around in the project file via Terminal to investigate. Ironically, it wasn't until he couldn't find anything that he realized the meaning of the error message: SQL variables apparently max out at 999, so his assessment was that my project simply got too big and/or complex. It is, after all, over 500MB and very *very* complex project.

I let it run overnight trying to open and after approximately 8 hours, it actually did. I should point out that I let it run on a separate machine with no events or projects on the disc.

I broke the project down into 6 smaller projects and brought them back over to my production machine. Everything opened fine.

Unfortunately, I discovered later that I had none of my custom Motion templates on the separate machine I had used for the overnight opening. For some reason, none of those FX settings carried over to the newly built, smaller project chunks so in a sense, the rebuild was rendered moot.

Regardless, the most important parts of the work have been salvaged and I can just re-apply some of the missing FX pretty easily.

Lesson learned.

Jon, if you're still curious I'll go ahead and send you the file.

Thanks.

Reply

Answer 3

Jun 18, 2012 11:34 AM in response to TheFlaneur

That explanation makes perfect sense. 500 MB is a huge project.

Reply