Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Control Surface + FCP

  • Control Surface + FCP

    Posted by Asher Lewis on March 31, 2009 at 4:25 am

    Hi All,

    I’m having an odd issue with my Tascam FW 1082 and Final Cut. I’ve got it all set up as a control surface, but when i adjust the levels while the video is playing through the sequence the video starts lagging and eventually audio drops out. If i stop the playhead and restart playing it’s back in sync and playing audio.

    I’ve tried uninstalling and reinstalling fresh, in addition to deleting the control surface in FCP and then re-adding it…any other suggestions? (the tascam is on it’s own firewire bus btw).

    Cheers! and thanx!

    asher.

    Asher Lewis replied 17 years ago 3 Members · 5 Replies
  • 5 Replies
  • Michael Gissing

    March 31, 2009 at 4:30 am

    Not sure as I don’t use a control surface, but perhaps it is the writing off lots of keyframes that bogs the system down. There might be a setting to reduce the number of keyframes written from every frame to say every three frames.

    Do you have a grunty Mac & plenty of RAM?

  • Asher Lewis

    March 31, 2009 at 4:35 am

    it’s got plenty of ram, and i’m not even actually keyframing the audio i’m just setting levels for the track

  • Michael Gissing

    March 31, 2009 at 4:39 am

    You might have to talk to Apple and /or Tascam. Sorry I can’t be more helpful. There are others here at the cow, who use the Tascam and might have ideas.

  • Reid Caulfield

    April 13, 2009 at 1:55 am

    Sounds like FW bus overload.Are your media drives running on the same firewire bus? Is this new behavior for this setup? Have drives changed recently for some reason (system crash & restore, new driver install, etc)?

  • Asher Lewis

    April 13, 2009 at 2:03 am

    hey mate,

    thanx for the response. i ended up reinstalling the OS and the problem went away, i’m thinking it may have been a corrupt plugin.

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