Playback Hangs after 2 minims in 1st bar - graphical & playback glitch.
Reported version
4.x-dev
Type
Performance
Frequency
Once
Severity
S3 - Major
Status
needs info
Regression
No
Workaround
No
Project
Enter 2 minims in the 1st bar, enter a bunch of crochets after and then press play.
It hangs on the 1st bar.
I also had the add note thing on while it was playing, forgot if that's a bug too or if it's supposed to be that way.
There also seems to be a graphical glitch too where some of the playback is found around 5 bars away while what's left of the playback is in the first one.
Bug found on Ubuntu 20.04 LTS using the AppImage.
I don't really know how likely it is to happen or anything but it looks important so.
| Attachment | Size |
|---|---|
| BugSS.png | 21.83 KB |
| Untitled.mscz | 8.7 KB |
Comments
In order to investigate, we would need precise steps to reproduce the problem.
I'm guessing, though, that this will turn out to be some sort of conflict with a device driver or other software unique to your particular system. You might try different settings in Edit / Preferences / I/O. Or perhaps an issue with a custom soundfont, if you've installed one.
In reply to In order to investigate, we… by Marc Sabatella
No custom soundfonts or anything. It was just the appimage so no software installed should be an issue to my knowledge. System Info: AMD Ryzen 5 4600H, PopOS/Ubuntu 20.04, Driver: PulseAudio. No MIDI device was connected I was just using the mouse to enter the notes.
I do have Musescore 3, installed while running the Testing Appimage for Musescore 4.
That could be a reason but as far as my understanding goes it shouldn't cause any issues?
The notes entered is screenshotted too if that somehow affects anything.
Any unnecessary drivers wouldn't be loaded in the kernel unless needed to my knowledge too.
I'll look into the settings I had on but I'm pretty sure it was just the defaults so.
Oh wait, I missed that you were testing with an experimental development build. No big surprise if those don't work. So, 3.6.2 works OK?
I see from your image you have loop playback turned on, that could be a factor as well.
In reply to Oh wait, I missed that you… by Marc Sabatella
Yeah I just posted it on here cause I wanted to help get rid of bugs in the new testing build.
I'm guessing this is the wrong place or time to do that?
It doesn't happen on Win10 with the 10/18/2021 nightly build (with or without playback looping).
It might just be a Linux thing.
@benowens9865 Playback was still a work in progress 9 months ago and has gotten a lot better.
I am also not able to reproduce this on a current 4.x nightly macOS build. Can you (or anyone else with access to Linux) please check using a current 4.x nightly build if you are still experiencing the issue? If not, pls close with Status: fixed.