incorrect parsing of ATEM data

[nrkno]

incorrect parsing of ATEM data

[mint-dewit]

The current status on this is that we throw an error when we find incorrect data. On some models this can however be mildy annoying as there are many errors (Ex. #24)

The errors on the user side of the library do not mean the user can do anything against this, this is really an error on the atem side of the connection and we unfortunately are not in a position where we can improve that. For this reason I think we could change the error throwing behaviour to a warning emitter or a parserError emitter. This could be something used for debugging or even logging in production systems but would not be as annoying for library consumers working on models that emit a lot of errors.

[Julusian]

A prerelease of v2.0.0 has just been pushed to npm under the nightly tag yarn add atem-connection@nightly that should resolve this, along with other problems.
The parsing has been made a lot less picky on values to avoid errors like this, and any out of range ids are now debug warnings rather than errors.

We are happy that v2.0.0 should be stable, but want to spend a bit more time giving it some realistic testing before doing a proper release of it.