Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Head scratcher: unable to export (share) a project

  • Head scratcher: unable to export (share) a project

    Posted by Jeff Markgraf on November 22, 2017 at 2:22 am

    Strange issue that came up today. Here’s the background:

    10 seats of FCPX 10.3.4 connected via 1GigE (through a switch) to a Jellyfish server. (3 seats directly connected at 10GigE.). Libraries live on the server in their own folder. Media on the sever in a different folder (with subfolders). Media is a mix of ProRes HD, XDCam 35, some 4k, etc.

    Everything working as expected until today. Suddenly 2 users were unable to export some of their sequences. Attempting to share with any preset resulted in nothing – no export dialogue at all. Command+E also did nothing. No sequences in the library would export.

    Sequences in a different library open on the same machine would export. Also, opening the sequences in the non-exporting library on another system worked fine.

    Two different users had this happen to them in one afternoon. Restarting FCP did not help. Restarting the Mac did not help. Will try restarting FCP and deleting preferences, but I’m not hopeful.

    I am at a loss to explain or fix this odd behavior.

    Anyone experience this before? Any thoughts?

    Sam Mestman replied 8 years, 5 months ago 2 Members · 3 Replies
  • 3 Replies
  • Sam Mestman

    November 22, 2017 at 4:21 am

    Hey Jeff!

    Put in a ticket when something like this happens (we’ll help you take care of this stuff and dive in deeper on the troubleshoot… and let me know if this has not already happened). That said, a couple things to try before going deeper:

    1. What happens when you place that same library local for a second and try to export?
    2. Does anything happen when you try to open the library from the backup or is it the same issue?
    3. What happens if you create a new library and copy the problem event/sequence into the new library?

    Seems like it could be a permissions issue… but definitely talk to support and we’ll get it figured out one way or another. Have a great Thanksgiving!

    Sam Mestman
    CEO – Lumaforge (www.lumaforge.com)
    Founder – We Make Movies (www.wemakemovies.org)

  • Jeff Markgraf

    November 22, 2017 at 8:24 pm

    Hi Sam.

    I didn’t put in a support ticket with you guys because it didn’t seem like a Jellyfish problem. I could export his sequences just fine from my system. Same with the other user.

    Today one of the problem systems saw the problems disappear. Go figure!

    After Googling the issue, it seems bad renders and/or corrupt files may be at play. I’m going to keep an eye on this and I’ll submit a support ticket if it crops up again. Thanks for the quick response.

    Enjoy your turkey & trimmings.

  • Sam Mestman

    November 22, 2017 at 10:43 pm

    Hey Jeff,

    Either way… always put in a ticket because your support contract covers workflow as well, so even if it’s not a Jellyfish problem, we still help with things like this, so don’t ever hesitate to reach out. When you’re one of our customers and having a problem, it is our job to help you solve it. Bottom line.

    Also… you’re probably completely right. Deleting generated library files (all renders) can also be a great way to take care of problems like this.

    Have a great Thanksgiving!

    Sam Mestman
    CEO – Lumaforge (www.lumaforge.com)
    Founder – We Make Movies (www.wemakemovies.org)

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy