Musescore playback with clicks and interference, crashes and does not save using new MacBook Pro.
I have previously reported a fault with the playback using a new MacBook 2019. The score was playing back with clicks and interference. However, there is now a more serious issue and that is that the software keeps crashing after it has opened or when I attempt to save anything?
Please help as I have spent weeks in creating a large score. I have sent the score to Muse score however it is too large to be accepted on this Forum as it exceeds 18mb.
Many thanks
Philip Hayward
Comments
(came here from #295684: Clicking on playback - crash on save)
See also https://musescore.org/en/node/290835
Hi,
I have a similar problem. I use musescore 3.3.2 and a mac. I've tried the file on different laptops, and there is always a lot of interference and eventually is slows down. Could anyone try this excerpt and see if he has the same problem?
Best regards
In reply to Hi, I have a similar problem… by Jeronome
That score has been created on Windows though (not that this would matter). It play just fine for me, on Windows 10, MuseScore 3.3.3
In reply to That score has been created… by Jojo-Schmitz
Yes, it was adapted from an existing score. Could it be a Mac compatibility issue then? Let's see if someone else has the same glitch...
In reply to Yes, it was adapted from an… by Jeronome
Since the files are identical internally, there should be no compatibility issues.
In reply to Since the files are… by mike320
I've asked 2 people to test it on their mac, they all have the same issue. So it is probably related to the mac version of Musescore. Further testing, or any idea to solve it, would be much appreciated :)
ISTR that some Macs have their audio interface set to 48kHz as default, while MuseScore enforced 41kHz and that way created unexpected sound artifacts.
See for example https://musescore.org/en/node/294451
In reply to ISTR that some Macs have… by jeetee
Hi Jeetee,
Not sure about what you mean by "audio interface". I though that encoded music could have different rates and a "reader" has to deal with it. Anyway, if that is the problem, I guess there's not much to do from a user point of view!
In reply to Hi Jeetee, Not sure about… by Jeronome
Simply put: at some point the digital audio signals have to be converted to analog signals within your computer; the thing responsible for it is called an "audio interface". It produces audio at a certain sample rate, which for MacOS seems to default to 48kHz.
Programs can request access to this interface and when given can assume that the audio is thus converted at a given sample rate. But programs can also request your audio interface to use a different sample rate. MuseScore is such a program, that requests your audio interface to work at 44,1kHz instead.
This in itself isn't necessarily a problem. The issue seems to arise that this happens while other programs have already connected with the audio interface and aren't aware of this change happening. So that other program might still assume audio to be processed at 48kHz, whilst in reality it isn't anymore. This can lead to audio artifacts.
All of the above is a theoretical explanation of what could cause some of the issues some of the users have perceived, based on information they have provided (I don't even have a Mac).
Hi Guys
Thank you to you all for having a look at this issue for me. It seems like there could be a compatibility issue with MacBook. I’m sure the lovely people at Musescore are onto this
Best wishes Phil.
Hi,
There is a weird behaviour with the playback with this file: From measure 15 on, many notes are missing. But when parts are played there is no problem. I tried to export the file as an mp3 and the problem remains.
I guess the more examples like this we find, the easier little bugs can be fixed :)
It's been tested on different computers.
Thanks
Jeronome