Activity › Forums › AJA Video Systems › Kona3 RS422 interrupts
-
Doug Beal
December 21, 2010 at 8:03 pmWe have no issues patching 422 control to any of the decks in house, hot patching 422 has never been an issue going back thru nonlinear days. I’ve seen issues with Kona controllers when someone has gone in to the Network pane in system preferences and attempted to connect Kona Serial, I’ve seen issues when the HDCam (SR and vanilla) is improperly configured as to which downconvert or off-tape signal is being sent down the 422 line, but that’s frame rate servo issues. None of our Apple/FCP/AJA stations nor HP/DS/AJA stations drop 422 connections. The only time I’ve seen issues is when the appropriate machine are not patched, the tape is record inhibited or my most occuring error “local” (I need a remote for my remote)
If you’ve been doing this for that long the you can look at the “capture setting” during output as the old “preview switcher” from linear switcher days.
Sounds like a call to AJA is in orderDoug Beal
Editor / Engineer
Rock Creative Images
Nashville TN -
Bob Zelin
December 22, 2010 at 1:24 amBoy Doug, what’s the problem. You’ve been doing this for 30 years – never saw a dead CMX port, never saw a dead AVID port ? This is NOT an OS-X 10.6.x issue, and even though Apple makes me sick, this is not their problem. AJA will be thrilled to send you a replacement card, or K3 box, or breakout cables. If you already have the original breakout cable that came with your Kona 3 (not the K3 box), there is a RS422 connector on it, so you can see quickly if the problem is your K3, K3 breakout cables, or the Kona 3 itself – this will save you some time.
Troubleshooting, and equipment failure is part of being in this business and owning equipment. Don’t tell me that “you never had any problems with any thing you ever owned in the last 30 years”, because that will prove to this forum that you have been working as a house painter, instead of this business. Equipment aggrivation is what our industry is all about. No ulcer – you ain’t a pro.
Bob Zelin
-
Doug Beal
December 22, 2010 at 6:26 pmBob
My reply was to Joseph having the problem
I don’t have “those” problems
I have some problems but not the kind this wonderful forum seeks to address.
All the best in the new year.Doug Beal
Editor / Engineer
Rock Creative Images
Nashville TN -
Jason Higgins
December 28, 2010 at 12:54 amHi all,
I’m currently experiencing the exact same issues with deck control. I’m using a Mac Pro 2 X 3GHz Dual-Core Intel Xeon with 8 GB RAM and a Kona 3. I’m running FCP 7.0.3 on OS X 10.6.5. This installation of Snow Leopard is about two weeks old.
We have four Final Cut rigs here. Three of which are running Leopard with FCP 7 and Kona 3’s and are working as well as can be expected. The machine exhibiting the problem with deck control is a test machine to verify the functionality of Snow Leopard. It was previously running FCP 6 on OS X 10.4.11 and we didn’t have any problem connecting to any deck in our tape room before upgrading to Snow Leopard.
I would have to disagree that this problem is hardware related other then possibly how Snow Leopard communicates with the hardware via it’s drivers. While this is likely what is going on when we have perfectly good hardware that worked well under previous versions of OS X and after an upgrade begins behaving strangely, we are lead to believe that we should buy new hardware to solve the problem. Now I’m aware that the this PC is a few years old but for a lot of the work that we do here it performs as well as our 8 core or 12 core machines. I’m sure that Apple would like everyone to buy a new computer every time they release a new os. That way they wouldn’t have to support legacy hardware but this just isn’t feasible for most consumers. Weather the blame for this current problem lies with Apple or AJA, I couldn’t say but I am tired of dealing with this crap.
Sorry about the rant, but there it is.
Jason Higgins
Editor
Point.360 West -
Jeremy Garchow
December 28, 2010 at 1:52 amWhat version of Kona drivers and have you contacted AJA about it?
-
Jason Higgins
December 28, 2010 at 2:41 amHi Jeremy,
I’m using Kona driver version 8.0 NDD. I have not contacted AJA concerning this issue yet. I usually spend a little time troubleshooting and researching a problem before I call tech support. Also I’m on a swing shift and I literally walked into this problem when I came to work today. If I haven’t found a solution before I come to work tomorrow I’ll probably give AJA a call.
One odd thing about this is we did use the system for over a ween without issue. (At least not this issue.) Then I come in today and FCP is losing communication with the deck. It’s really a new adventure every day.
Jason
-
Joseph Owens
December 31, 2010 at 7:48 pmI thought it might be a prefs issue and did the old superstitious mantra “trash prefs”. I was also starting to get random crashes with various plugins, specifically the AJA Kona Plugin for FCP.
No dice, plus I got to reset all my preferences, trims, offsets, paths, default directories, and so on.
I can’t see how this cannot be a system problem, since resetting the system fixes it (at least temporarily).
jPo
You mean “Old Ben”? Ben Kenobi?
Reply to this Discussion! Login or Sign Up