Getting error message "The share operation master file has failed" error occurred when creating farme ..... (error -1). Any idea why this happened? Using Apple pro res 422 format.

Question

Level 1

0 points

Getting error message "The share operation master file has failed" error occurred when creating farme ..... (error -1). Any idea why this happened? Using Apple pro res 422 format.

I am trying to share my film to put on idvd. I used the Apple Pro Res 422 setting before and it worked fine. This time I am getting the error message "The share operation master file has failed." an error occurred when creating frame ..... (error -1). Is this a bug? I am currently using the setting Apple Pro Res 422 LT, but it is taking forever to finish. Any idea of what is causing this problem?

Final Cut Pro X, OS X Mountain Lion (10.8.3)

Posted on Apr 7, 2013 5:48 PM

Reply

Answer 1

Best reply

Russ H

Level 7

22,432 points

Apr 7, 2013 5:52 PM in response to joslech1216

joslech1216 wrote:

I used the Apple Pro Res 422 setting before and it worked fine.

What changes have you made to your system since the time went it worked fine?

Have you tried any other projects to see whether it works with them?

Russ

Reply

Answer 2

joslech1216 Author

Level 1

0 points

Apr 7, 2013 5:55 PM in response to Russ H

It worked fine with a large movie file created last Friday. I started a new project two days later about the same size and almost identica in format, but this time I got the error message. I'm not sure when the new update to final cut X came. I might have updated between these two projects. That is the only thing I can see as different.

It appears to be working on the setting Pro Res 422 LT, but it is taking a very long time.

Thanks.

Joe

Reply

Answer 3

Russ H

Level 7

22,432 points

Apr 7, 2013 6:01 PM in response to joslech1216

I'm curious whether it's project-specific or whether your export is just broken. Create a short test project and drag a few clips from a different event . Export and see whether you get the error.

Russ

Reply

Answer 4

joslech1216 Author

Level 1

0 points

Apr 7, 2013 6:08 PM in response to Russ H

I will try this. Thanks. I will have to wait to see if current sharing works.

Joe

Reply

Answer 5

Russ H

Level 7

22,432 points

Apr 7, 2013 6:30 PM in response to joslech1216

And just to acknowledge that there clearly have been quite a number of export difficulties reported after the 10.0.8 update. So far I haven't seen a pattern to these reports and I have not been able to reproduce them. And wondering whether length is a factor.

How long is your project?

Russ

Reply

Answer 6

joslech1216 Author

Level 1

0 points

Apr 7, 2013 6:32 PM in response to Russ H

one hour and fity two minutes. This is the same length of my earlier movies which worked fine. I used a canon vixia hf g10 comera when video taping. The approximate length is around 44 gigs with the pro res 422 setting.

Thanks.

Joe

Reply

Answer 7

Apr 8, 2013 1:07 AM in response to Russ H

Hi Russ,

I am getting the same error while testing 1 minute and a half compound clip. So, I don't think length is a factor. As a newbie question - do you have any idea if Apple are going to address this?

Thank

Tory

Reply

Answer 8

Apr 8, 2013 2:25 AM in response to joslech1216

Hello,

Please help me. I am having exactly the same problem with any type of share process. My source video files are mp4 1024 × 576 and whatever output settings I select I am getting this error message as soon as I start the share process.

I am an audio producer who is dipping his toe into the world of video editing, so please if anyone can help, I'll be the first to admit it's something I've done wrong, I just want to know how to put it right!

Many thanks,

Alan

Reply

Answer 9

Russ H

Level 7

22,432 points

Apr 8, 2013 5:23 AM in response to joslech1216

None of my exports – post update– have been any longer than 20 minutes.

Let us know whether your short test export works.

Russ

Reply

Answer 10

Russ H

Level 7

22,432 points

Apr 8, 2013 5:29 AM in response to Tory Dunn

Tory Dunn wrote:

As a newbie question - do you have any idea if Apple are going to address this?

Sorry. We're all users here and Apple typically doesn't let us know about their plans for anything.

But if it is a bug, no doubt they'll address it whenever.

Russ

Reply

Answer 11

Russ H

Level 7

22,432 points

Apr 8, 2013 5:37 AM in response to Alan Hyde

FCPX maynot be happy with your MP4 source files. Try MPEG STreamclip or Compressor toconvert to a Quick Time.

Russ

Reply

Answer 12

Apr 8, 2013 8:52 AM in response to Russ H

Thanks, Russ. I ended up taking out a transition, and that seems to have helped.

Reply

Answer 13

Apr 8, 2013 11:55 AM in response to Russ H

Russ - thank you for your words of wisdom. I decided to do the whole edit again, but without cutting corners, so converted all the source files to full HD mov files, and it worked perfectly. A lesson learnt for me, and my gratfeul thanks to you!

Al 🙂

Reply

Answer 14

joslech1216 Author

Level 1

0 points

Apr 8, 2013 3:28 PM in response to Russ H

I fixed the problem. I followed a suggestion to change the timeline to frames rather than time and discovered that the frame that could not be written was one area of my project. When I scrubbed through it I noticed that the image flickered from image to black. When left stationary the black would become an image. This did not happen in any other part of my project. When I deleted this segment and replaced it with the same favorite, it still did the same thing. I recontructed the favorite clip and it still did the same thing. I copied the entire project and created a new project. I pasted the copy into the new project and the problem did not re-occur. I shared the project with pro res 422 without waiting to have the project rendered. It took a bit longer, but the project turned out fine.

I don't know if the rendering caused the bad segment or just a bad import. The funny thing was that when I copied and pasted the same project into a new created project --it worked fine.

Thank you for your help.

Joe

Reply

Answer 15

joslech1216 Author

Level 1

0 points

Apr 8, 2013 3:30 PM in response to Alan Hyde

I fixed the problem. I followed a suggestion to change the timeline to frames rather than time and discovered that the frame that could not be written was one area of my project. When I scrubbed through it I noticed that the image flickered from image to black. When left stationary the black would become an image. This did not happen in any other part of my project. When I deleted this segment and replaced it with the same favorite, it still did the same thing. I recontructed the favorite clip and it still did the same thing. I copied the entire project and created a new project. I pasted the copy into the new project and the problem did not re-occur. I shared the project with pro res 422 without waiting to have the project rendered. It took a bit longer, but the project turned out fine.

I don't know if the rendering caused the bad segment or just a bad import. The funny thing was that when I copied and pasted the same project into a new created project --it worked fine.

Reply