1 2 3 4 Previous Next 56 Replies Latest reply: Sep 19, 2013 3:34 AM by Martin S Taylor Go to original post
  • 45. Re: 4.0.3 bug?
    scubajwd Level 1 Level 1 (25 points)

    Martin...been almost a month..is there anything new with this issue?  Seems like

    the time required to export the ProRes file would completely defeat the purpose

    of setting up a cluster..transfers of frames to clients in a cluster should

    happen asyncrohonously with encoding methinks...hope this gets fixed with the

    ML upgrades later this month...

  • 46. Re: 4.0.3 bug?
    Martin S Taylor Level 1 Level 1 (20 points)

    Nope, nothing new. I'll post if there is, but for the moment all we can do is hope there's something in Mountain Lion which helps.

  • 47. Re: 4.0.3 bug?
    Lakesailracer Level 1 Level 1 (0 points)

    Martin S Taylor wrote:

     

    Nope, nothing new. I'll post if there is, but for the moment all we can do is hope there's something in Mountain Lion which helps.

    Has anyone come up with a solution to the problem of not being able to submit to QMaster/Compressor from Final Cut 10.x?  I just bought a new Mac Mini and loaded it up best I could for use with Final Cut, and was really excited about shortening the trancoding times using QMaster.  I fought the same problem found in this thread for a day and a half, along with someone else, and came up with zip for a solution until I read the discouraging news here. 

     

    I agree with scubajwd that there is hardly any point to re-transcoding with QMaster and Compressor if you have to render out the file from Final Cut first,  That's like trying to shorten the time it takes to run a marathon by first running it, then retracing the route in a car!  Plus it would seem that you would lose some quaity by transcoding the file twice, not to mention the needless extra time

     

    I hope someone has a better solution since Spring of last year.

  • 48. Re: 4.0.3 bug?
    Martin S Taylor Level 1 Level 1 (20 points)

    It's looking increasingly as though Apple have done it deliberately, though heaven only knows why.

  • 49. Re: 4.0.3 bug?
    Ken G. Level 1 Level 1 (5 points)

    Anyone have any luck with the new updates!?

  • 50. Re: 4.0.3 bug?
    Russ H Level 6 Level 6 (14,245 points)

    It's unchanged from the way it's functioned with FCP and Motion since several updates ago (since FCP 10.0.3?).

     

    And to the best of my recollection, there has never been any indication from Apple that it was anything other than a design decision.

     

    Russ

  • 51. Re: 4.0.3 bug?
    Ken G. Level 1 Level 1 (5 points)

    Crap, even with 10.0.8 that came out today?

  • 52. Re: 4.0.3 bug?
    Russ H Level 6 Level 6 (14,245 points)

    Yes. 10.0.8 and 4.0.7

     

    Russ

  • 53. Re: 4.0.3 bug?
    Ken G. Level 1 Level 1 (5 points)

    Alright thanks for the info, :(

  • 54. Re: 4.0.3 bug?
    A. Shupe Level 1 Level 1 (0 points)

    This No cluster support for fresh transcoding is entirely frustrating, I recently had someone come in with some extremely noisey footage for me to clean-up. Not a problem I'm thinking, we can do that pretty easy ... wrong even tho the noise is eliminated it takes extremely long to transcode since im stuck using only 1 processor instead of 8.

     

    like was posted before it doesnt help us to re transode with a cluster that doesnt improve render times at all so my question is why can't compressor or FCPX use all of the available system proccessing power?

     

    After buying this iMac last year i kinda feel a little ripped off, I feel as thought i bought a ferrari but all i can do is get the groceries If compressor and FCPx only use one processor i could get just as much work done on my Asus at less then half the cost.

     

    thankfully the latest patch fixed the bug in my noise reducer, now all i need is to be able to use more then one proccessor on the initial export.

  • 55. Re: 4.0.3 bug?
    eventservices Level 1 Level 1 (0 points)

    So after researching this problem, I find this:

     

    http://support.apple.com/kb/HT5333

     

    Which details the steps that meharkins described.  However, if Martin is correct:

     

    The problem is that you first have to export the file from FCP X. Since this involves writing an immense (50 Gb/h) ProRes 422 file, it can take a huge amount both of extra time and temporary disk space before you can set Compressor to do its job.

    Then this a serious issue.  Our University has tons (yes we measured the weight of the tapes...) of backlogged video to digitize and render.  We need something that provides a workflow with very few steps.  FCP+Compressor looked like the optimal solution, but suddenly we have to rethink what we are doing.

     

    myk

  • 56. Re: 4.0.3 bug?
    Martin S Taylor Level 1 Level 1 (20 points)

    So after researching this problem, I find this:

     

    http://support.apple.com/kb/HT5333

     

    Which details the steps that meharkins described.

     

    I think it's the very last line of this document which details the problem we've been discussing:

    Note: Share to This Computer Plus is no longer available as an advanced option from the Share pane in Final Cut Pro X 10.0.4 or later or Motion 5.0.3 or later.

     

    No indication as to why, just that it 'is no longer available'.

     

    MST

1 2 3 4 Previous Next