[Remco Wiekard]

I’m still able to control any other machine (suchs as xd cam 1500, betacam J3, several DV decks). I am connected to a rs-422 switch in the machine-room.
This is just a temporary solution. I think that Blackmagic will speed up the proces of making a new driver to solve this problem. But in the mean time, I can connect to a DVW-A500

MacPro dual Quad 2,8 GHz – 16 GB RAM – Decklink Studio – FCP 6.05 – OSX 10.5.6 – G5 dual 2,0 GHz – 4 GB RAM – Decklink Extreme – FCP 6.05 – OSX 10.5.6

[Remco Wiekard]

here is the original mail i got from B;ackmagic design.

“We believe that this may be a grounding issue, similar to your
customer who tried to ground pins together. The current solution is
we have a small RS422 pin map cable, which so far has shown to solve
the problem in our testing. This will need to be attached to the back
of the Decklink card, and then the RS422 cable run as normal.
This problem will now be examined further in hardware/firmware and an
appropriate solution found.”

Pin out of the pin map cable is:

Cross pin 8 (Receive A) and pin 2 (Transmit A).

8 > 2
2 > 8

MacPro dual Quad 2,8 GHz – 16 GB RAM – Decklink Studio – FCP 6.05 – OSX 10.5.6 – G5 dual 2,0 GHz – 4 GB RAM – Decklink Extreme – FCP 6.05 – OSX 10.5.6

[Remco Wiekard]

If you are looking for a big floating tinecode window for Final Cut Pro,
this one is free and works great.
https://e-pocalypse.com/timecode/

MacPro dual Quad 2,8 GHz – 16 GB RAM – Decklink Studio – FCP 6.05 – OSX 10.5.6 – G5 dual 2,0 GHz – 4 GB RAM – Decklink Extreme – FCP 6.05 – OSX 10.5.6

[Remco Wiekard]

I don’t understand why it works, but it does. The only thing I do know is that when I used a straight sony rs-422 cable, the studio card did not see a machine. Crosswiring solved that problem. Blackmagic gave me that solution and it solved the problem

MacPro dual Quad 2,8 GHz – 16 GB RAM – Decklink Studio – FCP 6.05 – OSX 10.5.6 – G5 dual 2,0 GHz – 4 GB RAM – Decklink Extreme – FCP 6.05 – OSX 10.5.6