Audio Crackling in Musescore 3+ on MacOS
In Musescore versions 3+, I've been having an extremely annoying audio crackling issue that's caused me to stick to version 2.3.2. I recorded an example of the issue: https://www.youtube.com/watch?v=uOOiwp_SSEM
All I did was open the attached midi file in the Musescore 3.4 Beta (the issue affects all Musescore 3+ versions), and record the audio and video. I'm using the default soundfont with no alterations to any audio settings and I'm running the latest MacOS Catalina. If anyone could help that would be greatly appreciated.
| Attachment | Size |
|---|---|
| example.mid | 5.24 KB |
Comments
Sounds like your system is having a hard time keeping up. A smaller soundfont, more RAM, or a faster computer might help. Also search the forum for other threads on this that may have other suggestions.
In reply to Sounds like your system is… by Marc Sabatella
The problem only occurs in Musescore 3+. In 2.3.2 I can run any soundfont with any number of instruments and my computer does fine. And it's not only with a large number of instruments, it also happens with just a solo piano often.
In reply to The problem only occurs in… by jakekgearhart
I, too, encountered this problem with the advent of MS3, on a mac. I went as far as to replace the Mac with a bigger, newer one (there were other motivating factors), and while it has gotten immeasurably better over time, occasionally it recurs, but not enough to be a problem.
In reply to I, too, encountered this… by [DELETED] 1831606
It's been a major problem for me. Is there a bug report or something somewhere that'll get the attention of the developers? I can't upgrade until the issue is fixed.
In reply to The problem only occurs in… by jakekgearhart
Different version of Qt and many other dependencies we rely on could easily mean it's more resource-hungry than before due to no fault of our own. For whatever reason, seems to mostly be the case on macOS.
In reply to Different version of Qt and… by Marc Sabatella
I'm using the 2019 Macbook Pro with 8GB of RAM and when using a sine wave only soundfont and only one instrument, I get the same issue. I highly doubt it's a resource problem. Is there any way this issue can be researched because it's a major problem if the application doesn't work properly on MacOS.
In reply to I'm using the 2019 Macbook… by jakekgearhart
So far no developer is able to reproduce it that I know of. Seems to only affect a small number of users, so we'd need one of them to do more investigation. Could be a bad interaction with some other application or library I suppose.
In reply to So far no developer is able… by Marc Sabatella
I'm willing to do any investigating necessary to help out. I can create a new installation of MacOS on my laptop to see if any non-default application or library is causing the issue because that seems to be a good first step.
In reply to I'm willing to do any… by jakekgearhart
I put a great deal of effort into trying to reproduce it usefully over a year ago when MS3 came out. Couldn't. Good luck. It's good almost every day now, but every so often, a score is corrupt, and almost always, playing it again makes it better.
In reply to I'm willing to do any… by jakekgearhart
On MacOS, do you have the chance to set your audio driver's settings to 44.1kHz 16bit?
Or do you have a chance to force these settings?
It's worth a try if you have one.
In reply to On MacOS, do you have the… by Ziya Mete Demircan
Mine isn't failing now (most days). @jakekgearhart should try it. I remember playing with that to no avail.