Bug in P2 Log and Transfer related to DVCPRO HD Frame Rate Converter

Describing the bug below is hard to do because of all the variables involved but I am going to try to make my description as clear as possible.

I recently started work on a spot that was shot in Panasonic DVCPRO HD using two different cameras, a HVX-200 and a HDX-900 (using P2 Gear for storage).
I am using FCP 6.0.3 on OS X 10.5.3.

All the footage came to me on a hard drive set up with the individual P2 cards as directories.

Ingestion using the Log and Transfer tool went normally.

All footage from the HVX-200 was perfect and did not exhibit the problem described below. All slo-mo footage from the 200 came in already converted which was good.

Since some footage from the HDX-900 was shot at 60FPS for conversion to 24FPS as slo-mo, I then attempted to use the DVCPRO HD Frame Rate converter to accomplish this.

I got this error dialog that said:
"The selected media file (FILE NAME) cannot be processed by this tool.
Only DVCPRO HD 720p 59.94 and 50 fps media files are supported."

Which is odd since this footage was EXACTLY that format.

I should also mention that the converter is embarrassingly flaky--sometimes the error dialog referred to a clip other than the one highlighted.

I tried a lot of things to make the converter work--putting all the slo mo stuff in a separate project and other voodoo that people had mentioned on the various forums to no avail.

In the end, I installed a clean version of Final Cut on another computer.

Using FCP 6.0, I re-ingested and tested. Under 6.0 the process worked smoothly and properly with no error dialog.

Also, using the footage ingested under FCP 6.0, the converter worked fine under FCP 6.0.3.

I notice that one of the software updates for FCP installs a package called:

P2.RADPlug

I believe that this is the culprit but removing it from 6.0.3 makes the Log and Transfer tool no longer work for P2 Directories.

This package is not in the plain FCP 6.0.

So my work-around is to use FCP 6.0 to ingest....not very elegant.

Love to hear any others experiencing this problem and finding other solutions.

Thanks,

Lance Moody