AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() But the autodetect value was changed accidently in one place, so would always be seen as not matching in that check. ![]() The logging of that error is defined as 'if config is not autodetect, and config does not match what we are connected to, then log error`. Intenrlly this module has a feature list defined for each model. The module matches the device based on a numeric id the atem sends. Did the crashing happen in 2.1.0? Perhaps you could give a beta build of 2.2.0 a quick try too (backup your config first, it might mess thingsup), as that should behave I dont understand how that could happen with the correct model selected. ![]() Im not able to reproduce that crashing in 2.1.2, Ill give it another try later to confirm.
0 Comments
Read More
Leave a Reply. |