Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Export to Vimeo hangs on Share Monitor

  • Export to Vimeo hangs on Share Monitor

    Posted by Michael Garber on August 4, 2012 at 6:15 pm

    Hi all,

    I know there are sometimes issues with sharing out of FCPX to Vimeo/Youtube/etc… Intermittently and depending on the project and whether or not I’m using proxy media, the transcode for Vimeo or Youtube will hang. The progress bar sticks at probably about 1/8 of the way through. The time to completion just increases.

    The project I’m working with is at 720p60 and contains a mix of 1080psf23.98 footage and 720p60. Every clip has been rendered. This works fine when I’m in proxy mode, but hangs when set to original media. Since the project is complete, I want to make the encode from the original media.

    I ran Digital Rebellion’s compressor cleaner. It didn’t work. Just ended up putting it through Adobe Media Encoder which worked great – and in 10 minutes! (Have I mentioned how much I love AME? Oh, I have already? How redundant of me. Whoops!)

    The issue I’m running into is on a Macbook Pro 13″. I have run the same media off the same drive on a Mac Pro and the encode works fine along with the upload.

    Any help would be greatly appreciated. Thanks.

    Michael Garber
    5th Wall – a post production company

    Bill Davis replied 14 years, 1 month ago 2 Members · 3 Replies
  • 3 Replies
  • Bill Davis

    August 5, 2012 at 7:31 pm

    [Michael Garber] “The issue I’m running into is on a Macbook Pro 13”. I have run the same media off the same drive on a Mac Pro and the encode works fine along with the upload.

    Any help would be greatly appreciated. Thanks.

    Michael,

    One thing I’ve noticed with X is how it’s really easy to create something simple on the timeline that has an unexpectedly HUGE render penalty on output.

    Aligned stacked dissolves on stacked titles is one area where I saw this a lot.

    So I”m wondering if you look closely at the part of your project where this massive “bog down” is taking place – ithere might be a reason you’re inadvertently ratcheting up the processing load – something that your MacPro might be able to chew through, but that brings the MacBook to what seems to be a total stop?

    There are threads here about how to use clip compounding to tell X to consider composites as a single clip, rather than a stack of discrete elements that necessitate the software calculating the pixel values of each against all the others seemingly endlessly.

    I don’t understand this fully, just know that I earlier on when I was constructing my X timelines like I’d constructed my Legacy timeline I often had projects get “hung up” on export – but after I changed to judiciously using compounds when they’re appropriate, I seldom have same problems any more.

    Good luck. And let us know how things work out.

    “Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor

  • Michael Garber

    August 6, 2012 at 9:04 pm

    Hi Bill,

    Thanks for the input. I tried making a compound clip out of the entire timeline. That didn’t work. Then I added a broadcast safe to the compound clip so that it gave FCPX something to render to a new file. That didn’t work, either. As I mentioned, it renders out just fine on my Mac Pro. So, I really think it’s isolated to some issue on my system (what that is, I haven’t a clue).

    Also, the timeline is pretty basic. It is just under 4 minutes. There are some titles and there are some stacked dissolves at the end of the timeline, but only 2 layers worth. So if there was a slowdown you’d think the progress bar would go further before stalling.

    I haven’t tried new footage yet. But I will later on. I have been teetering on reinstalling the OS on the laptop just to see if it improves general performance and not necessarily to fix this problem. So might do that sometime next week and hopefully it will be a nice side effect of a fresh install.

    Will try out some new footage later to see if that does anything. It’s just getting stuck. The time keeps increasing. Adobe Media Encoder takes 8-12 minutes to render at the same settings.

    Michael Garber
    5th Wall – a post production company

  • Bill Davis

    August 7, 2012 at 12:46 am

    Understood.

    If you figure out what’s causing your slowdown, please come back and let us know.

    I’d be interested and I know a lot of others will as well.

    Take care.

    “Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor

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