Musescore 3.3 -- Problems with playback
Hello,
Occasionally when I click the playback button for a score the piece does not playback (no sound). I've checked all the I/O settings (nothing had changed) and they are ok. Quitting Musescore and re-opening generally does the trick. When playback doesn't work all scores are affected; opening a different score doesn't make a difference. Never saw this issue with Musescore 2.
Sometimes the initial playback takes several seconds to start (first time play button is pressed).
Comments
that delay after statrup is normal, the SF3 soundfont gets loaded and unpacked into RAM in the background, this is causing the delay. Only option to avoid that is to use a(n uncompressed) SF2 soundfont
In reply to that delay after statrup is… by Jojo-Schmitz
That's fine, I can live with that. The main issue is that sometimes playback in non-functional unless I close and re-open the application. Using Windows 7, btw.
In reply to That's fine, I can live with… by dengelwood
You could in those cases try Edit > Settings > I/O > Restart Audio and MIDI devices
In reply to You could in those cases try… by Jojo-Schmitz
thanks, I will try that and post the results.
In reply to that delay after statrup is… by Jojo-Schmitz
This may be a stupid question, but does the soundfont need to be re-loaded/unpacked if the system has been idle for a time? I often take breaks from editing, and sometimes when I return to a session, there is a marked delay before playback begins.
In reply to This may be a stupid… by toffle
No, only once on startup. And again if you load a score that uses a different soundfont and has its name embeded
In reply to No, only once on startup… by Jojo-Schmitz
Well, that is odd. As I said, sometimes there is a delay after re-starting a session. (Once playback does begin, there are no further troubles.) I do not think there are any RAM-related issues, so it is puzzling. I have been aware of this for some time, certainly before updating to the most recent version.
In reply to Well, that is odd. As I said… by toffle
If you stop doing something, the operating system may suspend certain programs, particularly ones that use a lot of memory. A program like MuseScore using several sound fonts would have a more obvious delay than say your desktop calculator as the physical memory in the computer is reassigned by the operating system to the memory intensive program.
In reply to If you stop doing something,… by mike320
That makes sense, as I tend to alternate between working on scores/script. I'll get in the zone with one task or another, and not return to MS for an hour or so.