Dynamics tool misbehaving
When I open the occasional piece I have Saved in Muse, some of them have suddenly quit obeying the dynamic markings and will increase/decrease volume arbitrarily. They did not do this when I first created them, before I Saved them. I have tried putting "pianissimo" markings under four notes in a row: Keeps on playing "forte" or whatever volume it has chosen. Does not seem to be related to dynamics or hairpin markings. If I Save the piece and put it away, get it out in a day or two, the problem is still there. My computer is Windows 7 and the Muse program is 2.0.3, as per your request for systems info. I have tried Copy and Paste onto a New page, but the problem came along with the paste. Then I tried this (labor-intensive) thing: Copy the whole piece onto a New page, note by note. The new one is fine. I have also done this: I Add/insert about 6 blank measures just ahead of the defective area, Enter the notes of, say, the first 3 measures of the defective section, then Delete the extra blank measures (have to have them as a buffer) and, at the same time, Delete those 3 original measures (that I hand-copied) of the defective area, put in the proper dynamic markings and that seems to work, sometimes. But at other times, it will play fine for the parts I hand-copied and then when it gets to the part I did NOT copy by hand, the original measures of the defective piece, it reverts to going haywire with the volume. Any way to persuade it to follow my directions?
Comments
You should upgrade to 2.1, even if this probably is unrelated.
And without seeing the score (the mscz file) we can't help here.
In reply to You should upgrade to 2.1,… by Jojo-Schmitz
Hi, thanks for your reply. I am reluctant to upgrade to 2.1 because I read that the later version(s) does/do not have the capability of taking the Lame file that allows pieces to be turned into MP3's, which is a feature I really like. Someone else suggested that the problem might be the Velocity Offset and something else to do with Velocity. I checked in F8 but it turned out that they were already set as per that person's suggestion. (These might have been ones I imported from Allegro, as many of those looked like they were run through a blender and needed a lot of fixing. But once they were fixed, they played fine. It was only after I Saved them that the glitch showed up.) I will see if that person has any other suggestions (or if you do) along those lines first before I try to figure out how to send a chunk of the piece where the errors occur. Beth
In reply to Hi, thanks for your reply. … by Beths
2.1 works with lame_enc.dll the same as all other 2.x version. 2.2 will even have it included by default. For Windows, that is.
It sounds very much as though the notes have a custom velocity set. This happens regularly if you start off with importing a MIDI file.
Try to select all notes and in the inspector (F8) make sure the Velocity type is set to Offset and the Velocity is set to 0
In reply to It sounds very much as… by jeetee
Thanks for your reply. When I hit F8, and get "Inspector", the Velocity Type is already at offset and the Velocity is already set to 0. And I think you are correct that this was one of the pieces I imported from Allegro, so it might well have been a Midi file, all of which translated over very poorly. But this glitch is not showing up in very many of them, only in 3 or 4 of about 20 pieces. (If it matters, it would not let me Select all of the notes-- that tall window of all those selections would not come up unless I Selected only a part of the piece, so I just Selected 2 lines of it.)
In reply to Thanks for your reply. When… by Beths
You can select all the notes using Ctrl+A and then in the inspector click the notes button at the bottom.
I'm unsure of which value the inspector shows in these fields if you have multiple notes selected and only some have those properties changed.
Just to make sure, try changing them from Offset to User and from 0 to 1 and then change them back.
If that doesn't fix it for you, please attach a score showing the issue (or just the measures from it having the issue by deleting all other measures).
In reply to You can select all the notes… by jeetee
OK, with a bit more finagling, that did the trick. Here is the finagling part: When I hit Ctrl+A it selected all the notes but the window with all the choices would not come up so I deselected the last measure (which has some grace notes, if that matters). Then I did the User/Offset and 0/1 switch and back again. Now the glitches were all gone but it would not play the last measure at all. I tried deselecting the first meas., then the first line, then several lines, finally deselecting all but the last 2 lines and deleting the grace notes, for good measure, did the User, etc. thing again, added the grace notes back in and it all plays perfectly. Thank you!! Beth
In reply to Thanks for your reply. When… by Beths
If you select multiple notes, you will get the value of one of the notes in the inspector such as Offset and 0 while other notes may be set at another value. To the right of both the Offset and the 0 there are counterclockwise arrows. If either of them are black, you can press them to reset all of the selected notes to the default values (offset and 0).
Another way to test that you did not stumble upon a note with no change is to select a single note you know plays incorrectly and look at its value.
In reply to If you select multiple notes… by mike320
Thanks, the problem is solved-- I fiddled with the Offset/User ancd Velocity choices, selecting and deselecting measure/lines, deleting grace notes in one measure and it finally worked perfectly. Thanks for your input.
Beth