Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Kona LH and Drop Frame

  • Kona LH and Drop Frame

    Posted by Buck Miller on January 26, 2007 at 4:17 am

    I am trying to import some Beta SP footage through my Kona LH that was recorded as drop frame. When I try to capture the footage, it “kicks out” about a minute into the capture whether I am batching or capturing “now”. I spoke with AJA, they said they thought it was an Apple/FCP setting, but in the capture settings box, the drop/non-drop choice is greyed out, and therefore, cannot be chosen. I had no problem capturing non-drop footage. Any ideas? Thanks!

    Buck Miller replied 19 years, 3 months ago 4 Members · 7 Replies
  • 7 Replies
  • Shane Ross

    January 26, 2007 at 4:35 am

    What Easy Setup, or capture settings, are you using?

    Shane

    Shane

    Littlefrog Post
    http://www.lfhd.net

  • Jeremy Garchow

    January 26, 2007 at 5:03 am

    …and how fast are your drives that you are capturing to?

  • Buck Miller

    January 26, 2007 at 5:45 am

    Thanks guys.
    Jeremy, I am using the Xserve RAID drives.

    Shane, in the “Capture Presets” tab of the “Audio/Video Settings”:

    The Preset is: AJA Kona LH: 525 29.97 10 Bit

    When I click on Edit:
    Frame Size: 720 x 486 CCIR 601 NTSC (40:27)

    QuickTime Video Settings:
    Digitizer: AJA Kona 10-bit Digitizer
    Input: 525i29.97 (720×486)
    Compressor: Uncompressed 10-bit 4:2:2
    Quality: 100%
    FPS: 29.97

    Quicktime Audio Settings:
    Device: AJA Kona
    Input: (grayed out)
    Format: 48.000 kHz 24-bit 8-chan

    Capture Card Supports Simultaneous Play Through and Capture IS checked
    Remove Advanced Pulldown and/or Duplicate Frames from FireWire sources IS NOT checked
    Hight-Quality Video Play Through IS checked

    Under the “Device Control Presets” tab (I use a Sony 1800):

    The Preset is AJA Kona LH NTSC Sony VTR

    When I click on Edit:

    Protocol: Sony RS0422
    Audio Mapping: 2 channels
    Time Source: LTC+VITC
    Port: Kona Serial
    Frame Rate: 29,97
    Default Timecode: THIS IS GRAYED OUT!

    Use Deck Search Mechanism IS checked

    Capture Offset: -2
    Handle Size: 00:00:00;00
    Playback Offset: 00:00;00

    Hope this helps. Thanks!

  • David Roth weiss

    January 26, 2007 at 6:30 pm

    Are you trying to capture from the very head of the reel or from the very beginning of a camera start?

    The only time I ever see any drop frame/non-drop issues is when not allowing the deck enough preroll time to accurately set the proper timecode flavor. This can apply to either a logged entry or with record now.

    DRW

  • Buck Miller

    January 26, 2007 at 6:44 pm

    Thanks David. No, I am not trying to start at the beginning of the tape. It is really about in the middle. I can capture a minute at a time, and edit that together, but as you can imagine, that will take some time with three 30 minute tapes to do. I am not SURE that drop frame is the issue, I just assume it is because all other tapes have been non-drop and I have been able to capture them fine.

    Buck

  • David Roth weiss

    January 26, 2007 at 6:55 pm

    [bucksbucks] “I am not SURE that drop frame is the issue, I just assume it is because all other tapes have been non-drop and I have been able to capture them fine.”

    Drop/non-drop is pretty much a non-issue. I would instead consider one of three things as a more likely candidate:

    1) corrupt timecode on the tape – in this case dub to another tape

    2) trash prefs and try again – prefs got corrupted in between tapes

    3) project developed corruption – try capturing the offending tape to a new project

    Hope this helps…

    DRW

  • Buck Miller

    January 26, 2007 at 7:24 pm

    It will be tonight, but I will try all of these things. Great ideas. I will let you know if any of these work. Thanks again.

    Buck

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