logo

Live Production Software Forums


Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

2 Pages<12
Options
Go to last post Go to first unread
sg93  
#21 Posted : Friday, November 20, 2026 4:43:36 AM(UTC)
sg93

Rank: Member

Groups: Registered
Joined: 10/31/2025(UTC)
Posts: 10
Germany

Originally Posted by: Dist Go to Quoted Post
Originally Posted by: sg93 Go to Quoted Post
Hi everyone,

In the ReplayAPI only the tag of the selected camera is shown. This maybe come in handy in some situations but it would be preferable if all tags were available with the tag of the active camera being in a separate data point


Have you tried ReplayEventsAPI? That provides all events data such as every single event, and the description (tag) of every single camera, and which cameras are enabled. So that provides all the event data, and in combination with ReplayAPI (or the main XML api, as the ReplayAPI is just a subset of that), will provide you with the playback data of what's currently selected, should be everything you need.


Yes. unfortunately it doesn't help because it doesn't change depending on which event is selected
doggy  
#22 Posted : Friday, November 20, 2026 5:12:23 AM(UTC)
doggy

Rank: Advanced Member

Groups: Registered
Joined: 12/27/2012(UTC)
Posts: 5,540
Belgium
Location: Belgium

Thanks: 319 times
Was thanked: 1022 time(s) in 839 post(s)
Originally Posted by: sg93 Go to Quoted Post
Originally Posted by: Dist Go to Quoted Post
Originally Posted by: sg93 Go to Quoted Post
Hi everyone,

In the ReplayAPI only the tag of the selected camera is shown. This maybe come in handy in some situations but it would be preferable if all tags were available with the tag of the active camera being in a separate data point


Have you tried ReplayEventsAPI? That provides all events data such as every single event, and the description (tag) of every single camera, and which cameras are enabled. So that provides all the event data, and in combination with ReplayAPI (or the main XML api, as the ReplayAPI is just a subset of that), will provide you with the playback data of what's currently selected, should be everything you need.


Yes. unfortunately it doesn't help because it doesn't change depending on which event is selected


The vMix API gives you the ID of the selected event, the Number of the selected camera and the tag of the selected
Based on the ID one can pull all the tags from that event and which angles are set from the ReplayEventsAPI
sg93  
#23 Posted : Saturday, November 21, 2026 1:16:39 AM(UTC)
sg93

Rank: Member

Groups: Registered
Joined: 10/31/2025(UTC)
Posts: 10
Germany

Originally Posted by: doggy Go to Quoted Post
Originally Posted by: sg93 Go to Quoted Post
Originally Posted by: Dist Go to Quoted Post
Originally Posted by: sg93 Go to Quoted Post
Hi everyone,

In the ReplayAPI only the tag of the selected camera is shown. This maybe come in handy in some situations but it would be preferable if all tags were available with the tag of the active camera being in a separate data point


Have you tried ReplayEventsAPI? That provides all events data such as every single event, and the description (tag) of every single camera, and which cameras are enabled. So that provides all the event data, and in combination with ReplayAPI (or the main XML api, as the ReplayAPI is just a subset of that), will provide you with the playback data of what's currently selected, should be everything you need.


Yes. unfortunately it doesn't help because it doesn't change depending on which event is selected


The vMix API gives you the ID of the selected event, the Number of the selected camera and the tag of the selected
Based on the ID one can pull all the tags from that event and which angles are set from the ReplayEventsAPI

Thats more of "hack" and creates an unnecessary step. Why not just include all information of the current event in the API anyway? :)
Dist  
#24 Posted : Saturday, November 21, 2026 2:43:23 AM(UTC)
Dist

Rank: Advanced Member

Groups: Registered
Joined: 12/19/2019(UTC)
Posts: 66
United Kingdom

Was thanked: 28 time(s) in 20 post(s)
Originally Posted by: sg93 Go to Quoted Post

Thats more of "hack" and creates an unnecessary step. Why not just include all information of the current event in the API anyway? :)


Not really a hack, more so different sources for different information.
For example the XML endpoint provides the data needed for things such as this

ShareX_NwufCaPWqz.png (17kb) downloaded 30 time(s).

This is what a lot of replay setups need, so that they can have parity with other replay systems that provide this data, they don't necessarily need the events data to show the state of every single camera/tag currently playing.

This is an example of the Events endpoint showing a single event (and you would need twice this as there's channels A and B).
Code:

<event>
<inPoint>-193859946</inPoint>
<outPoint>4665651678</outPoint>
<description>someTag</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<selectedAngles>True</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<id>4</id>
<speed>-1</speed>
</event>


If you need events data as well as replay data, poll them both, if you don't need events data you don't need to request it. I'd rather they didn't bloat the XML and ReplayXML endpoints with all of that data as that's a lot of data (in relation to the rest of the payload), and it's infrequently updating so wouldn't need to be polled as frequently as XML or ReplayXML.

Personally I don't think the inconvenience of needing to poll 2 different endpoints for different data outweighs the benefits of the data being split in this way as you can still get the data you need.
sg93  
#25 Posted : Saturday, November 21, 2026 3:26:08 AM(UTC)
sg93

Rank: Member

Groups: Registered
Joined: 10/31/2025(UTC)
Posts: 10
Germany

Originally Posted by: Dist Go to Quoted Post
Originally Posted by: sg93 Go to Quoted Post

Thats more of "hack" and creates an unnecessary step. Why not just include all information of the current event in the API anyway? :)


Not really a hack, more so different sources for different information.
For example the XML endpoint provides the data needed for things such as this

ShareX_NwufCaPWqz.png (17kb) downloaded 30 time(s).

This is what a lot of replay setups need, so that they can have parity with other replay systems that provide this data, they don't necessarily need the events data to show the state of every single camera/tag currently playing.

This is an example of the Events endpoint showing a single event (and you would need twice this as there's channels A and B).
Code:

<event>
<inPoint>-193859946</inPoint>
<outPoint>4665651678</outPoint>
<description>someTag</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<description>-</description>
<selectedAngles>True</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<selectedAngles>False</selectedAngles>
<id>4</id>
<speed>-1</speed>
</event>


If you need events data as well as replay data, poll them both, if you don't need events data you don't need to request it. I'd rather they didn't bloat the XML and ReplayXML endpoints with all of that data as that's a lot of data (in relation to the rest of the payload), and it's infrequently updating so wouldn't need to be polled as frequently as XML or ReplayXML.

Personally I don't think the inconvenience of needing to poll 2 different endpoints for different data outweighs the benefits of the data being split in this way as you can still get the data you need.

I don't think you understand my point.
It's not about polling two different endpoints.
The thing is ReplayAPI updates the content of the same row as the played event changes. ReplayEventsAPI basically is a static ordered list of events. I have no benefit using it in my case.
I want to play a list of events, have the data of the playing event shown in a title and updating the data as the event changes.
doggy  
#26 Posted : Saturday, November 21, 2026 5:05:26 AM(UTC)
doggy

Rank: Advanced Member

Groups: Registered
Joined: 12/27/2012(UTC)
Posts: 5,540
Belgium
Location: Belgium

Thanks: 319 times
Was thanked: 1022 time(s) in 839 post(s)
Originally Posted by: sg93 Go to Quoted Post

I want to play a list of events, have the data of the playing event shown in a title and updating the data as the event changes.


I dont understand the issue

If you poll ( with a datasource ) you get the info updated as the (multiple) events are played out

xpath //input[@type="Replay" ]//channel[1] that you can link to your title
Users browsing this topic
Guest (2)
2 Pages<12
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.