Survived a MuseScore attack tonight

[sgcim]

I had a performance of a new chart I wrote tonight by a big band I play in. Luckily, it's not one of best of the three bands I play in, and I use this band to test out any new chart that has never been performed before.
When we got to the sax soli, two of the sax parts didn't have the same amount of bars as the other three saxes had. When I got home, I compared the score to the parts, and it was perfect. Then I looked at the 1^st Tenor and 2^nd alto parts we played tonight, and the freaking thing repeated two bars of the 1^st Tenor part, and omitted two bars of the 2^nd alto part!

So I just pressed the print button, and it came out perfect. The other three sax parts were all eight bars.
Why would something like that happen?

[grahambop]

Maybe it’s a new AI feature which helps you by making ‘improvements’ to your scores without telling you.

[Christian Miller]

Make sure you flag the error with the development team. They do in fact want to hear about this stuff.

[sgcim]

maybe it’s a new ai feature which helps you by making ‘improvements’ to your scores without telling you.

lollllllllllllllll!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!

[GuyBoden]

MuseScore has lots of quirks and bugs.

But, it's FREE.

I'm a Software Engineer and I've grown to like MuseScore a lot.

Download MuseScore Here;
Download | MuseScore

[rpjazzguitar]

If the electrical grid worked like software, you could turn off your radio in San Diego and trigger a power failure in all of Des Moines. If it's not, somehow, a version control issue, it may be that kind of not-obvious bug.

[RJVB]

Why would something like that happen?

The answer to that question is obvious: because you asked for it!


Without knowing exactly what you were asking for, of course

File a bug report. If your chart isn't in the public domain, say so; the devs have to be used to dealing with content required to reproduce an issue that cannot be shared publicly (attached to the issue).

[jzucker]

post a bug report and upload your score at their gitlab site.

[sgcim]

I wrote the chart a few years ago (I've written over 80 charts). They've had so many updated versions since then, the bug has probably been fixed by now, so reporting it probably isn't important.

[GuyBoden]

I wrote the chart a few years ago (I've written over 80 charts). They've had so many updated versions since then, the bug has probably been fixed by now, so reporting it probably isn't important.

'I wrote the chart a few years ago'

Backward compatibility is always an issue with Software releases, it should have been tested, but Software is expensive to test everything.