Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy HDMI capture in FCP

  • HDMI capture in FCP

    Posted by John Mckinney on May 29, 2007 at 6:37 pm

    In FCP with new Sony HDV deck using HDMI cable to my Mac.

    I selected Blackmagic Intensity as my capture preset.

    I can “capture now” but how do I get FCP to recognize this deck (Sony HVR-M25) as a controllable device?

    Jonathan Miller replied 18 years, 11 months ago 5 Members · 8 Replies
  • 8 Replies
  • Jeff Carpenter

    May 29, 2007 at 7:25 pm

    I know very little about this subject, but I THINK that you use firewire to control the deck. So the HDMI does all the A/V stuff while the FW does the controlling.

  • Jeremy Garchow

    May 29, 2007 at 8:47 pm

    [Jeff Carpenter] “but I THINK that you use firewire to control the deck”

    Yes, and you have set the deck for dv downconvert and then set FCP to DV device control. HDMI should still be HD output.

    Jeremy

  • Jonathan Miller

    May 29, 2007 at 9:13 pm

    This same configuration works for capturing video through an Analog to HD-SDI box. Just FYI.

    Like you said, you’re just using the “HDV->DV” downconverting for deck control. The video outputs should remain untouched.

    Jon

    TreeLine Productions
    Fort Collins, CO USA

    Currently producing these popular podcasts:

  • John Mckinney

    May 29, 2007 at 9:16 pm

    That worked. Thank you all.

    John McKinney

  • Chris Poisson

    May 30, 2007 at 2:43 pm

    Jonathon,

    Could I trouble you for a more in-depth explanation of this? Yesterday I was trying to capture from a Z1 using component, running FCP Studio 2 on a G5 dual 2 gig, with a Kona LH.

    Using the component out from the camera, please explain the settings including deck (camcorder) control, and what capture settings for a DVCproHD 1080i capture, and what happens with audio in a scenario like this?

    BTW this was a rented camera, I have a Canon A1 on order, would settings be much different on that camera?

  • Jonathan Miller

    May 30, 2007 at 3:24 pm

    Sorry, Chris–I’ve never used one of the Canons. If it can downconvert over FireWire, then it should be a similar setup.

    In your camera, navigate to the in/out menu and roll down to “i.Iink conversion”. Choose “on”.

    Now, in the same menu, choose “Component” and make sure that it’s set to “1080i/480i”.

    OK, so now you’ve got regular old DV being output through the FireWire jack, and 1080i video being output through the component break-out cable.

    Plug the camera into a FireWire port on the G5, and the component video cable to the Kona (love those RCA to BNC adapters!)

    IN FCP open the capture window. Click on the Capture Settings tab and you’ll have two drop-down menus. For Device Control, choose “FireWire NTSC”. For Capture/Input, choose whatever your capture card is and the format you want to capture to. There should be a preset for DVCPROHD 1080i60 or similar with the Kona.

    Now, you will also have to feed audio to the Kona card from the camera in order to capture sound.

    Once this is all connected and set up, FCP will control the camera just like you were capturing DV. But you won’t be capturing DV, you’ll be capturing DVCPROHD and the TC will carry over from the camera to the QT files perfectly.

    I hope that helps.

    Jon

    TreeLine Productions
    Fort Collins, CO USA

    Currently producing these popular podcasts:

  • Chris Poisson

    May 30, 2007 at 6:14 pm

    Jon,

    Wow, that’s just superb, giving me all this detail. Thanks you so much! My camera is arriving today sometime soon, can’t wait to try all this.

  • Jonathan Miller

    May 30, 2007 at 6:16 pm

    Yeah, all of my desription is for the Z1U/FX-1 form Sony. Sure Hope your new Canon can do the same!

    Jon

    TreeLine Productions
    Fort Collins, CO USA

    Currently producing these popular podcasts:

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