Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums AJA Video Systems LHe – 1080psf23.98 to NTSC

  • LHe – 1080psf23.98 to NTSC

    Posted by David Jahns on May 16, 2007 at 10:08 pm

    is the LHe not able to downconvert from 1080psf23.98 to 525i29.97?

    Am I hallucinating? Is the KONA LHe not able to downconvert & add pulldown?
    I am 99% certain that I have made NTSC DigiBetas from a 1080-23.98 timeline
    in the past. No?

    The CODEC tab has 24-30 fps conversion settings – do they not work with the
    LHe?

    I’ve tried Kona Drivers 3.3 and just tried 3.4 as well.

    Jeremy Garchow replied 19 years ago 3 Members · 8 Replies
  • 8 Replies
  • Jeremy Garchow

    May 17, 2007 at 1:58 am

    Right click on your SDI output on the Kona control panel and choose secondary from the drop down menu, then right click again and choose 525i.

    Jeremy

  • Gary Adcock

    May 17, 2007 at 12:31 pm

    [David Jahns] “is the LHe not able to downconvert from 1080psf23.98 to 525i29.97?”

    YES is does, in real time

    “I’ve tried Kona Drivers 3.3 and just tried 3.4 as well.”

    Follow Jeremy’s advice, you have not set the Kona Control to downconvert, this cannot be done in FCP it has to be done in the Control Panel.

    gary adcock
    Studio37
    HD & Film Consultation
    Post and Production Workflows

  • David Jahns

    May 17, 2007 at 3:37 pm

    Thanks, guys – good to know that SHOULD work and I’m not crazy. I’ve been using the LHe for over a year – and I know the control panel interface. I have tried the normal methods of doing this. The problem is that when I try to choose 525i – it is grayed out.

    When I choose Primary 1080i29.97 – I can downconvert just fine. When I switch back to 23.98 – my secondary format of 525i turns gray (red on the SDI Output graphic).

    AJA Support just wrote me back that “The KLHe can’t do the cross convert, the K3 will do 1080sf 23.98 to 525i29.97.”

    That is flat-out wrong – I’ve done this in the past – and both you guys have confirmed it, right?

  • Jeremy Garchow

    May 17, 2007 at 4:15 pm

    Try going in to the formats tab and change the secondary format to 525i, forget the control click on the little triangles. Change the secondary to 525i then change the appropriate output (SDI or analog) to secondary and then go back to FCP and see if that works. It should.

    Does that make sense?

    Jeremy

  • David Jahns

    May 17, 2007 at 6:29 pm

    thanks for your help Jeremy.

    The problem is that my 525i is grayed out in secondary format. See screenshot:

    https://homepage.mac.com/jahns/1080-24_2_NTSC.png

    525i is OK if I’m at 1080i, but as soon as I change Primary to 1080sf23.98, the only secondary format that isn’t grayed out is 1080sf23.98.

    I know I have done this before without any problems, but now AJA is telling me that the KONA 3 can do that, but not the LHe – which is b.s.

    Any suggestions?

  • Jeremy Garchow

    May 17, 2007 at 8:12 pm

    Go to View > Video Playback and change it to 1080i 29.97 (from 23.98), then change the secondary to 525i. That should do it.

    Jeremy

  • David Jahns

    May 17, 2007 at 8:24 pm

    Hmm… yes, that works – but it seems wrong to have my video output set to 1080i29.97 when I’m working at 1080sf23.98. I know I’ve done this before, and I don’t recall having to futz with the settings like that. I guess FCP is then feeding it the 2:3 pulldown?

    I wonder if the previous Easy Setups for 1080sf23.98 used Vid Playback at 1080i?

    Thanks for your help Jeremy.

  • Jeremy Garchow

    May 17, 2007 at 8:41 pm

    Here’s what happening, the KOna is adding 3:2 pulldown to your video to get it to 29.97 (that’s what the 3:2 pulldown prefs in the codec tab are for). Then from there it’s a simple down-convert since the pulldown has been added. FCP is not adding pulldown in this case. It should be all done in hardware with the Kona.

    Jeremy

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