Closed bevand10 closed 1 year ago
Base: 85.97% // Head: 85.98% // Increases project coverage by +0.00%
:tada:
Coverage data is based on head (
bd070cf
) compared to base (cc1ee5e
). Patch coverage: 86.66% of modified lines in pull request are covered.
:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
Thanks, this is published in v3.1.0
What kind of change does this PR introduce?
Support for the
STAB
message -ST
reamingA
udioB
itratesWhat is the current behaviour?
STAB
is not currently supported.What is the new behaviour?
STAB
message receipt is supportedData received is added to the
atem.streaming
object. Here's the results of aconsole.log(atem.state);
command in Node when using this branch.STAB
message transmission is supportedA new command has been added to set streaming audio bitrates. BMD documentation states that a STAB message defines two bitrate values, one for framerates up to 30fps, and another for framerates greater than 30fps. It refers to these as
lowBitrate
andhighBitrate
values. Strictly speaking, IMO, these should really be referred to aslowFramerates
andhighFramerates
or even more explicitly,upto30fps
andmorethan30fps
, but I'll overlook that mistake from BMD!This example sets both values to 128k:
Safe defaults
When calling
atem.setStreamingAudioBitrates()
(i.e. without params), safe defaults are applied: