Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums AJA Video Systems What the IO does NOT do.

  • What the IO does NOT do.

    Posted by Kevin Hedin on March 28, 2006 at 10:44 pm

    Ok, in case anyone is about to clone a tape with accurate timecode using the IO and the Control Panel, forget it. I’ve also confirmed this with AJA Tech Support today. Here was my scenario:

    SDI SOURCE VIDEO –> IO
    IO ANALOG COMPONANT –> BetaSP

    TC OUT to TC IN (deck to deck connection as there is no TC on the IO)

    There is a 2 frame video delay that CANNOT be adjusted using the IO Control Panel. If you are shooting 24p footage, you will notice the problem right away (on the cloned tape) when you expect your A frames to fall on :00 or :05, instead they fall on :02 and :07 which is not correct.

    Solution: Hooking the decks up directly, and bypassing the IO alltogether.

    What a bummer as I expected the IO to handle something as simple as a clone. If anyone has another workaround using the IO, please let me know.

    Kevin Hedin replied 20 years, 1 month ago 2 Members · 2 Replies
  • 2 Replies
  • Jeremy Garchow

    March 31, 2006 at 8:02 pm

    Well, it won’t wash your dirty dishes either. Your problem makes sense. If you were going through any a/d conversion you would experience this same delay. What you need is a time code processor from something like a Horita (TCP-50 is the model number). It’s a box that would insert a 2 frame delay into your timecode stream.

  • Kevin Hedin

    April 5, 2006 at 5:28 pm

    Thanks Jeremy for that product info. I didn’t know something like that existed. Now I might be able to continue to use my IO for Cloning tapes.

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