Pedal markings and dynamics not carrying over from score to individual part
Reported version
4.0
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
needs info
Regression
No
Workaround
No
Project
The pedal markings I entered the attached score for the vibraphone 1 part are not carrying over to the individual part. All of the pedal markings are gone but you can see the issue from m1 - m6 for example.
| Attachment | Size |
|---|---|
| Yamanashi Blues - M4 - 011823 - 01.mscz | 395.77 KB |
| Screen Shot 2023-01-18 at 3.45.39 PM.png | 272.11 KB |
| Screen Shot 2023-01-18 at 3.45.24 PM.png | 330.41 KB |
Comments
If I delete from the score and then re-enter, the marking shows up in the individual part. At this point I either have to adjust on the score or the individual part. Either way, it's creating extra steps.
I updated the name of this post because I also noticed that crescendos are not carrying over as well. That would include both the graphic crescendo and the cres------ style.
The crescendo markings not transferring to individual parts happens with all parts, not just the one vibraphone part, so I did produce the error multiple times within this piece.
In general, if you add an element to the score, it should appear in the part, and normally it does. I have seen one or two cases before where this seems to not work. Can you provide precise steps to reproduce the problem?
Basically I added the pedal markings and dynamics when writing the score. All pedal markings and dynamics were complete. I was then ready to generate the individual parts. I simply clicked on parts at the top middle of the screen, chose which part I wanted. When I did Vibraphone 1, all of those elements were completely missing.
So, can you post a version of a score from before the problem appears, then give precise steps to reproduce the problem from there? I can't reproduce this now, but I do believe you, as I have seen it happen once for twice in over the course of the course the past few months I've been working with MuseScore 4. We just need precise steps to reproduce the problem since it obviously doesn't happen all the time.
I will see if I can find a previous build of the score and generate a part to see if the problem replicates. I’ll do that and post here asap.
Marc,
Here is a version that seems to work correctly when generating parts.
As far as steps, there’s really only a few. Click on parts, click on Vibraphone 1. That’s it.
If I open your updated score, then click Parts, then click vibraphone, I'm still in the dialog, so I assume you mean I then should also click Open Selected, then examine the newly generated part? If I do that, I see pedal markings, dynamics, and hairpins where I expect, although I didn't inspect every single one. Is there a particular measure I should be looking at to see the missing hairpin? I also tried deleting the one in measure one from the score and re-adding it, then viewing the part, but that worked as expected also.
So the question remains, what steps would I need to do starting from here in order to reproduce the problem?
Yes that’s correct in opening the part. My apologies for leaving out a step.
As for where it’s missing in the more recent version, none of the pedal markings, or crescendos/decrescendo transfer. It’s not just one place, it’s the whole individual part.
Hmm, are you sure you're talking about the file you just uploaded? Here's what I see when I follow those steps:
If you see something different, could have something to do with a difference in behavior if you've just loaded the score versus when you've had it open for a while and been working on it.
The original file is the problem. 011823
The older one I just uploaded works fine. 011623
On the newer one at the very beginning of the piece I added the pedal marking in the vibraphone one part because it was missing. I added it by deleting it off the score and then entering the pedal and decrease in again.
In reply to The original file is the… by brandonhbrooks
Decrescendo
Right, so again, what we still need are steps that get from a working version to a non-working version. The original file already has the problem. The question is, how did it occur? Once we know steps to reproduce the problem from scratch - from a score that doesn’t already have the problem - then an investigation can begin into why those steps cause a problem.
There are two versions in this thread. The version I uploaded today (011623 - older version) doesn't have the problem.
The newer version (011823 and first upload) does.
I took video of the steps (identical on both) but cannot upload the video. Is there a way to send it to you?
Again, I understand that the first score demonstrates the problem. That is because it is already corrupted in this way. What we still need is a precise step by step procedure we can follow to take the second uncorrupted version of the score and get it into the same corrupted state that the first score is in. A video won't be as helpful as simply listing the steps - it's way easier to follow written directions than to try to follow along with exact what is happening in a video. But, once you have those clearly written steps, if you wish to show a video demonstration as well, just upload to YouTube or elsewhere and post the link here.
I'm guessing at this point it's going to be next to impossible to retrace the steps and figure out how to produce the corruption starting from that uncorrupted version of the score. Probably better to see if you can reproduce this in a totally new score, and post those steps.
Again: we would need a score that has no corruptions, and then a precise series of steps we can follow that then gets it into the same corrupted state that your first posted version is in.
Once we have those clear steps, then an issue can be opened on GitHub so the developers can begin investigating.
I imagine the steps to be too numerous as there were minor changes in many different parts. I doubt at this point there is any way to retrace all of those steps.
Indeed, which is why I said it's probably going g to be next to impossible to figure out in this score. If it ever happens again, maybe you'll be able to recognize the connection - something you remember doing in both of the scores that seems like it could somehow be related. And then ideally you'd to test your theory by trying to reproduce the problem in a brand new score.
Unfortunately it's often a bit of a struggle to figure out how to reproduce problems. But you're in a much better position to be able to do that than someone who has no idea what steps you might have undertaken. And there are plenty of other bugs that do have clear steps to reproduce that the developers can tackle meanwhile, so no need to continue beating your head against this particular problem at the moment. Eventually, I have no doubt that either you or someone else will stumble upon the steps to reproduce, and then this issue can be handed over to the developers.
Marc,
I had this same thing happen again with a different score. On this particular score the Vibraphone 2 part didn't carry over the pedal markings or crescendo/decrescendo's
I've posted a few other recent issues and am trying to include all steps. I will post steps back to when I generated parts and there was a naming issue.
Starting SAVE; Punta_Patri Musescore 4 - 012323 - 01 - SCORE
Most recent SAVE: Punta_Patri Musescore 4 - 012423 - 01 - SCORE
I will include (what I hope) is every single step between these two versions below this post.
Start - Punta_Patri Musescore 4 - 012323 - 01 - SCORE
SAVE AS
Punta_Patri Musescore 4 - 012423 - 01 - SCORE
1 m4 dynamic change to mp in Tenor part
2 Delete Percussion (top staff)
3 Hide “Violins 3 Playback Only” in Instrument Palette
4 Hide “Violins 4 Playback Only” in Instrument Palette
5 Hide “Chimes” in Instrument Palette
6 SAVE
7 Open Parts Dialogue (top of UI)
8 Delete Chimes in Parts Dialogue
9 Delete “Violins 3 Playback Only” in Parts Dialogue
10 Delete “Violins 4 Playback Only” in Parts Dialogue
11 Delete “Crotales Playback Only” in Parts Dialogue
12 SAVE
13 CLOSE Musescore (to check for crash / errors)
14 Re-open Musescore
15Close Mixer
16 Open Instrument Palette
17 Open Parts Palette
18 In Parts Dialoge (top of UI) rename “Tenor” to “Voice”
19 Rename the second “Vibraphone 1” part to “Vibraphone 2”
20 Rename the second “Vibraphone” (no number) part to “Vibraphone 3”
21 Rename “Mar 1” to “Marimba 1”
22 Rename “Marimba Grandstaff” to “Marimba 2”
23 Rename “Mar 3” to “Marimba 3”
24 Close Parts Dialoge
25 SAVE
26 CLOSE Musescore (to check for crash / errors)
27 Re-open Musescore
28 Delete 2 measures of rest at beginning of piece
29 Open Instrument Palette
30 Rename “Tenor” to “Voice” & abbreviated name to “V.” - THERE WAS A LARGE AMOUNT OF LAG TIME HERE
31 Rename “Marimba 2 / Vibe 3” to “Marimba 2” and abbreviated name to “Mrm. 2” - - THERE WAS A LARGE AMOUNT OF LAG TIME HERE
32 SAVE AS file as new name: Punta_Patri Musescore 4 - 012423 - 02 - SCORE
33 CLOSE Musescore (to check for crash / errors)
34 Re-open Musescore
35 m26 change dynamic in “Voice” part from p to mp
36 OPEN PARTS DIALOGUE AND NOTICE ERROR - Part name changes did not save in parts dialog. Part name changes in Instrument Palette did save.
Update: I went through the following steps again with the same results of the part names not saving the change in the Parts Dialogue
18 In Parts Dialoge (top of UI) rename “Tenor” to “Voice” 19 Rename the second “Vibraphone 1” part to “Vibraphone 2” 20 Rename the second “Vibraphone” (no number) part to “Vibraphone 3” 21 Rename “Mar 1” to “Marimba 1” 22 Rename “Marimba Grandstaff” to “Marimba 2” 23 Rename “Mar 3” to “Marimba 3” 24 Close Parts Dialoge 25 SAVE 26 CLOSE Musescore (to check for crash / errors) 27 Re-open Musescore
OPEN PARTS DIALOGUE AND NOTICE ERROR - Part name changes did not save in parts dialog. Part name changes in Instrument Palette did save.
Update:
1 Reopen Musescore 2 Generate "Tenor" individual part. 3 Change "Tenor" in Parts Dialogue to "Voice" 4 Close Dialoge 5 Close "Tenor" part 6 Re-open and name change is save on individual part and on Parts Dialogue.
I did this for all parts and the name changes saved. However, when closing Musescore with all parts and score open, upon reopening the Glock / Crotale part doesn't automatically open even though all other parts do. It will open manually.
Saved as: Punta_Patri Musescore 4 - 012423 - 03 - SCORE
01/25/23
Numbering on score adjustment
set X to -1
Same on “Voice” part
Apply to all parts
SAVE AS: Punta_Patri Musescore 4 - 012523 - 01 - SCORE
On Score:
Format - Style - Measure Numbers
Position Above X change to -1.0sp
Position Above Y change to -1.5sp
Same on “Voice” & Apply to all parts
SAVE AS: Punta_Patri Musescore 4 - 012523 - 01 - SCORE
Format - Page Settings - Staff Space
Change to 1.5mm
Apply to all parts
Format - Style - Page -
Min. System Distance change to 15.0sp
Max. System Distance change to 20.0sp
Apply to all parts
Format - Style - Rehearsal Marks
Position Above X change to -0.5sp
Format - Style - Page -
Vertical frame top margin change to 15.0sp
Vertical frame bottom margin change to 10.0sp
SAVE AS: Punta_Patri Musescore 4 - 012523 - 02 - SCORE
01/26/23
Punta_Patri Musescore 4 - 012623 - 01 - SCORE
Format - Style - Page -
Music Top Margin - change to 15.0sp
Music Bottom Margin - change to 10.0sp
Apply to All Pages
Format - Style - Tempo Text
Position Above - Y -3.50sp
Apply All
SAVE
Adjust Staff Text on Glock/Crotales part
Vibraphone 3 - flipped accents to top and corrected spacing
SAVE AS: Punta_Patri Musescore 4 - 012623 - 02 - SCORE
Marimba 1 - Hide Bass Clef staff on score
Marimba 2 - Hide rests in Bass Clef where not needed
SAVE
Timpani - replace repetitive parts with repeats
SAVE
Add notes to Voice part to score at end
Move Fermata on Score
Move Fermata on Voice part
Add ties
Add diminuendo
Add system breaks to Voice part
Hit Return at G to move to next system
SAVE
Hit Return at I to move to next system
SAVE
Increase Stretch 67 to end 10 times
SAVE
NOTICED Vibraphone 2 missing crescendo/decrescendo and pedal markings
Punta_Patri Musescore 4 - 012623 - 02 - SCORE
@Marc Sabatella I tried to document as many steps as possible. I'm noticing now that it wasn't just the Vibraphone part that was affected by the decrescendo/crescendo markings missing. The Marimba 1 and Marimba 2 parts were affected as well so there is definitely and issue with the transfer of those markings.
That's quite an exhaustive list - thanks for doing that! Now, the real trick will be spending time figuring out which of these steps are the actual relevant ones - to reduce it down to just the steps needed to reproduce the problem.
Also rests that were made invisible on the score are not invisible on the Marimba 2 part.
In reply to That's quite an exhaustive… by Marc Sabatella
You’re welcome. I live the program and really want to see the glitches worked out. In the meantime some things are twice the work.
It's by design and an important feature that it's possible to control the visibility of elements independently for score and parts.
In reply to It's by design and an… by Marc Sabatella
Ahhhh. Makes sense now. Thank you.
In reply to Start - Punta_Patri… by brandonhbrooks
Hey Brandon, did you log all these actions manually, or did you use an app? I'm consistently getting the same bug, and I'd like to log my work in the same manner if possible.
In reply to Hey Brandon, did you log all… by Antoni Schonken
Hey. I'm sorry I'm just now seeing your question. It was manually. Tedious but it got the job done.
@Marc Sabatella So I corrected the pedal markings issue and dynamics that were missing by going back through the whole score and deleting and replacing. That corrected everything. I do not remember what changes I made but between 020723 - 01 and 020723 - 02 all of those corrections went away again. At this point I'm furious because its causing hours of extra work that randomly happens. I noticed when I did another save as today 021023 - 01 and the dynamics / pedal markings were gone on the vibe parts. I had to go back 2 saves to find where the marking actually stayed on some of the parts.
I hear you; it's definitely frustrating. There are a few other similar seeming reports over on GitHub and elsewhere but so far I don't think anyone has figured out the precise steps to reproduce the problem. If someone can do that before 4.0.2 is released, I'd expect to see it fixed there. Not sure how much longer that will be, but my guess is we're talking days or a small number of weeks at most.
I was hoping the extensive list above would help find the trigger for the issue.
Please understand that we are all dealing with many issues here and doing our best to help, but realistically it's just much easier for the person who is actually experiencing the problem to find the precise steps. I mean, it's not going to be easy for anyone, but armed with your own extensive list, you can start narrowing it down by say, omitting half the steps and seeing if the issue is still reproducible, etc. And it's easier for the person who is experiencing the problem to do this, because you know exactly what you mean in each of those steps. It would take someone else much longer to even understand the steps, and we are all just volunteers here.
So again, once there is a clear, direct, and precise set of steps to reproduce the problem without a lot of unnecessary extra steps to figure out, that's the point at which it makes sense to report to the developers. Because they have their hands full as it is too.
@Marc Sabatella I completely understand about having their hands full.
An interesting find on the Parts of the 021023 - 01 save. If you click on Parts and look at the list (scroll down) you'll see 2 Crotales parts. I didn't add those and when you open them they are blank. MuseScore keeps adding random parts. Also the missing dynamics/pedal markings that disappear are almost always Vibraphone parts. Also in a previous discussion you mentioned that there were 7 Crotales parts (which I did not add) so perhaps it has to do with Crotales and vibraphones specifically. I don't know if that helps but hopefully it will.
For the parts that are being added, here again, precise steps to reproduce the problem are what is needed. It's conceivable that is related to the problem at hand, but more likely it's a separate issue.