Forum Replies Created

Page 8 of 33
  • Neil Ryan

    November 16, 2011 at 4:06 am in reply to: Can’t open a quicktime file from FC on a PC.

    Adam,
    Is this the error you got?:
    “error 2048 could not open filename.mov because it is not a file quicktime understands”

    If so, then I suspect that, from what I’ve read elsewhere, you have a file issue. And not a codec (ProRes) issue. Some suggest the -2048 error is a Registry error. “Most of the time, error 2048 is caused because of a corrupt Windows registry.” I read elsewhere.

    If it was a codec issue, you would normally be able to open the file in QuickTime, but not see the vision; just a grey screen or only the timeline, like it is an audio-only file.

    Neil.

  • Neil Ryan

    October 31, 2011 at 3:34 am in reply to: Strange text and dissolve issues

    … then you should post the fix…

  • Neil Ryan

    October 26, 2011 at 5:23 am in reply to: Black outline on unmatted clips in Final Cut Pro 7

    I have seen something similar to what you describe, in my work. But the outline disappears once the clip is rendered.
    What happens once you render your clip?

    Neil.

    – – – – – – – – –
    Neil Ryan
    Post Production Protagonist

    – – – – – – – – –

  • Neil Ryan

    September 22, 2011 at 2:16 am in reply to: Final Cut Pro X – The New Manual

    The optimist in me suggests they cleaned up 79 pages of known bugs…

  • Neil Ryan

    September 22, 2011 at 2:12 am in reply to: Thanks Apple!

    Was this FCP X or 7?

  • I think that Bret has got it!

  • The way I read the problem, Dupe Detection was not the solution.
    [Caitlin miller] “…Is there a way to find out if your source clips have been used in a sequence yet?” and “…but we’ve already prepped almost 100 scenes. Going clip by clip to make sure everything has been used will be too time consuming.”
    So I read this as Caitlin wanting to find out out if she can tell in the Bins, which clips have been used. She doesn’t want to have to place them in a Sequence and use Dupe Detection, as there are that would be “… too time consuming.” Which I can understand.
    Interesting that different people perceive the problem differently. (And it’s not for me to say who is correct.)

    Cheers,
    Neil.

  • Have you turned everything on in Render All? If not, try & see if that improves it.
    You said “seems”. Maybe lay that section to tape & capture it back in, sync it with the original timeline & see what is REALLY happening.
    Curious.

    Neil.

  • Several things:
    1. I can’t thing of a solution to your problem.
    2. This is one of those things Avid got right, right from the beginning. Your problem highlights the need for a User to be able to access this kind of information. (And none of that is meant to inflame anyone.)
    3. DVD Studio Pro has a column in the assets window (read Bin) called ‘In Use’. Something similar in ye olde FCP would have been good.

    Neil.

    – – – – – – – – –
    Neil Ryan
    Post Production Protagonist

    – – – – – – – – –

  • Neil Ryan

    September 12, 2011 at 4:38 am in reply to: Widescreen and Motion Problem

    Whilst you got around it this time, it would pay for you to understand the original problem, as you’re bound to come across it again.
    The issue you had stems from the order in which FCP process. Effects come after Motion Tab.

    From the online help: (When it says ‘rendered’ read ‘processed’ for a better understanding)
    Order of Effects Rendering
    When you render effects in a sequence, they’re rendered in the following order:

    The top video track (the highest-numbered track) is rendered first and then composited onto the track below.

    Within each track, effects are rendered as follows: speed, filters, motion, motion blur, opacity, and transitions.

    You can change the order of rendering by using nested sequences. For more information, see Sequence-to-Sequence Editing.

    This is why you should take note of Kent’s workaround.

    Neil.

Page 8 of 33

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