A minor help request, towards debugging Musescore

[bunsen_h]

There's a bug in Musescore's web interface that I'm seeing quite consistently, which their developers seem not to be able to reproduce. I have several scores on their server which are quite short but which feature many repeats, resulting in a fairly long play duration. That duration is shown at the top left of the score, as displayed in a web browser, and should be 3:19:48.  But every browser I've tried, with a variety of setup options, on two machines at home and on one at my library, shows it as 27:19:48 -- that is, an extra day tacked on.  The pieces are monotonous, but not that monotonous..!

If you wouldn't mind, would you please take a look at: https://musescore.com/user/28554317/scores/9087566, and let me know what duration you see just above the upper left corner of the score?  (At the library, I had to expand the page to "full screen" mode with a button at the top left in order to see the duration display.  I don't know why that was different from my machines at home; it may be a matter of screen resolution.)  It might also be useful to me to know what operating system and browser you used.

Thanks!

Comments

[bunsen_h]

I don't think that's it. I see the same thing regardless of time of day, from late morning in Ottawa (when I become functional) to an hour or so after midnight local time.

But I'm reminded of a bug I had to try to sort out nearly 30 years ago when I was the so-called "Manager of Scientific Support" for a software company. A few of our customers reported that a few of the commands in our scripting language weren't working. Eventually, one of them stumbled over part of the cause: the problem depended on the Windows language setting. Set to North American English, and most other languages, everything was fine. Set to some other languages, those commands didn't work. *Somehow,* a bog-standard library string comparison function -- comparing a string from a script to strings from a list of known commands -- was failing. (C's strcmp(), as best I can recall.) The bug popped up regardless of whether the script commands were being read from a plain-text file or being sent via the Windows API from, say, Excel or Visual Basic. We never did figure out why​; we didn't have the expertise or resources. All that we could do was to tell our customers how to work around the problem: change their language setting.