Blackmagic Decklink HD Extreme 3D

[garnoil]

My Blackmagic Decklink HD Extreme 3D has stopped outputting 1920X1080 video and only outputs 720p. I had this problem before a long time ago and somehow I fixed it but...I can not remember how to fix it. I tried everything I could think off but 1920X1080 is not outputting form the card.

Does anyone know a fix for this?

At this point this is what is happening:

Load PT session with 1920X1080 video there is no video. Monitor say 'no sync signal'

Load PT session with 720 video everything works

Load PT session with 1920X1080 there is no video, remove 1920X1080 and replace with 720p it works.

I contacted Blackmagic and they say that the Decklink HD extreme only plays 720p out of Pro Tools. I have at least 40 feature films that use to output at 1920X1080 and now they do not.

I have trashed PT prefs (just in case it was something with PT) but I have not yet un-installed and re-installed blackmagic software as I am in the middle of a film.

Last time I fixed it I think it was a setting on the blackmagic panel but I tried everything and it is not working.

[smurfyou]

I would definitely try uninstalling the driver and reinstalling. An old version like 10.4.x. It might take a couple of reboots but it's quicker than chasing gremlins.

I've had a setting stick before and this cleared it up.

Mac or PC?

[minister]

Yeah, odd that BM would claim it only plays 720 out of PT as I rarely play 720 out of PT and do 1080 95% of the time.

Try:

1. Zapping P-Ram
2. Resetting SMS -- shut down computer, unplug for 30 seconds, hard restart
3. Get Memory Cleaner and pay for Extreme, run it
   https://fiplab.com/apps/memory-clean-for-mac
4. Uninstall/Reinstall Drivers

These have helped me.

[garnoil]

Originally Posted by smurfyou

I would definitely try uninstalling the driver and reinstalling. An old version like 10.4.x. It might take a couple of reboots but it's quicker than chasing gremlins.

I've had a setting stick before and this cleared it up.

Mac or PC?

Mac

[smurfyou]

OK. When I had a problem it was on a Windows machine. But I would still try uninstalling and reinstalling. It starts off with clean settings.

[MIKEROPHONICS]

Very scary that BM have almost zero idea about video in PT....

I keep saying it - but jump ship to AJA where support answers the phone and knows what you are talking about and their drivers just work (and better and more responsive than BM)

Failing that George have you tried restarting the ref generator that feeds the BM, I once had a flag caught on the BM (when I used to have one) which got refreshed when changing the ref from pal to NTSC.
Sometimes PT gets caught in this too - check the IO in the edit window to see what it thinks the video flags are, and check the apple 2 references of your session.

[garnoil]

Originally Posted by MIKEROPHONICS

Very scary that BM have almost zero idea about video in PT....

I keep saying it - but jump ship to AJA where support answers the phone and knows what you are talking about and their drivers just work (and better and more responsive than BM)

Failing that George have you tried restarting the ref generator that feeds the BM, I once had a flag caught on the BM (when I used to have one) which got refreshed when changing the ref from pal to NTSC.
Sometimes PT gets caught in this too - check the IO in the edit window to see what it thinks the video flags are, and check the apple 2 references of your session.

Thanks you I will follow your advise and re-start the generator and look at the reference in. I am ready to go to another video card solution, and the Aja sounds good. I will look at alternatives when things slow down.

[MIKEROPHONICS]

Great to hear you are so busy. We should catch up


Sent from my iPhone using Tapatalk

[garnoil]

Originally Posted by garnoil

Thanks you I will follow your advise and re-start the generator and look at the reference in. I am ready to go to another video card solution, and the Aja sounds good. I will look at alternatives when things slow down.

Update: I wanted to give you an update just in case someone runs into the same problems when Pro-Tools stops outputting 1920X1080 video and only outputs 720p when using the Blackmagic Decklink 3D Extreme video card.

Nothing worked after: Trashing prefs in Pro-Tools, un-installing and re-installing the Decklink drivers (desktop video), updating the drivers form 10.1.1 to 10.4, using memory clean extreme, re-starting the computer form cold, re-starting the generator form cold, re-strating sync hd form cold, re-starting the computer form an older Mac HD, and even re-setting the actual decklink card to make sure it was sitting properly in its PCIe slot. None of this worked, Pro-tools would not output 1920X1080 to an external monitor which I have been doing for 10 years.

As I was bout to give up and thinking that the Declkink must be shot, I was looking through the Pro-Tools preferences and options menus as perhaps, there was a setting that I was missing, although unlikely as I had never seen such a setting. At some point, I came up to the 'enable/disable' video hardware and out of frustration I disabled and enabled the hardware (unchecked the menu and re-checked it) and this, this, stupid thing fixed the problem. So in Pro-Tools the 'enable and disable' video hardware for some unknown reason reason can do something internally, and get stuck in the 720p output, that causes the video output of Pro-Tools (the video output that appears in the output of the video track) not to output any video at 1920X1080. When this happened (perhaps because I had loaded a 720p video) Pro-Tools got stuck in the 720p output. By this I mean, when the video output was set to 1920X1080 there would be no video out of the Dekclink card, but if I imported a 1920X1080 video into a PT session that had a 720p video, the newly imported 1920X1080 video would switch its output to 720 and play out of the card. But no session with 1920X1080 would output video out of the Deckling at all. Checking and unchecking (basically restarting the 'enable video hardware') fix the problem. Pro-Tools preferences should address this.

I hope this helps if someone runs into the same situations.