Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy General Error (88)

  • Anders Haavie

    April 30, 2008 at 2:22 pm

    Here is my take on it. I got this error message for the first time today. I could output a timeline with 50frames but not 25. Reinstalled aja drivers and then I noticed that my device control was set to 50 panasonic VTR.Changed it to Sony PAL VTR and then all worked. Not sure if this helps you out.. .

    Anders

    Xraid-Xserve-Xsan-Xeverything

  • Cedric Robertson

    April 8, 2009 at 6:53 pm

    I resolved my error 88.

    Timeline of 720p50 and edit to tape on Panasonic 1400 using Multibridge Extreme 720p50 8 bit.
    I changed the device settings in audio/video settings to frame rate of 25. Problem solved.

  • Mike Beats

    May 31, 2009 at 4:10 pm

    I actually came across this when laying off 720p 59.94 to a Panasonic D5 3700B deck. What got me by was actually putting in and out point. Weird. Also, I noticed the output was 2 frames off. I’m going to do it again and this time give it 720P reference.

  • Cedric Robertson

    June 4, 2009 at 6:23 pm

    I found that I was either spot on or 1 frame out and to rectify this, had to move my timeline by -2 frames and in point for print to tape by +1 frame. Hit and Miss.

    I find it insane that delivery must be on 1080i50. Why we can’t deliver on 720p50 is beyond me.

    We are also running into problems when shooting 50p mode and delivery needs to be 50i. Whether 720p50 or 1080p50. When editing we need to make sure that the edit point is not on a “b” field. With FCP, set the TC to 50 over 25 and a “b” field will show as a *. All editors must then add one frame to the edit point or subtract one from from the edit point.

    Who else has had this delivery problem?

  • Christopher Gray

    February 10, 2010 at 12:09 am

    I just wanted to thank everyone for contributions to this stream.
    I got the General Error (88) today when trying to output a downconverted
    23.98 timeline (using blackmagic card). The posts pointed to frame rate issues and that
    made me check the device control preset – sure enough it was 23.98, changing it to 59.94
    made everything work great.
    CGray

  • Andrew Saliga

    April 13, 2010 at 8:47 pm

    I had this same issue today and tried all the obvious troubleshooting steps.

    Turns out I was getting it because of one of my deck presets was misconfigured. I have one labeled “AJA Kona: 29.97 Sony VTR A” and one labeled “AJA Kona: 29.97 Sony VTR B”. Generally they are both set to the same settings. They are both even labeled 29.97. In “A/V Settings” I looked at the “Device Control Presets”, not the “Summary” page. Turns out that the preset got the fps switched to 59.94.

    On a slightly related note, I see a “Playback Offset” option. When would that come into play?

    -Andrew Saliga

    Steelehouse Productions
    http://www.steelehouse.com (undergoing a much-needed redesign)
    http://www.vimeo.com/steelehouse

  • Kurt Waddington

    October 2, 2010 at 3:05 am

    Hi all,

    Just thought I would post my experience with the General Error (88) problem. I was successfully Printing to tape when all of a sudden I couldn’t get past this error. Tried all of the above remedies to no avail.

    What fixed it for me was simply trashing all the FCP 7.0 preferences as per Larry Jordan’s instruction on the web somewhere as well as repairing the permissions on the Boot drive.

    After that PTT worked fine again. Obviously you have to go in and reset all your preferences again.

    Now it could have been either of the two things I did so you could try one at a time.

    Just thought it might help someone.

    Kurt

  • Andrew Dietz

    February 15, 2011 at 12:21 am

    It sounds like everyone figured this out. I had this error today whilst doing a 29.97 1080i downconversion (via Kona 3 Control Panel) to NTSC. I simply changed the deck control preset from 59.94 to 29.97 and everything was peachy.

Page 2 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy