Caesura Playback Issue (in Muse4)

• Dec 20, 2022 - 20:58
Reported version
S3 - Major
GitHub issue
  1. Create score with piano (I am using musesounds playback)
  2. Add caesura to music
  3. Play music

The sounds will continue to play while the music should be stopped, then once the music gets going again they stack on top of each other.


Frequency Few Many

addendum: if I save and reload, the caesuras play correctly. The next one I add is ignored, but if I save and reload it plays correctly. At this point I have nine caesuras and nine reloads which is "many"

Frequency Few Many

I am guessing this is an artifact of the new interpretation software... I am using Muse Sounds... in Muse3 caesuras are always honored

For the record, "frequency" is how often a bug is reported; "reproducibility" is how often it occurs for those people who have reported it. This information is present in the FAQ article that appears when you click "read the instructions" upon posting a new issue. I suppose it would be good if that link was also presented when commenting on an issue. But I also think this issue tracker is likely to be retired in the not-too-distant future.

Status active duplicate

In any case, a number of reports of caesura playback issues already exist on GitHub, so I'm closing this one as du0licate (search "caesura" on GitHub issues to find them, there are several).

Same issue here. Using Musescore V4 and Musesounds. It stucks somehow, but does not pause at all. Issue still not resolved, right?

Workaround No Yes

As per @Marc Sabatella:
The pause is honored after the playback info is regenerated - save/reload, for example, but also any edit that changes the playback.

Regression No Yes
Severity S4 - Minor S3 - Major
Status PR created active
Reported version 4.0 4.x-dev
Workaround Yes No

MuseScore 4.1 was fine, but with 4.2, placing a note immediately before a caesura or section break causes that note to sustain (instead of pausing)

Severity S3 - Major S4 - Minor
Status active PR created
Reported version 4.x-dev 4.0
Workaround No Yes

That's a separate issue and also being dealt with

Severity S4 - Minor S3 - Major
Status PR created GitHub issue
Reported version 4.0 4.x-dev
Workaround Yes No

This is already reported on GitHub, so no need to open a new issue. But also, definitely no need - ever - to respond to issues here in this obsolete tracker. The original bug discussed here, btw, is unrelated to the new one, but the original one has a pending fix.