Thu Oct 23, 2014 5:03 pm
We are noticing similar behavior on Windows systems running ATEM 6.1. From our testing, it appears that writing the H.264 file to existing folders on the local drive or attached storage like a RAID might be giving problems. However, if you create a new subfolder such as on the Desktop or on the RAID, this seems to capture as expected. This would be considered a workaround while we look into what might be going on.
There are a few other potential workarounds. The issue does not appear to occur in Blackmagic Media Express. This software is included with the ATEM download and can be found in the Desktop Video folder of your programs. It will also detect the ATEM Television Studio as a capture device in much the same way as the Capture Media palette in the ATEM GUI. Just make sure that you turn off the Capture Media palette before launching Media Express so the Television Studio is available for the software to grab.
Additionally, as others have noted, the issue does not appear to occur in the previous ATEM 6.0 release. Rolling back to this software version could be a viable workaround for the time being.
The issue also does not appear to occur on Mac OS X systems. I'm not sure I'd classify this as a workaround, but perhaps some might find this useful.
I'll add that this seems to only be related to H.264 capture from the ATEM Television Studio's USB 2.0 connection. Users employing capture devices such as DeckLink, UltraStudio, or Intensity devices should not experience any irregularities.
Sarah Jones
Blackmagic Design