Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Blackmagic Design not communicating with digibeta deck

  • not communicating with digibeta deck

    Posted by Jeremiah Black on October 8, 2005 at 12:43 am

    Hi,

    I just recently hooked my decklink extreme into a DVW-a500 digibeta deck, and keep getting “no communication” from FCP. I have the rs-422 pluged in fine, and the SDI ouput on the deck going into my decklink, but I get no picture or anything. Is there something I’m missing? I have the inputs in system preferences set to SDI, but it seems like my card isn’t responding.

    help,

    – JB

    Jeremiah Black replied 20 years, 7 months ago 3 Members · 4 Replies
  • 4 Replies
  • Jeremiah Black

    October 8, 2005 at 1:51 am

    Well, I got it up and running- I had to switch to pb.ee switch on the digibeta deck.

    My next question is that I chose “Blackmagic 10 bit” easy setup, but when I look at the setup- I notice that capture has the digitzer set to off, and it doesn;t work. Blackmagic easy setup 8 bit works, but not 10 bit. What easy setup should I be using?

    thanks

  • Sean Oneil

    October 10, 2005 at 9:05 pm

    You must have changed your Audio Video Settings. The Blackmagic 10-bit Easy Setup will not have digitizer set to off.

    You can always re-install the Blackmagic drivers to restore the default Easy Setups and AV settings.

  • Kristian Lam

    October 11, 2005 at 5:13 am

    Hi Jeremiah,

    Please also make sure you run the “Uninstall Blackmagic” application in the driver download before re-installing again.

    regards

    Kristian
    Blackmagic Design

  • Jeremiah Black

    October 13, 2005 at 8:50 pm

    Sean,

    Incorrect. I just uninstalled my drivers and then reinstalled them. And the 10 bit NTSC easy set up is (again) automatically set to have the digitizer off. Says everything is “missing”. Every other Blackmagic easy setup, however, is just fine.

    There appears to be some sort of bug in the drivers or something.

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