Casper Jeukendrup

It can't be the same as https://github.com/musescore/MuseScore/issues/17662, because that crash happens inside macOS-specific code. But I'll have a look.

@arkssheo It is important to test this with (the pre-release versions of) 4.1 specifically. Some of the crashes that occurred in 4.0.2 have been fixed, and I think there is...

Thanks for checking! It might be good to open a separate issue about the lag in handsfree mode (and include a description of what handsfree mode does exactly).

Might be related to https://github.com/musescore/MuseScore/commit/2fa36e3371700c49c37ac1a19b1eb47872c772c7: that commit may have fixed this, but sadly it had to be undone in https://github.com/musescore/MuseScore/pull/22681, because it caused big trouble (https://github.com/musescore/MuseScore/issues/22640, https://github.com/musescore/MuseScore/issues/22641)

There was a time where midi export was indeed broken in development builds. That PR is probably from that time, and has not been rebased since then, so the build...

@wizofaus It seems that problem is actually logged as https://github.com/musescore/MuseScore/issues/13220. If you'd indeed like to work on that issue, please post a comment there so that I can assign you...

It's perhaps not a priority, but that doesn't mean that if you create a PR it won't be reviewed. (to be honest, in my case, how soon I review a...

@DmitryArefiev If the performance is okay when scrolling around in a large score with many MuseJazz bold texts, then I think this can be merged!

Of course not, because this will only affect the drawing, and not the actual layout computations.

Since the differences seem too tiny to be spotted in real life, I think it's safe to merge this to master (but let's maybe not merge it to 4.1.0 yet)....