Forum Replies Created

  • Ben,

    I know your pain. I, too, was getting the same

  • Wsc2005

    December 20, 2006 at 9:02 am in reply to: Closed Captioning

    Maybe this helps. It sounds like you can overlay Line 21 on your timeline/video then output a CC-encoded tape. I’m interested in this workflow. Let us know if you can make it work. Good luck.

    https://www.cpcweb.com/Captioning/cap_how_nle_software_works.htm

    “Inserting Closed Captions to Video Using an NLE System
    CaptionMaker for NLE systems works by putting a 2-D visual representation of the appropriate closed caption commands into a QuickTime or AVI movie. This movie file is then imported into a non-linear computer editing system and put on the editing system time line exactly like other video material. A picture-in-picture effect or a crop effect is then applied to the imported movie to mask off all but the closed caption image lines, and the NLE system is used to merge the imported movie with video program material. The resulting video output from the NLE system is closed captioned. Using this method, no additional encoder is needed to produce closed captioned video.

    This method requires the NLE system to be able to display a line from the visual picture area into line 21 of the television signal vertical blanking interval (VBI). Video editing hardware from Avid, Media 100, Matrox and Pinnacle Systems, among others, supports this capability.”

  • Wsc2005

    September 14, 2005 at 6:21 am in reply to: KONA-2 Captured Video/Audio Sync Problems

    Greg,

    See my thread “Kona 2 Downconvert audio problem” on 9-08-05.
    I may have experienced the same problem. I was on FCP 4.5 at first.
    When I upgraded to FC Studio and Tiger, things got better.
    (Gee, that was only a $1400 fix.)
    Check your Mac system preferences– set the sound output to the Kona card.
    Also “refresh A/V devices” whenever you change settings in FCP.
    Check your audio playback preferences: Kona.
    Make sure that the audio offset is set to 0, (not the default 4).
    Good luck.

    WSC2005

  • Wsc2005

    September 10, 2005 at 10:51 am in reply to: *NEW* AJA Desktop Product News from IBC 2005

    30-day return policy? Since I bought the Kona 2 and Kbox only a week ago (with audio defects no less), I’m going to see this through. I needed the downconvert to deliver a rough cut to the client, and Kona 2 was the only solution at the time (besides Decklink). Had I known about LH, I would have waited. I’d gladly choose the analog I/O and $avings of LH over the upconvert and 4:4:4 of Kona 2. But perhaps I’m being shortsighted. Can anyone relate their experience and needs for upconverting? I’m looking for any upside here.

  • Wsc2005

    September 8, 2005 at 7:08 pm in reply to: Kona 2 Downconvert audio problem

    Sorry, Jeremy. I misspoke when I said the frame buffer was at 525i29.97 (the control was on “Mac Desktop”). When FCP takes control, the frame buffer is at 720p59.94. And I still have the audio problem. After troubleshooting with Clark and Rudy at AJA, we’re going to swap out the Kbox and proceed from there. If you or anybody else comes up with another solution, I welcome your thoughts.

  • Wsc2005

    September 8, 2005 at 6:03 pm in reply to: Kona 2 Downconvert audio problem

    The export is self-contained and plays fine when opened in a QuickTime player (at HD resolution). The Kona control panel shows 525i29.97 in the frame buffer, Comp SMPTE analog out. I thought I found the problem when I jiggled the connection behind the Kbox, but it went out of sync about 8 minutes in (the longest it played correctly.) I think I’ve tried about every preset combination. Could RAM be a factor?

  • Wsc2005

    September 8, 2005 at 5:36 pm in reply to: Kona 2 Downconvert audio problem

    I’ve exported a 15-minute sequence to a clip on one of my internal SATA drives. I still have the problem. Is there any other way I can troubleshoot the Kona card and Kbox? I think I’ve got a mismatch on one of my presets.

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