Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums AJA Video Systems AJA KONA 2 bug with COLOR

  • Jeremy Garchow

    May 24, 2007 at 8:00 pm

    I would think that would be normal. You can’t play out 23.98 material out of FCP if your output is set to 23.98 and your monitor doesn’t support 23.98 SD. But it will if you play 23.98 media out @ 29.97 adding the pulldown.

    I wouldn’t call this a bug, I’d call it an NTSC limitation.

    Jeremy

  • Bob Zelin

    May 24, 2007 at 9:04 pm

    ya see David – everyone yells at me for telling them to work at 59.94, but everyone says “nothing wrong with working at 23.98”.
    Jeremy is of course correct, just set to 29.97, but if you input your 23.98 material at 59.94 from your VTR, you dont’ even have to think about these settings.

    Bob Zelin

  • Jeremy Garchow

    May 24, 2007 at 9:33 pm

    Alright, here we go again. It’s a flip of a switch to do what David wants to do. If we had monitors that could support 23.98 SD, this wouldn’t even be a discussion. Who wants to add interlace to a 23.98 progressive image? Why capture pulldown when it will throw off the 3:2 cadence of the whole piece? Again, don’t blame David as it’s not his fault. People work @ 23.98. We deal with it. You know how we deal with it in this case? Flip the output to 29.97. Thanks to AJA it’s extremely simple and rather transparent.

  • David Battistella

    May 25, 2007 at 12:52 am

    Why does AJA have an NTSC 23.98 8 or ten bit choice then?

    Color recognizes it as 23.98 material.

    I see what you are saying. I have been shooting everything in anamorphic 24PA for a long time now. It’s not that big a deal as the KONA plays it out at 29.97 fine, BUT i get the advantages of sending the Progressive image to the DVD and also when encoding to WMV or .mov files. It;s not such a retarded way to work. IT also upconverts nicely to HD this way.

    David

    Peace and Love 🙂
    Read my Blog
    https://blogs.creativecow.net/DavidBattistella

  • Jeremy Garchow

    May 25, 2007 at 1:01 am

    [David Battistella] “Why does AJA have an NTSC 23.98 8 or ten bit choice then?”

    because AJA understands the needs for this option. It’s just like it has a 720p 23.98 uncompressed setting. Just like you said, we can get to 1080 23.98 psf this way. You can record to a device (such as another computer) that understands 23.98 sd, and then the obvious reasons you mentioned.

    But in order to monitor on a monitor that doesn’t understand 23.98, we must watch it wrapped in 29.97.

  • David Battistella

    May 25, 2007 at 1:58 am

    Thanks JG,

    Nice to see you here.

    david

    Peace and Love 🙂
    Read my Blog
    https://blogs.creativecow.net/DavidBattistella

  • Jeremy Garchow

    May 25, 2007 at 2:22 am

    Thanks, David!

    ? & ?

    Jeremy

  • Jeremy Garchow

    May 25, 2007 at 2:33 am

    [JeremyG] “? & ?”

    Hmm, I guess the cow doesn’t read keycaps.

  • Gary Adcock

    May 25, 2007 at 12:31 pm

    [David Battistella] “Just wanted to let you know that 23.98 DV material is not playing back properly through the K2 with the KONA 2 output set to 23.98 8 bit or 10 bit. “

    there is not any playback of 23.98 SD content in any way, shape or form.
    That setting is there to allow you to convert SD 24p to HD 24p on output.

    SD must always play to a monitor at 29.97, just as 720p needs to playout at 60p

    gary adcock
    Studio37
    HD & Film Consultation
    Post and Production Workflows

  • David Roth weiss

    May 25, 2007 at 2:16 pm

    [Bob Zelin] “everyone yells at me for telling them to work at 59.94”

    They just want to make sure you’re really listening when they tell you that there is a huge difference between monitoring video at 29.97 and converting video to 29.97.

    David Roth Weiss
    Director/Editor/Post-production Supervisor
    David Weiss Productions, Inc.
    Los Angeles

Page 1 of 2

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