Rank: Advanced Member
Groups: Registered
Joined: 12/19/2019(UTC) Posts: 46  Was thanked: 23 time(s) in 16 post(s)
|
I'm one of the main developers for the Companion module for vMix, and when doing some v24 testing I noticed that we started getting some errors due to the API response about replay inputs differing from the structure we expected. My current assumption is that because v24 supports 8 cameras this leads to increased load times for that input, and if the API is polled during that loading the input returned is different from the standard response. This is all JSON, as I don't log the raw XML, but this is an example of a known good replay input: Code:{
key: 'bc8245b1-e288-4b89-9504-83d855c13914',
number: '6',
type: 'Replay',
title: 'rp1 - A',
shortTitle: 'rp1',
state: 'Paused',
position: '0',
duration: '-67',
loop: 'False',
muted: 'True',
volume: '100',
balance: '0',
solo: 'False',
audiobusses: 'M',
meterF1: '0',
meterF2: '0',
overlay: [],
replay: {
live: 'False',
recording: 'False',
channelMode: 'AB',
events: '1',
eventsA: '1',
eventsB: '1',
cameraA: '1',
cameraB: '1',
speed: '1',
speedA: '1',
speedB: '1'
}
}
But the API response that is given during the loading of the replay input is: Code:{
key: 'bc8245b1-e288-4b89-9504-83d855c13914',
number: '6',
type: 'Replay',
title: 'rp1 - A',
shortTitle: 'rp1',
state: 'Paused',
position: '0',
duration: '0',
loop: 'False',
}
Is there a public schema documenting the structure/types of the API response so that we know that some fields will not always be returned? If not, is this behaviour that we can expect from all inputs, where fields could be entirely missing if the XML API data is requested at a certain time in the inputs loading/unloading?
|
