How can this not be a bug? Creating an empty project, not even touching a single thing or doing any action within the project sets this indicator into a permanent state of alert. IF the user would not be aware of that and manually reset it from alerting for no reason, it can not do its intended job. Because the user can not see when an actual overload would appear. This is not a behaviour, this is a broken functionality and only low on priority, because users can work around it easily. That said, I can understand that it is a lower priority, but it simply must not be as low as to survive two major software versions over the course of years and even that “big bug fixing update” for Cubase 10.5.
The thing is, this is not the only long lasting issue with the software, but it is so obvious and visible and shows how little priority bug fixing in general has for Cubase. And that is in itself a serious issue. Release deadlines and new features are prioritized, but that is no good when the new features rolled out are half baked and broken. People who make their income with this software, which is supposed to be a professional tool, simply can not afford to upgrade to a new release, as things get rolled out too early. This puts the “Pro” in question and is just a real shame.
Thank you for at least removing the Cubase-9 tag, by the way.