You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Task description
I was looking through my older scores in MuseScore 4 and wanted to hear how they sounded with MuseSounds. I opened up a piano piece that had the two hands playing different dynamics. When I played it, both hands used the same dynamics instead of each hand having different dynamics.
In MuseScore 3, I could fix this using the "Dynamic Range" property. In MuseScore 4, I either cannot find that property, or it doesn't exist. I would assume it would be under the "Playback" settings in the Properties pane, but it is grayed out. I'm sorry if I'm wasting your time and that the solution is that I cannot find the setting, but I truely have no idea how to do this.
I should also note that I am using the Keyboard Muse Sounds while playing back the music. I'll attach the MuseScore 3 file, along with the MuseScore 4 file I got when I saved my score with new engraving. Thanks!
Task description
I was looking through my older scores in MuseScore 4 and wanted to hear how they sounded with MuseSounds. I opened up a piano piece that had the two hands playing different dynamics. When I played it, both hands used the same dynamics instead of each hand having different dynamics.
In MuseScore 3, I could fix this using the "Dynamic Range" property. In MuseScore 4, I either cannot find that property, or it doesn't exist. I would assume it would be under the "Playback" settings in the Properties pane, but it is grayed out. I'm sorry if I'm wasting your time and that the solution is that I cannot find the setting, but I truely have no idea how to do this.
I should also note that I am using the Keyboard Muse Sounds while playing back the music. I'll attach the MuseScore 3 file, along with the MuseScore 4 file I got when I saved my score with new engraving. Thanks!
MuseScore Files.zip
The text was updated successfully, but these errors were encountered: