We’ve discussed this with our senior QA and development teams. The team is investigating some possibilities here and, as soon as that investigation is complete, we’ll be sure to follow up ASAP.
You have our apologies for the trouble here, and we’ve greatly appreciated your patience as we continue investigating this tricky issue. We’ll be in touch as soon as we can.
Hello @oekrep
Thank you for the update.
I have the great news, our QA team are no longer able to reproduce the issue on the current internal build. So seems the fix would be included in the next release. Please follow our Roon Software Discussion > Software Release Notes and let us know if the issue resolved after the next upgrade.