Forum Replies Created

Page 1 of 2
  • Monica Nolan

    March 27, 2013 at 4:53 am in reply to: Codec could not be opened-avid clip

    Thanks for the quick response.

    I looked at the file in quicktime, did a restart, looked at it again in both QT and FCP. Still no picture. Now the QT info window says avid dv codec under format–I think when I initially looked at it, the format was still gobbledygook. Maybe I’ll try another restart and cross my fingers this time. I have QT 7.7–don’t know if this might make a difference.

  • Monica Nolan

    March 27, 2013 at 4:34 am in reply to: Codec could not be opened-avid clip

    Downloaded the codecs you linked to, but no change.

  • Monica Nolan

    January 20, 2013 at 7:33 pm in reply to: Processing raw video

    Brilliant! I downloaded the AJA mac QT codec v4.0 and was finally able to see an image. I’m converting the file to prores in Compressor and it seems to be working (although will probably take all day). Thanks so much!

  • Monica Nolan

    January 20, 2013 at 7:28 am in reply to: Processing raw video

    Thanks Neil & Rafael,

    The QT info window tells me the format is rgb 10-bit, 1920×1080, millions. It’s a pretty huge file. 106 gigs for 9:33. Definitely overkill.

    Neil, I’m confused. I thought 444 in this context referred to the colorspace sampling, not a specific codec? My understanding of a raw video file was that it is codec-free; just the sampling data. In any case, I’ll try it on FCP 7’s compressor on a friend’s system and see what happens.

  • Monica Nolan

    December 11, 2011 at 8:20 pm in reply to: Getting the ProRes Codec

    This didn’t work for me. I keep getting the “codec not found” error message. I’m on OS 10.5.8, FCP 6.0.6.

    Is it possible I’m putting the .component files in the wrong folder? I put them in, library>quicktime, and when that didn’t work I tried putting them in system>library>quicktime.

    Any other ideas?

    Thanks

  • This post was super-helpful to find. However, although I was able to finally get past the error messages and import the xml file, I seem to have only got part of it, one folder of master clips. When I look at the doc in text edit, I can search and find the names of the missing clips. Any thoughts as to why I’m not getting them?

    Thanks.

  • Monica Nolan

    May 5, 2011 at 5:43 am in reply to: Fuzzy HD from Canon or transcoding?

    Still doesn’t explain why the source file would look fuzzy when I opened it on my desktop in quicktime.

    a camera guy said something about Canon + motion + greenscreen having an issue but didn’t elaborate. Anything to that?

  • Monica Nolan

    May 4, 2011 at 10:24 pm in reply to: Animating separate shapes on a single layer

    Thanks much, that was it. I was assuming the diamond shaped keyframes meant I was in linear land, but I was only there temporally and not spatially.

  • Monica Nolan

    May 4, 2011 at 12:43 am in reply to: Fuzzy HD from Canon or transcoding?

    Okay, I’m officially obsessed.

    When I look at the source files (before any transcoding). I can stop on a frame and see that it looks blurry. The placket of the guy’s shirt is sharp in one frame, fuzzy when he moves.

    When I look at the FCP transcoded clip in the viewer, same thing. This is not a playback issue–I’m looking at the still frame. At this point, wouldn’t I see what I’m getting?

    Another, separate puzzling thing: I set the log & transfer preferences pulldown to Canon>Eos as source, transcode to ProRes 422 (I’ve tried both HQ and regular), yet everytime I reopen that window, it’s defaulted back to the top choice (AVCHD). That seems odd to me. Generally when you set a preference it sticks. And the window has been open all the time.

    Thanks for any thoughts…

  • Monica Nolan

    May 3, 2011 at 10:42 pm in reply to: Fuzzy HD from Canon or transcoding?

    Another thought: shouldn’t the file look okay if I open it as a quicktime movie on my desktop? (i.e. not within fcp)

Page 1 of 2

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