Jean Bovet

Q: Final Cut Pro X share fails with QuickTime Error -50

Hello!

 

I'm facing a very annoying issue when trying to share my project from Final Cut Pro X. It used to work perfectly fine but now I'm getting consistently "QuickTime Error -50" after FCPX exported about 10% of my project. This can be reproduced with other project as well - one time I was able to export by restarting my machine but not anymore.

 

My configuration is a Mac Pro early 2008 with a ATI Radeon 5770. The only recent change I did to my config was to upgrade my old graphic cards to the Radeon 5770: do you think this can be the cause of this error?

 

Thanks for any help,

 

Jean

Mac Pro, OS X Mountain Lion (10.8.3), Radeon HD 5770

Posted on Jun 2, 2013 9:32 AM

Close

Q: Final Cut Pro X share fails with QuickTime Error -50

  • All replies
  • Helpful answers

first Previous Page 3 of 3
  • by Cédric74,

    Cédric74 Cédric74 Jan 6, 2014 1:39 PM in response to Jean Bovet
    Level 1 (0 points)
    Jan 6, 2014 1:39 PM in response to Jean Bovet

    Thank you @ Hellocheryl, it worked perfectly for me.

  • by joshWL,

    joshWL joshWL Jan 19, 2014 8:11 AM in response to Cédric74
    Level 1 (0 points)
    Jan 19, 2014 8:11 AM in response to Cédric74

    Hey guys, I am having the same problem. I am running mavericks, but have not upgraded FCP to 10.1 on this particular machine, still using 10.0.8. I've tried all the suggestions listed here but still getting the same error -50.

  • by Russ H,

    Russ H Russ H Jan 19, 2014 8:55 AM in response to joshWL
    Level 7 (21,770 points)
    Quicktime
    Jan 19, 2014 8:55 AM in response to joshWL

    As I recall, 10.0.8 had the most reports of failed exports of any version. 10.0.9 fixed a lot of those issues but it's too late to update; now you would be limited to 10.1. If you're in the midst of an important project, you might understandably choose not to update.

     

    Since you're running Mavericks, one of the first things to check is whether the error is caused by App Nap. Checking Prevent App Nap for FCP.app may be all that is needed.

     

    In 10.0.8, many of the problems were caused by a tendency for render files to become corrupted. So lots of advice was given on deleting project and event renders and exporting unrendered projects. Other times, however, the export fails were caused by problem media and could be fixed by replacing a bad clip. If the error provided a frame number, replace the clip at that location.

     

    Russ

  • by Nejigs,

    Nejigs Nejigs Feb 10, 2014 7:14 AM in response to Jean Bovet
    Level 1 (0 points)
    Feb 10, 2014 7:14 AM in response to Jean Bovet

    Hello everybody,

     

    today I had a similar problem. But I got it occuring at several different % of the export procedure.

    I tried everything (even changed the RAM).

     

    I found a dirty solution that worked for me, not sure everybody finds it helpful, but I write down

    what I did in case somebody desparate will get helped by it...

     

    1. I did a manual render all at my project.

    2. I did a partial export of the 2nd part of the project's timeline.

    3. I did a partial export of the 1st part of the project's timeline.

    4. I did a complete export and voila!! It majestically worked!

     

    Don't know why it worked, but it saved my life today!

     

    Hope it helps!

  • by nilimamoo,

    nilimamoo nilimamoo Feb 16, 2014 3:33 PM in response to Jean Bovet
    Level 1 (0 points)
    Feb 16, 2014 3:33 PM in response to Jean Bovet

    I was having the same problem and I tried a lot of the suggestions here and nothing worked. Then I simply created a new project in FCPX and copied and pasted the one that wasn't exporting -- this seemed to solve the problem. Is there a downside to this approach? I've deleted the original project but haven't emptied the trash yet. Should i be concerned the something at a deeper level corrupted that original project or is this sort of thing 'normal'?

     

    thanks.

  • by Bradster90,

    Bradster90 Bradster90 Mar 10, 2014 9:25 AM in response to Jean Bovet
    Level 1 (0 points)
    Mar 10, 2014 9:25 AM in response to Jean Bovet

    Hellocheryl's solution worked find for me too! Thanks!

  • by smashtov,

    smashtov smashtov May 3, 2014 10:09 AM in response to hellocheryl
    Level 1 (0 points)
    iLife
    May 3, 2014 10:09 AM in response to hellocheryl

    Thanks hellocheryl! The AppNap did the trick for my case.

  • by marioi01,

    marioi01 marioi01 Jun 2, 2014 7:41 AM in response to Jean Bovet
    Level 1 (0 points)
    Jun 2, 2014 7:41 AM in response to Jean Bovet

    Thanks for the post.  I had the same problem and achieved a succesful share after 7 failed attempts by Duplicating the original project "as snapshot".  Did the share off of the snapshot duplicate and worked the first time.


    Thanks for posting....

  • by js_cdp,

    js_cdp js_cdp Feb 25, 2015 11:46 AM in response to Jean Bovet
    Level 1 (0 points)
    Feb 25, 2015 11:46 AM in response to Jean Bovet

    For any future readers getting a "Video rendering error: -50" - I found that within multiple projects of mine any clips where I used the retime menu to set a specific duration (Retime> Custom... > Set Speed: Duration) would cause this error on export. If I go in and set the timing to one percent faster or slower, it fixes the issue. If you want to keep the same percent, just change it to something else, then change it back, and it should be fixed. (It will not work if you simply type the same percent in and hit enter, it has to be changed to something else once first.)

  • by QSerious808,

    QSerious808 QSerious808 Mar 22, 2015 9:58 PM in response to Tom Wolsky
    Level 1 (0 points)
    Mar 22, 2015 9:58 PM in response to Tom Wolsky

    Tom Wolsky


    Thanks for the tip it worked great for me. Sorry everyone who is having bad luck with this issue.

  • by palmerijosh,

    palmerijosh palmerijosh Aug 27, 2016 10:15 PM in response to Tom Wolsky
    Level 1 (4 points)
    Aug 27, 2016 10:15 PM in response to Tom Wolsky

    Brilliant! Thank you Tom!

first Previous Page 3 of 3