Blackmagic Forum

Running Win 7 64-bit with the latest software build for the ATEM TV Studio on an i7. Am able to control the ATEM TV Studio normally w/o incident. However, periodically (exact timing is random), the app stops responding and has to be killed.

When its restarted, everything is fine and the hardware does't need to be reset/rebooted.

Network OK ? All IPs correct ? (No Double)
New Router ? wLAN ok ?

Pretty sure the network was ok, but what I'll do is a setup a ping window in the background and see if we ever lose connectivity with the device and if so, whether that correlates to the app not responding to input and needed to be killed.

The IP address was pulled out of the DHCP pool so there shouldn't be a conflict, but I'll double check that also.

1. be sure, that Controlling Computer and ATEM really have different IPs.

2. connect Controlling Computer direct to ATEM with Network-cable. What Happens ?

Did a test last night. Had a background window pinging the ATEM TV Studio and the app never was unresponsive. Unclear if that was just coincidence or a potential lead to the root cause.

Last nights test was only 30 minutes, will do a longer test this weekend.

Maybe another device (e.g. A Second Computer) Uses One of the IPs. So a Test only pc and ATEM directliy connected is the First step. Ping Controllers IP and Atems IP in the Network, when both are switched Off or not connected to network to find other devices with this IPs. Maybe use Controller and ATEM in a separate subnet or Network area.

The other thing to know is what type of switch you are using. ATEM's and their Control computers do not work well on 10/100 switches - much better to use Gigabit. The amount of network traffic between the devices can be quite high. I've never seen the ATEM Software control lock-up - but rather just disconnect.

Anyhow... something else to consider.

Its a 10/100 switch. I'll try a gigabit switch and see if that makes a difference.

Behaved much better this weekend w/a gigabit switch.

There were only two times when it stopped responding and both times was when the display driver crashed. Now what is interesting is only the ATEM studio became non-responsive when the display driver crashed. All other apps continued w/o incident.

So the question is whether or not this is a display driver bug and the Black Magic software is the innocent victim or the BM software is doing something that caused the display driver to crash.