Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums AJA Video Systems Kona 2 RS 422 Issues

  • Kona 2 RS 422 Issues

    Posted by Jared Picune on March 21, 2006 at 5:44 pm

    About 90% of the time I boot my edit system, and go to log and capture, I have no communication with my VTRs. If I restart the Kona card sees them. Not a really big issue, because it does end up working, but I would just not like to restart before I have to capture all of the time (especially when a client is siting next to me). Does anyone have any ideas? Thanks in advance.

    Jared
    Idea Spring Editing, Inc.
    Denver Final Cut Pro UG

    Bob Zelin replied 20 years, 1 month ago 6 Members · 18 Replies
  • 18 Replies
  • Bob Zelin

    March 21, 2006 at 7:05 pm

    trash your FCP preferences, and try it again.
    Bob Zelin

  • Jared Picune

    March 21, 2006 at 7:41 pm

    I wish it were that simple. Trashing prefs does not make any difference. It was the first thing that I tried, but with no luck. It is just really weird. But thanks anyway.

    Jared
    Idea Spring Editing, Inc.
    Denver Final Cut Pro UG

  • Bob Zelin

    March 21, 2006 at 10:40 pm

    are you trying to communicate with Sony or Panasonic VTRs? And if they are Panasonic VTR’s – what model #’s.

    Bob Zelin

  • Jared Picune

    March 21, 2006 at 10:51 pm

    Sony uvw 1800 most of the time. Ironically, I also have a JVC D-9 deck and don’t seam to have issue nearly as much with it. However, I don’t use it very much at all, so I don’t know if that is a fair assumption. I have had issues trying to used an panasonic SD93 (I think that was the model) big issues there. Ended up having to use firewire. The Sony Digital Beta deck and the J3 deck worked once I did the reboot thing.

    To be fair I am connecting out of the Kona 2 to a cable technec (expecive RS 422) cable and into a patch bay. However, I am not sure how this would interfere, and how a reboot would solve the problem. Oh, and the OS sees the port on the Kona even when FCP will not see the deck.

    Jared
    Idea Spring Editing, Inc.
    Denver Final Cut Pro UG

  • Bob Zelin

    March 22, 2006 at 1:54 am

    OH EAT ME JARED ! –
    you write –

    To be fair I am connecting out of the Kona 2 to a cable technec (expecive RS 422) cable and into a patch bay. However, I am not sure how this would interfere, and how a reboot would solve the problem. Oh, and the OS sees the port on the Kona even when FCP will not see the deck.

    Jared

    REPLY – you have got to be kidding me. You CANNOT troubleshoot with a RS422 patch bay in line, and I have no idea of the quality of the RS422 bay you are using, nor do I care at this moment. YOU MUST do all of your tests with the RS422 cable plugged DIRECTLY into the VTR from the AJA product, with no AB boxes, no patch bays, no extenders. Once this fails, then you have something to complain about – until then, I don’t want to here it –

    here is how I qualify this statement. I just finished rewiring a 2 room AVID facility – one AVID Xpress Pro, one AVID Adrenlaline, one UVW1800 and one UVW1200 with an Addenda RS232 to RS422 adaptor on it. I put in a RS422 patch bay. All of a sudden, I could not get the AVID Xpress Pro to control the UVW1200 (via the Addenda), but every other combination works. So I know that the Adrenaline can control both Beta VTRs, but the XPress Pro can only control the UVW1800, not the 1200. JARED – THIS IS NOT AN AVID PROBLEM – THIS IS MY PROBLEM, and I am going back in to figure out what the hell is going on – I will do this by DRAGGING THE UVW1200 RIGHT OVER TO THE XPRESS PRO and plugging it in directly – thats right – I am going to unmount it from the rack, unplug all the cables, drag it into the room with the edit system, and wire it up locally. It’s a lot of work BUT I MUST DO IT.

    AND GUESS WHAT – this is EXACTLY what you are going to do. You MUST take the VTR right over to your AJA product, and plug it in DIRECTLY. If you have trouble getting RS422 control with the UVW1800, then there are issues with the MAC or AJA (probably the MAC software load). But if there are no problems, then it’s something else – and you won’t find out what that something else is, until you start replacing pieces, because as you see, if you reboot, it starts to work.

    Bob Zelin

  • Jared Picune

    March 22, 2006 at 2:12 am

    Sorry Bob, but I do appreciate you help. I have connected decks directly into the Kona 2, with the same problem. I just thought that maybe there was some fix that would not require a reboot if any one knew.

    Jared
    Idea Spring Editing, Inc.
    Denver Final Cut Pro UG

  • Wayne Carey

    March 22, 2006 at 6:58 pm

    Well, this will throw a wrench into your troubleshooting…. I have had this same exact problem ever since I purchased the system in May of 2005. Still no fix or no idea why this is happening. It happens with all driver versions and every time I have installed one I used the uninstall program first then repaired my permissions. Still no good…

    So….. What’s the answer now? Let me ask, Jared, what system are you using? I have a G5 Dual 2.7 with 4.5 gig of RAM. I’m just looking to see if you have the same, and if so, we have a problem with Apple on this issue.

    _____________________________

    Wayne Carey
    wcarey@strikeking.com

  • Jeremy Garchow

    March 22, 2006 at 7:44 pm

    Have you guys called AJA about this?

  • Jared Picune

    March 22, 2006 at 7:45 pm

    I have a dual 2.5 and only 2 gigs of RAM. I have the Kona 2 card, an Apple Fiber card for the Xserve RAID and an upgraded video card.

    Jared
    Idea Spring Editing, Inc.
    Denver Final Cut Pro UG

  • Jared Picune

    March 22, 2006 at 7:48 pm

    Have not contacted AJA, as it still works, but just thought that there might me a work around. And today I did not have a problem, go figure.

    Jared
    Idea Spring Editing, Inc.
    Denver Final Cut Pro UG

Page 1 of 2

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