Loudness suddenly changes without dynamics
The first two measures in the attached file show that the last eighth note of the first measure produces a sudden increase in loudness (instrument: violoncello solo, muse sounds).
The other measures show that this change depends on the pitch of the note of that last eighth note.
The system is MuseScore 4.2.0-233521124, revision: eb8d33c, running on Windows 11
| Attachment | Size |
|---|---|
| Loudness.mscz | 18.46 KB |
Comments
Also, if you move it down to start on an F, it isn't as bad. Shouldn't happen, I know. So Muse sounds is trying to interpret the phrase. I recall they wanted to do this so that we wouldn't need NotePerformer. Doesn't always work
In reply to Also, if you move it down to… by bobjp
Perhaps for such a short piece starting on an F will minimize the problem, but in a full score, if you start on an F the problem will appear in another fragment, especially when it also happens with other instruments, or with voices.
So, two scores are necessary: one, which will be the published one, with the indications of the true dynamics of execution, and another, necessary while it is being composed, to correct the dynamics that Muse Sounds enter on its own when trying to interpret it. It is unfeasible.
Sorry, but I think that the bug is bigger than only a question of interpretation by Muse sounds.