On Tue, Jan 25, 2022 at 09:27 AM, Gene wrote:

I was saying that we don't know why this problem is occurring since we don't know of any other cases where it is.  I am also saying that I very much doubt that the synthesizer itself generally announces cap because if it did, this would be such a serious bug that no one would buy it and we would have heard about this a long time ago.  And only two  reports doesn't tell us if this is a general problem or not.

-
Two reports, over the amount of time that things have been "as they are," which is quite a while, tells us directly that it is not a general problem.

I have said this, again and again, and will keep doing so until it sinks in for some:  Most issues are not global, they are idiosyncratic to the computer on which they are occurring.  As such, the solution does not lie with "fixing the software" (or similar) but figuring out what the heck is weird about your own machine.

I see this all the time given what I do for a living.  Sometimes it gets to the point where the only solution is what we in the biz call a "nuke and pave," a completely clean reinstall of Windows and the software the person was using (user data is backed up prior to doing a nuke and pave).

If this were a global problem, we would have heard about it many, many times from many, many users.  We have not.  That does tell us something, or should.  Whether what it tells us is accepted by the individuals afflicted by the issue is an entirely separate matter.  But there are "standard procedures" in place in instances such as this and there's no reason to change those.
 
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)