Forum Replies Created

  • Jenni Saaristo

    October 20, 2010 at 9:46 am in reply to: Compressor Problem: QuickTime Error: -50

    I see this is an awfully old thread, but it seems the problem still persists.

    I’m exporting 30 min offlines for remote viewing, using reference Quicktimes and Compressor to create H.264 -files. This has worked perfectly for three episodes.

    The fourth one would end time and again with “Quicktime Error: -50”.

    After strenuous troubleshooting I pinpointed the problem to be caused by certain text elements on the timeline, created with FCP’s own text tool. Funnily enough, not all text clips were problematic! Some of them went through with zero errors.

    I can’t even begin to guess what this is all about. But testing the timeline and having some luck saved my day this time.

    FCP 7.0.2 / Compressor 3.5.2 / Mac OS 10.6.3

    Jenni Saaristo
    freelance editor / Helsinki, Finland

  • Jenni Saaristo

    April 6, 2010 at 8:05 am in reply to: SOS multiclip bug or fatal mistake made

    Hello,

    I have a slightly different problem with unstable multiclips, It would be great to know if it’s a known bug and not something I’m doing wrong.

    We have two angles of video (ProRes Proxy), which we sync in a 3rd party software (Sync-N-Link) with our production audio (WAV). After that we pair them into multiclips manually (by inpoints) in FCP.

    Lately we’ve begun to see a problem with matchframing: Matchframing from the timeline results in the right angle, but the audio sync is way off.

    Could this also be a question of how FCP treats Audio TC?

    The mind boggling thing is, that this only happens in about 1/3rd of the material. Also, everything has been pretty much fine for three weeks, up till last friday. We’re copypasting multiclips and their masterclips from our assistant projects to the editors project, and the affected clips in the two projects aren’t necessarily the same – the editors copy is sometimes better.

    We’re running FCP 7.0.1 with Mac OS 10.6.2. I’ve trashed the preferences and emptied caches.

    Jenni Saaristo
    freelance editor / Helsinki, Finland

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