Forum Replies Created

  • I’ve been having the same issue today after capturing 1080i60 with a Sony HVR-Z1U.

    None of these suggestions worked, and I’ve checked and re-checked.

    Trying to import into a Mac Pro 2 GHz, dual core intel xeon running FCP 6, Mac OSX 10.4.11. I finally gave up trying to capture HD and switched the iLink on and set my FCP capture settings to Firewire DV NTSC 48 kHz Anamorphic, sequence to DV NTSC 48 kHz and Device control to FireWire NTSC, because I have to use the video tomorrow at a press conference.

  • Beth Goins

    January 1, 2009 at 2:15 pm in reply to: Skipping after export from FCP to Quicktime

    Happy New Year, and thanks for responding. Sorry for the scant info earlier. I will have to power up the iMac and let you know the settings, since I changed them a few times yesterday, but in the meantime, I seemed to have found a solution. Via the Final Cut Movie option, I exported out of Final Cut using what seemed to me an odd combination of HDV and DV settings (will get those and post them here later today). It looked great, with no skipping, but for the final destination, the web, it wouldn’t work, because using that option it will only play within the Final Cut project. So I created a new project, imported the Quicktime file back in, changing the sequence settings to match, then exported out using Quicktime Conversion using custom settings, at a frame rate of 24 since the lower frame rates didn’t work (again, will post all the settings here later). The final product is compact, crisp, and smooth. The only thing I’m not happy with is the audio–it sounds rather tinny to me. I’ll probably go in and tweak it later today, then will go into the settings and put them here.

    I think the issues were a few things–I probably had the wrong settings on capture, but the only setting in which the camera would recognize the Canon camera was the HD setting. Weird. I usually use a Sony and have no problem. Then, the project settings were probably off–I had it set for HD to match the capture settings, and it was probably too much for the processor, although I thought the iMac had plenty of muscle going into this. The third issue was the export settings. Somehow all these things created the perfect storm that screwed up the video. Fixing one at a time didn’t work, but fixing two of the three together did the trick.

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