-
Kona LHe + Unlimited RT + Motion Templates = Crash every time
Greetings.
(The following problem is strictly Leopard related. Our Tiger systems are not encountering this issue.)
I’m testing out a Leopard based system prior to upgrading our production facility.
System versions at initial crash: OSX 10.5.2, Quicktime 7.3.1, FCP 6.0.2, AJA 5.1
Problem: Adding a DV-NTSC Motion Template to a DV-NTSC sequence causes FCP 6.0.2 to lock up mid-way through playback via Unlimited RT.
After consulting the Console logs after multiple Force Quits, I noticed some entries in the system log regarding “ProIO”, which was referring to the AJA IO box. When switching Video Playback to the Kona card, Console Logs made note of Kona instead of ProIO. Relaunching FCP, disabling external video, and adding the same motion templates to the sequence did not produce any FCP lockups. This lead me to suspect the AJA drivers.
I contacted Steve at AJA Tech Support, and he sent my crash logs to their software team. The following day, I received an email advising me to try upgrading that system to OSX 10.5.3, Quicktime 7.5, and FCP 6.0.3. Since this is a test system, I installed the upgrades and attempted to recreate the crash. With the updates, this time FCP would play through the motion template, however, trying to stop playback (by pressing the space bar) would cause FCP to Crash. The difference this time was that FCP would actually crash and display a dialogue box with what it suspected was the cause of the crash “AJAVideoOutput” plug-in.
Screenshot: https://dl.getdropbox.com/u/19589/FCP%20Crash%20Message.png
Yesterday, I booted back into Leopard after receiving an email from Steve which said that this problem was “fixed with 10.5.3 and 6.0.3”, just to give it another shot. For some reason, I could not duplicate the crashes…until today. I remembered that yesterday, I changed my FCP scopes to monitor the Viewer instead of Current Frame. When I switched the scopes to Current Frame and attempted a playback through a .motn file…crash.
I’ve been able to duplicate this issue on another Leopard machine here, however, I’m not at liberty to upgrade that one since it is an online machine and also because our facility is currently standardized on 10.4.11 and FCP 6.0.2.
What is the point of this post? I’d like to see if anyone out there can also duplicate this problem.
Crash logs are available upon request.