With the recent release (vMix 29), we can now access TimeCode in the API, which is great progress for external replay integrations.

However, one key piece of information is still missing: there’s currently no way to determine which replay event is currently selected, or which camera angles are active for that selected replay event, directly via the API.

This makes it difficult to synchronize external control surfaces or Stream Deck feedback with the replay module.
At the moment, the only workaround is to query both the API and replay2.xml:

The API gives general replay input data and TimeCode

replay2.xml lists all replay events, including selected angles and IDs

Unfortunately, these two sources cannot be directly linked — the API does not expose the event ID, and the XML’s timecodes differ from those in the API. As a result, there’s no reliable way to map the “currently selected replay” in the API to its corresponding entry in replay2.xml.

If the API could:
Provide the ID of the currently selected replay event, and/or
Include which angles are selected for that event

…it would eliminate the need for an external XML query and significantly improve integration possibilities for control systems and Stream Decks.

This would allow operators to instantly see which replay and camera angles are armed for playback — a critical need in live production where quick visual feedback and control are essential.