The Share Operation Master File has Failed – when creating a frame (error -1)

[Fabrizio D’agnano]

I had a similar problem a couple of months ago. FCPX refused to export and stopped all the times at the same frame, contained in a plain video clip with no effects or whatever. I could export low res demos, even a HD range containing the frame, but not the whole project in HD. I traced the frame and eventually bladed it off and everything went fine. But the fail was not randomly distributed along the timeline, and referred to the very same frame all of the times.

Fabrizio D’Agnano
Rome, Italy
early 2008 MacPro, BM Intensity Pro, early 2008 iMac, 2011 MacBook Pro, FCP7, FCPX, OSX 10.8.3

[Dave Jenkins]

Are you on FCP 10.0.9? That corrected the problem for me but I was doing an HD project not 4K.

Dajen Productions, Santa Barbara, CA
MacPro 3.2GHz Quad Core – AJA Kona LHe+
FCS 3 OS X 10.7.4
FCP X, Logic Pro, Squeeze, Filemaker 10.8.3

[Richard Hall]

Hi Dave
Yep on 10.0.9 but as mentioned the error happens in the rendered 1080P timeline as well – very frustrating!

Today only your imagination is the limitation.

[Dave Jenkins]

Are you using variable speed at the frame that is having the error? I had to change from variable speed to constant speed and also sometimes change the constant speed by a small percentage. Deleted all the render files and exported the sequence unrendered. Sounds like you may have tried all this.

Dajen Productions, Santa Barbara, CA
MacPro 3.2GHz Quad Core – AJA Kona LHe+
FCS 3 OS X 10.7.4
FCP X, Logic Pro, Squeeze, Filemaker 10.8.3

[John Fishback]

I’d run trusty ol’ Disk Warrior. If your directory is anyway corrupted FCP loses its way. Just today, after working fine for a long time, my FCPX started crashing (I know that’s not your issue). After DW all was well. Over the years DW has fixed many mysterious issues. It’s worth a try.

John

MacPro 8-core 2.8GHz, 16 GB RAM, OS 10.7.4, QT10.1, Kona 3, Dual Cinema 23, ATI Radeon HD 5870, 24″ TV-Logic Monitor, ATTO ExpressSAS R380 RAID Adapter, PDE enclosure with 8-drive 6TB RAID 5
FCS 3 (FCP 7.0.3, Motion 4.0.3, Comp 3.5.3, DVDSP 4.2.2, Color 1.5.3)
FCP-X 10.0.9, Motion 5.0.7, Compressor 4.0.7

Pro Tools HD 10 w SYNC IO & 192 Digital I/O, Yamaha DM1000, Millennia Media HV-3C, Neumann U87, Schoeps Mk41 mics, Genelec DSP Monitors, Prima CDQ120 ISDN

[Richard Hall]

Hi John
Only have an old version of DW but might invest and try that.. but thanks – you have given me an idea re disk permissions that i’ll try and run first with disk utilities – will let you know how I go..

Today only your imagination is the limitation.

[Richard Hall]

Thanks for all your help! Looking through your responses it became apparent it could be a drive issue.

As mentioned each time the project failed to export in a different place on the timeline and so it appeared to be random. But by taking a snapshot of the error report on every fail I eventually worked out using the frame counter that all of the frames were associated with two lengthy items of media in particular that was spread across the timeline – sooo not really random at all!

So I copied the media across to another raid drive, deleted the original and relinked – hey presto – job done!

I have done speed and performance tests on both sets of raid drives report to be working well, so its still a bit of mystery – but if you are having problems changing your media to another drive if you can is defo worth a go as is checking permissions etc.

Hope this helps someone in the future…

Today only your imagination is the limitation.

[Jeff Kirkland]

Just idle curiosity but I’m wondering if you tried deleting your render files when you had the error? My first thought was that you had a corrupt render file and the fix you describe would certainly have forced FCPX to regenerate the render files for everywhere that clip occurred…

Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland

[Richard Hall]

Hi Jeff

Yep, after looking at the forum that was one of the first thing I tried. I don’t think it was a dodgy render file because I had the same errors on both my 1080 and 4K timelines…

Today only your imagination is the limitation.

[Don Smith]

Haven’t had this problem in the latest release of FCP X but the way I used to cure that problem was to go to Preferences and change the timecode display to Frames. Back in the timeline go to the suspect frame and identify the suspect clip.

I then selected the clip, Shift-F to match itself in the Even Browser, then just dragged back down to replace itself in the timeline. Worked every time for me.

I suspect that I’m just forcing a new render file for the duration of that clip and that simply deleting all render files would do the same thing but I chose this way so I wouldn’t have to wait for the whole project to re-render. But, you could do either.

Don Smith – NewsVideo.com

NewsVideo.com