blackmagic input to windows in max 5?

    May 22 2010 | 10:51 pm
    So I have used blackmagic cards on windows machines before...and it was on an early version of Max 5 on xp pro. currently i cant get any of my blackmagic cards to send an input stream into jitter. I have tried intensity pro decklink studio and decklink sdi
    on both a 64 bit windows 7 system with i7 processor and a 32 bit windows xp pro system with i7 processor.
    I have tried installing newest direct x sdk as well as all relevant blackmagic drivers.
    i have tried using qt grab and dx grab and focusing on dx grab now as that is what I had success years ago with with the intensity card.
    anyone have success with blackmagic cards and windows recently? or anyone have a good source for older quicktime installers?
    thanks! B

    • May 23 2010 | 1:23 am
      using quicktime 6.5.2 gave me input to an intensity card on the analog breakout in 64 bit windows 7 going to test with multiple decklink cards now.
    • May 24 2010 | 12:36 am
      I was able to get two intensity cards streaming input from two separate jit.dx.grab objects on the analog NTSC inputs. I was actually unable to get any input into jitter from the decklink family of cards thus far. good framerates with intensity at 720 480 for grab and preview windows. b and h closed for today but will pick up another couple and test and post.
      using quicktime 6.5.2 windows 7 ultimate 64 max 5.1.4 intensity driver 3.6.3
    • May 24 2010 | 8:34 pm
      can't really offer any advice, but thanks for the reports.
    • Aug 12 2010 | 3:56 pm
      Did you manage to do that ? I'm getting into the same trouble.
    • Aug 17 2010 | 5:31 pm
      Hello, does it works on intensity shuttle on a laptop? Because I am don't arriving with matrox mxo2 mini...
    • Aug 31 2010 | 12:08 am
      custom driver is the best and only solution right now. blackmagic has a developer kit for download and they claim there are multiple companies using multiple decklink cards but they dont seem to be doing any of that research in house. looking at the base driver it really just seems to be some variable localization and such that needs to happen. should be small work for someone good in C.