Beaming notes from multiple measures across system break leads to crash

• Sep 13, 2020 - 01:11
Reported version
3.5
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project

In the attached file, I have attempted to select the pedal (Led) marking in measures 27, 28, 29, 30 -- but when one attempts to select any of these pedal marks to highlight them and then render them not visible, Musescore selects the beams on the crossbeam measures of measure numbers 30 and 32. If one then uses the cursor to touch these beam lines, the program will crash (every time in my experience). Sometimes too when I select the pedal markings in measures 27, 28, 29, 30 -- this too will cause the program to crash. Any advice is deeply appreciated. I have attached the file herewith. Dan Bradford

Attachment Size
Scarborough Fair TWO.mscz 42.48 KB

Comments

Frequency Many Once
Type Performance Functional

I saw everything you did in this except the crash only happened when I tried to drag the beam in 30 or 32.

In reply to by mike320

When you try to highlight the pedal marks in measures 27, 28, 29, 30 in order to render them "not visible" using the inspector -- instead of the LED pedal marks getting highlighted...the beam in measures 30 and 32 highlight. Then, if you try to mess with those beams in either measure, CRASH. I've even tried to erase everything in measure 32 for example and start over but then when I tried that I get all KINDS of strange beams going all over the place and it's just not workbable. I'm pretty fluent at Musescore but this one has me totally stumped. I don't want to have to redo tons of measure to get rid of the problem -- thanks for any insight you have.

Attachment Size
Scarborough Fair TWO.mscz 42.52 KB
Title Cross beaming causes multiple problems and crashing Beaming measure from multiple measures across system break leads to crash

I've now managed to fix the score. Here's what I did. In measures 31 & 32 I selected the first notes and set the beam property to "Beam Start" In your copy these were both set to beam middle. MuseScore got confused and thought this was one long beam (which it should be) but displayed the 3 distinct beams that looked normal. This is a bug and I've changed the name to indicate the problem.

I then deleted the second pedal (Ped not Led) under measure 27. They're stacked so it looks like one darker one.

You said "if you try to mess with those beams" it crashes. More specifically if you try to drag the beams it crashes, which make this a critical issue.

A fixed score is attached.

Attachment Size
Scarborough Fair TWO_0.mscz 41.66 KB
Title Beaming measure from multiple measures across system break leads to crash Beaming notes from multiple measures across system break leads to crash

Better title.

In reply to by mike320

Thanks so much for your kind help. Yes I would NOT have noticed that the beams APPEARED normal but in fact were not "Beam Start" which of course I had to use regularly throughout this transcription. I've now been able to properly render "not visible" the Ped. markings and it no longer plays with static noise and issues that also seemed to be part of the problem. I have a few more minor changes I need to make but will then upload. I appreciate your highlighting the problem though to the Musescore team. Again kind regards and thanks, Dan B.

What clued me in was that the drag boxes on the beams were so far apart, acting like the beams were much longer than they are. I also know that beaming across a system break was disabled in the 3.5 update so I knew there was the possibility that the m32 beam was a middle beam. When I fixed that one, the m31 beam showed itself to be attached to the previous measure also.