[Dean Mermell]

Actually, BlackMagic worked with me on this. I sent them the card and after numerous tests they determined there was in fact something wrong with the card and sent me a new one. I’ve just installed it and it seems to be working perfectly, the computer starts up in under 30 seconds.

[Dean Mermell]

I second that emotion. On my new 1/08 MacPro, 10.5.1, with FCP 6.0.2, 8GB of RAM, BlackMagic Decklink HD card (uh-huh, you say?) I get slow to no audio waveform drawing, regardless of track size or project size. No rhyme or reason that I can see, and it’s MOST annoying, to be sure. Would appreciate any suggestions, thanks.

[Dean Mermell]

Imagine Software just published a fix for the problem with QT 7.3 and P2 log (pro).
Here’s what they just sent me:
ATTENTION MAC USERS of HD Log, P2 Log, and P2 Log Pro

We’ve now resolved the incompatibility issues with the recent QuickTime 7.3 update. The problem was P2 specific.

New versions of all Panasonic P2 compatible applications are now available for download that are fully compatible with QT 7.0 – 7.3. The patches are also compatible with OSX 10.5.

Please download the appropriate update for your software from our web page at: http://www.ImagineProducts.com/dlupdates.htm (under the Support/Downloads tab)

Details of the problem:

The new QT 7.3 changed (slightly) how null values within the MOV file header are defined. Apple, for some unknown reason, departed from the long standing zero (0) designator for a null setting–now a minus one (-1) value = null. This small change (which may have been an oversight?), causes QT Player and any QT based application attempting to play the MOV file to fail since the QT engine no longer knows what action to perform when a zero designation is encountered.

Since MOV files already existing with a zero designation are no longer playable, it is unclear at this point whether Apple will fix the problem in later QT updates or not. There are numerous applications providing QT files that may have been affected by this problem, and you may have many older QT files created by Apple applications that will not open due to this problem.

At Imagine Products, we’re looking into the possibility of providing a batch “repair” utility for existing MOV files with this specific problem. If successful, we’ll send out another email when it’s available.

Thank you all again for your patience. And again, we wish you a happy holiday.

Sincerely,

The Imagine Products, Inc. Team

[Dean Mermell]

It’s a bad thing, this thing. I was fortunate in that I had another drive with my previous system cloned onto it (my favorite form of backup) which I swapped out with my “updated” QT drive, and I’m back in business. If I didn’t, I’d be looking at the complete reinstall you’re talking about, not pretty. I’d like to think there’s a fix in the new 6.0.2 update to fcp just released, but I read the release notes briefly and saw nothing about this problem in there…
Poor imagine software…all their mac stuff is broken with this QT release, it must really suck for them.

[Dean Mermell]

I was fortunate, or perhaps smart enough, to have cloned my hard drive to another drive about a month ago, so I’ve offloaded the newer files off my current drive, wiped it clean, and am now cloning the old drive and its unupgraded QT system back onto my working drive. I guess the alternative would have been an archive and install with 7.2 QT, but it didn’t come to that for me. Best of luck….this is indeed nasty.

[Dean Mermell]

I haven’t had any luck finding the stand alone installer for 7.2.1. I think the idea is to archive and install your system software from the Tiger disc and then upgrade QT separately from the stand alone, but I can’t find it. In my case, I’m waiting on Apple or Imagine software to post a patch to this problem soon, which I sure hope happens. My problem is with P2 clips brought into FCP via P2 log pro.

[Dean Mermell]

Did you just upgrade to QT 7.3.0? There are several problems happening, including green canvas output, and other things that I have at the moment…

[Dean Mermell]

I just spoke with the people at Imagine software. They’re not sure that reverting to an earlier version of QT will help at this point, and the “replacing codec” fix does not seem relevant to this particular issue with P2 Log Pro files.