Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Blackmagic Design Edit To Tape accuracy issue

  • Edit To Tape accuracy issue

    Posted by Andrew Yoole on May 7, 2007 at 8:34 am

    Some weeks ago I joined in a thread with other PAL users complaining about inaccurate Edit To Tape operations from FCP using various Decklink cards. It seemed only to be affecting PAL users. A duplicate frame is recorded at the head of any insert or assemble operation, pushing the rest of the edit one frame late on tape.

    I am still experiencing this issue on ALL my 3 systems without fail. I can use the playback offset control to shift the issue around, but I ALWAYS get the duplicate frame on insert and assemble edits, meaning I’m unable to insert a segment into a program. I can work around the issue with full program records to tape (so long as they start in black).

    Am I the only one experiencing this issue now? Have I missed a more complete fix than the workaround I’m using?

    Any responses appreciated.

    Jacob Benjamin replied 18 years, 7 months ago 5 Members · 4 Replies
  • 4 Replies
  • Simon Blackledge

    May 7, 2007 at 11:20 am

    Not tried this yet, only got system up and running recently, though after a hunt about I think the issue is looking to be solved with 6.2 drivers. Due 2 weeks post NAB.

    I’ve only seen replies from BM team asking what setup is etc… no firm answers.

    A ” we know there is an issue” would be good so we are not tearing our hair out.

  • Anders Haavie

    May 7, 2007 at 7:20 pm

    Same issue here. This is a MAJOR problem for us, as we master shows daily, and insert does not work.

    Decklink should take care of this issue in the very near future, or we will be forced to move to AJA.

    Anders

  • Sam Goetz

    May 10, 2007 at 12:38 am

    This issue does not only affect PAL users, it’s been haunting my NTSC life for the past year. Finally, within the last couple of months, I’ve come to a fairly easy work around. The key is that it requires the 6.1 drivers.

    Still, the fact that there is a workaround does not make it ok that Blackmagic should continue to ignore this problem like it doesn’t exist. The workaround (although simple) is still a huge pain in the butt on a day to day basis. If Blackmagic could give a definite answer on when this will be fixed I would be very very happy.

    Here’s the workaround:

    – Download & install the 6.1 drivers, this will not work unless you use the 6.1 drivers.
    – Before laying off go into your “AUDIO & VIDEO SETTINGS.”
    – Click on the “Device Control Presets Tab.”
    – Select your current preset and click “Edit.”
    – Here is where things may vary between users. In the “Playback Offset” box it should say something like +00:00;04. Change this playback offset by 1 or 2 frames up or down and try laying off. For me, +00:00;05 gives me perfect frame accuracy and perfect sync. Anything else will throw off my sync and my frame accuracy. So be VERY VERY careful about your tests. 1 frame inaccuracy on sync can sometimes be very difficult to detect.
    – Once you’ve found out what you need to change your “playback offset” to, layoff.

    ** VERY IMPORTANT ** Every time I restart FCP this “playback offset” box gets reset back to 00:00;04. What this means is that I have to re-do these steps EVERY time I layoff. This is what I mean by Blackmagic needing to address this issue. I should not have to re-check my playback offset every single time I layoff it’s a huge time waster and leaves lots of room for error.

    Hope this work around helps and works. It’s worked on the dozens of stations at my workplace that were all having TC inaccuracy issues.

    Word,
    Sam

  • Jacob Benjamin

    October 18, 2007 at 8:32 pm

    Seriously this issue had haunted me as well. Our facility is heavily vested in blackmagic, and to be honest it is starting to be a huge regret. We probably have about 15 cards at the moment and not one of them can lay off frame accurate. I have tried the frame offset thing but it does not consistently work. This is especially annoying when you are working in 23.978 and you go to do a down convert. That frame-off issue becomes even more of a big deal taking stuff from 23.976 to 29.97.

    Considering switching to Kona,
    Jake

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