FCP & VTR error messages
I have been installing several FCP 5.1 on new MacPro Intel G5's since last December. And I have been getting reports from the editors who operate these systems that they are getting error reports from FCP about the VTR. We have tried many different approaches to solve the problem, but to no avail. Part of the problem is that it is intermittent. What we are using are brand new MacPro Intel G5's with with 8GB RAM. Besides the internal OS drive, there is another internal 500GB drive for FCP media. The MacPro is at 10.4.8. FCP is at version 5.1.4. We are using Blackmagics MultiBridge Pro as the video/audio interface. That is at version 5.9.2 which is current. This uses the Decklink machine control software which is also 5.9.2. We connect machine control via a 9 pin RS-422 cable. The video is connect via the SDI port on the MultiBridge and the SDI on the VTR. We are using the 8 bit uncompressed setting. The throughput on the hard drive is more than adequate. Audio is analog. The tapedecks are Panasonic DVC Pro. We are using the Panasonic RS-422 protocol setup in FCP Device Control Setup. What the editors are reporting is that while digitizing they will get this error message on the screen and FCP stops digitizing. The first error message reads as follows "Tape trouble. Check VTR. Do not attempt to eject tape or use transport without checking VTR first." They will then click the OK button and this error message will appear twice again. After the third time they get this message. "Capture Now has reached the end of the tape. All existing footage between the point where you started the capture and the end of the tape was captured successfully" They click on OK and the error message disappears and that is it. The VTR is still running and is not at the end of tape. The editors rewind the tape to where the digitizing was halted and then begin again to digitize. The error message may or may not appear again. There is no break in timecode. FCP does not crash, there is nothing listed in any of the log files. Has anyone else run across this? Anyone have any ideas for a solution? We've tried just about everything we can think of. Thanks in advance for the help.
TiBook 867 among others, Mac OS X (10.4.8)