MuseScore icon indicating copy to clipboard operation
MuseScore copied to clipboard

French horn randomly starts playing fff at the beginning of a crescendo

Open macaquedev opened this issue 1 year ago • 2 comments

Issue type

Muse Sounds bug

Bug description

Well, it's in the title.... bar 15 of a file that I cannot attach because GitHub won't let me, but I can email it to whoever needs it if that's easier. But at least I've got a screen recording.

Steps to reproduce

Open the file, press play, wait until bar 15, then the horn randomly starts blaring at fff

Screenshots/Screen recordings

https://github.com/musescore/MuseScore/assets/69220675/a8807974-38d8-47d6-8d3f-a760b5bf2414

MuseScore Version

MuseScore Studio 4.3

Regression

I don't know

Operating system

Windows 11

Additional context

MuseScore 4.3 (I think this kind of thing happened in 4.2 as well, earlier than that, I don't have a clue, sorry)

macaquedev avatar May 14 '24 19:05 macaquedev

The problem, as it turned out, is much more serious. See #22862

Dima-S-Jr avatar May 16 '24 12:05 Dima-S-Jr

@macaquedev To attach a file, put it into a .zip or just rename .mscz to .zip.

its-not-nice avatar May 17 '24 13:05 its-not-nice

for some reason I opened this file again (this time MuseScore 4.3.2) and it doesn't do this anymore.... how odd!

macaquedev avatar Jun 14 '24 13:06 macaquedev

blah, scratch that. the problem's back and worse than ever. 🤣

macaquedev avatar Jun 14 '24 18:06 macaquedev

Then definitely ZIP and attach the actual score we people can examine it in order to begin investigating the problem.

MarcSabatella avatar Jun 14 '24 19:06 MarcSabatella

horn thing.zip here, try this - it just starts blaring randomly.... it's so confusing and such a pain

macaquedev avatar Jun 14 '24 22:06 macaquedev

@macaquedev I'm going to suggest this might have been resolved, because I cannot reproduce it on my end.

https://github.com/musescore/MuseScore/assets/86290556/a629be36-2c46-459b-866f-8070f563d287

But I am running updated sampler and libraries, so it's also possible the fix might not yet be in production.

Perhaps check it out again, but for now I'll mark this as resolved. If after 4.4 is released the problem continues to persist for you, then we can reopen it.

bkunda avatar Jul 11 '24 13:07 bkunda