Jason Higgins
Forum Replies Created
-
We had the same problem after an upgrade from Tiger 10.4.11 to Snow Leopard. After days of scouring the net, testing hardware, running AppleJack, resetting PRAM, booting back into Tiger (where the problem does not show up), I finally came across this article concerning the ATI X1900 XT video card.
https://www.xlr8yourmac.com/archives/sep10/092410.html#S27417
Here is the Apple Doc for the recall.
https://support.apple.com/kb/ts3420
Jason Higgins
Editor
Point.360 West -
Hi 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
-
Hi 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