Version 2.8 of Kramer Control is a single focus on improving stability of the Kramer Control solution. Our team has done a great job at identifying root issues that have affected Brain stability on SL hardware and issues with the Kramer Control client applications on iOS and Android.


SL Brain Stability

With the release of Kramer Control version 2.8 we have improved the Brain stability on SL hardware. We identified in previous versions that the root Linux OS on the SL hardware was killing the Brain process when too many resources were being used. Our team made some changes to the storage allocation on the SL hardware and in testing we have greatly improved reliability of the SL hardware.

Publish File Download

Our team identified that in versions 2.6.3 and 2.7, that the publish file would be downloaded regardless of publishing changes being made. This could happen on hardware restart, Brain restart, or Brain state change. This issue caused a need to additional resources on the SL hardware and caused some of the issues we mentioned above where the Linux OS would kill the Brain process due to amount of resources used on the hardware.

Android and iOS Applications

Version 2.8 also addresses memory issues on the client applications. We identified that memory would grow inside the applications very quickly, especially with large scale installations. We have resolved this quick memory growth and now in testing we see better stability and much less memory being used by Kramer Control.

Builder Fixes

  • Corrected an issue where alias state keys would change if an alias name was edited
  • Corrected an issue where image libraries were not saving order when Builder was re-opened
  • Corrected an issue where re-ordering events by moving an event to the bottom of the list of events would cause the view to change to the top unexpectedly
Revision: 4
Last modified: 25 May 2022


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment