Description
Particularly evident with advanced h.264 branch. On any config update from client or evAPI, StreamPI unnecessarily emits the full, cached, master config document to all connected clients/evAPI instances. This unnecessary emit will either indicate or not indicate the applied update, depending on how long the update takes to be applied. In the case of external device communications like IP cameras, it will be like receiving a “middle” document that indicates pre-existing values. In the example of a new event linkage, it will be like receiving a “duplicate” config with the updated value.
<br>
Introduced Version
7.3.14 / 7.4.0
<br>
Platform
[All]<br>
Steps to reproduce
- Connect an IP camera.
- Change any setting that’s stored in camera (like adjusting brightness or contrast sliders).
<br>
Expected result
Your slider will remain at its new position without any jumping.
<br>
Actual result
Your slider will temporarily revert to its previous position, then jump back to the new position.
<br>
Work Around
User experience annoyance, so not actually broken. The config update does actually apply correctly.
<br>
Fixed Version
7.9.3 / 7.10.0