Wed Jun 12, 2019 12:07 am
The new timecode functions don't seem to be mentioned at all in the latest SDK documentation. So even though they seem pretty straightforward, I suppose it's possible there is some trick to using them.
Since the ATEM control panel interface only lets you set hours, minutes, and seconds, I initially thought that maybe the frames parameter was ignored entirely. So I tried setting the timecode when the frame count would be 0 (when a change in seconds on the system clock happens), but this didn't seem to make a difference.
The other thing that is a bit odd, is that if you immediately call GetTimeCode() after calling SetTimecode(), the SDK seems to return the old timecode value. Which suggests that there may be some delay in setting the new timecode value.
I'm also not clear on what the purpose of the RequestTimeCode() function is. Does this need to be called before calling GetTimeCode()? Does it change what events are generated? It seems like at least some TimeCodeChanged events are generated without calling RequestTimeCode() though, so its purpose is a little murky.