Easy to verify if you loop a section. Everytime it goes back to the beginning there is an audio pop/crackle.
There must be an audio fadeout (5 to 10ms) at that point to make the audio wave go back to zero instead of popping the speakers. This is really annoying, specially on bigger speakers.
Comments
Hello! I can chime in to confirm that enabling looping does cause a pop/crack/crackle on my speakers. I am using linux with MuseScore configured to use Jack. The crackle happens at the end of the looped region, just before restarting.
The suggestion of fading the audio by a few ms seems like a good idea but I am not capable to implement a fix due to various reasons (ancient, slow hardware, lack of C++ knowledge). It would be lovely to get a fix in for this as it does cause slight frustration as I use the loop feature heavily while practicing exercises.
Is anyone willing to discuss this further? FWIW I can install MuseScore on OS X and see if the crackle is present there. I cannot try on Windows, however, so if someone else could that would be appreciated.
Cheers!
Update: I have tested Version 2.0.0 rev: 6e47f74 on Mac OS X and could not reproduce the pop/clicking.
The version I am using on Linux (where the pop is happening) is Version 2.0.0 rev: 3543170.
Further testing on Linux seems to show that this problem only happens when using Jack.
A workaround is to make sure to "sudo modprobe snd_seq", then restart pc, open musescore and change the I/O settings to use port audio via the ALSA driver.
3543170 is way older than 6e47f74, from July 2013 vs. March 2015. So just upgrade to the 2.0 Release version and check again.
@jojo-Schmitz: Okay now I'm slightly confused.
I have installed the musescore package via pacman on ArchLinux (built from this https://projects.archlinux.org/svntogit/community.git/tree/trunk/PKGBUI…)
That package uses rev: 6e47f (the v2.0.0 tag) and the SHA256 sum matches. However, when I use "mscore --version" it reports: "MuseScore: Music Score Editor; Version 2.0.0; Build 3543170"
Not sure what's going on with that.. any ideas?
BTW, In another thread I am (very slowly) compiling from git HEAD so that I can test with the bleeding edge version.
OK, maybe the packager didn't update the revision.h for some stupid reason. This really shouldn't happen and should get reported to them.
I believe they are missing a 'make revision' in their build
I have reported that particular issue to the package maintainer. Thanks for the help there.
I'm trying to reproduce the problem with MuseScore 2.0.2 without success so far. Can anyone confirm that it's still a problem? With a score and exact steps to reproduce?
Is this issue a duplicate or not? https://musescore.org/en/node/72326
File: loop.mscz
Closed due to inability to reproduce. Please report, with precise steps to reproduce, in a new thread if this still troubles you in the latest version (3.4.2).