Playback won't start on the first note
Hi all, here's strange one.
I opened a MS3 score to work on in MS4. The score in is 4/4, some bars have triplets in.
On playback, whichever bar I start at, the first note does not sound. If it's a bar that starts with triplets, the first triplet does not sound; the rest of the score after that sounds as it should.
Advice appreciated.
kph
Comments
Hi there, I still have the same problem, does anyone have a suggestion?
Thanks
kph
In reply to Hi there, I still have the… by kphunter
Oh thank goodness I'm not the only one having this problem!! I've noticed this too and it's SOO aggravating because I stream my cello playing on Twitch and now that I have Musescore 4, trying to play along to my Musescore stuff won't go smoothly! >:( I'm right there with you hoping for an official solution/update or something from the Musescore folks!
This seems to be a common issue. I've found if you click on the note you want to start playback from then wait a couple of seconds before starting playback it reduces the chance of this happening. In contrast if you rapidly play and pause the score or rewind the score then begin play back within a short time it will increase the likelihood of this issue happening.
In reply to This seems to be a common… by Whitefang165
Oh weird! Hmm I tried that and it doesn't help a wink, but I appreciate that you shared that possible workaround - hope it works for others, at least until some official patch/update comes out!
In reply to This seems to be a common… by Whitefang165
Thank you, pressing rewind then play works for me. Hopefully this will be properly fixed soon.
All the best
KPH
Hi, I'm a new user and I have the same issue. Hitting rewind before pressing play helps when you want to play from the start of the score. (I've mapped that to a shortcut Ctrl + Space to make it less inconvenient) but the issue remains if you try to play from somewhere else in the score.
As a workaround, you can try clicking on some element just ahead of the note you want to play back from. For example, I had a point in my score that was preceded by a time signature change. By selecting the time signature and hitting space, the computer acted like I were playing the signature itself and then it played the first note of the following bar.
In reply to Hi, I'm a new user and I… by adamcullenmus
Part of the problem is not having a computer that meets the specs needed to run MU4. Check out what you need on the download page. I was finally able to buy one that more than meets the specs. Play back starts correctly. The only other way to do it is what has been suggested on this thread.
I'm not sure this is something that can, or needs to be "fixed". Maybe sometime. There are other problems that need to be addressed.
I also had this problem, but I found that increasing the buffer size from 1024 to 4096 solved it for me.
On Mac, I updated this in preferences > I/O > Audio > Buffer Size.
In reply to I also had this problem, but… by andrewrgabb
Fantastic! Thanks for that solution. I increased my buffer size by the same amount on my PC and it worked a treat.
I still have this issue in Kubuntu 24.04, even though I have a laptop with a i7-8550U processor and 32 G of RAM, so I thought I had lots of processing and memory headroom. I've discovered a couple of workarounds while working on a piece.
The first workaround is to add a blank measure at the beginning of your piece while you're working on it. (delete it when you're finished.) This allows the piece to play from the beginning without losing notes. (Sometimes, in a score with lots of instruments, you'll still miss some notes, though.)
Another workaround is to use lightweight soundfonts. I use a lightweight Salamander piano when working on a solo piano piece and it can play from anywhere without any problems. I switch to the standard Salamander piano when it's time to render the mp3.
The third workaround is to always render your work as an mp3 to check it: the mp3 render never has the missing startup note problem.
None of these are ideal, but hopefully they help you (and others) make the most of the situation until this bug is fixed, if ever.