[1.2 pre-release 2] Non-removable courtesy clef appears after insert measure before first one
Win XP
Revision 2839
To reproduce fault
Open wtc1fuga5 example score
Select 1st measure, treble clef
Create/Bars/Insert measure
Expected. Empty measure at start of score
Actual Result
Empty measure at start of score
Stray unnecessary Bass clef symbol in bar 2 of second staff
The stray staff cannot be changed, cannot be deleted, cannot be hidden and is not influencing the notes on the staff
(This can be shown by dropping a treble clef on top of the bass clef in measure 1 of staff 2, when the notes on staff 2 will be seen to respond to the clef change in measure 1
Comments
Thought I'd just give it an update :)
1. Create piano score.
2. Enter notes.
3. Apply 8va bass clef to the bass clef at the beginning.
4. Select first bar.
5. Insert measure.
Using MuseScore 1.0 - Mac 10.4.11: A courtesy clef appears in the second bar - nothing can be done to change, move or remove it (setting it invisible appears to be, at least, the one thing possible).
Using MuseScore 2.0 nightly build (4303) - Mac 10.4.11: Crash. Check once this is fixed: #4184: [Trunk] Crash when inserting a measure before the first one
Change title
This is still present in v1.1 on Windows 7
This is still present in 1.2 pre-release 1 Windows 7 64 bit
Using home-compiled 1.2 R5420 under Win7 32-bit. I don't see this issue.
I do - did you follow the instructions in #1?
I can't see it in the trunk - can anyone confirm?
Using MuseScore 1.2 (Pre-release 1) - Mac 10.6.8.
Yes I did, twice, in different locations (home r5420, work r5421, both Win7 32-bit v1.2). Here's the before and after pix to prove it.
@schepers: the attachments don't work..
Web folks, please fix the file attachment/upload for the web site. I don't attach files too often because usually they simply don't work. This time when I attached my screen shots everything looked fine, no error messages, so I saved the posting, only to find the attachments are nowhere no be found. Only when I use the back button of the browser do I see an error message:
"The selected file could not be copied, because no file by that name exists. Please check that you supplied the correct filename.
The selected file could not be copied, because no file by that name exists. Please check that you supplied the correct filename."
I will try again.
Second try at attaching.
Step 3: Apply clef, not line.
Ah, yes I see the issue now. A mini version of the bass clef.
Fixed in r5422
Absolutely confirm chen lungs finding with comment #1
This is completely repeatable from a new score.
My original bug report re wtcfuga5 , still shows the fault.
Further experimentation shows that this does not happen with all files however, it does happen with several of the demo files when inserting a new measure before measure 1. It happens with these files at least:
wtcfuga5, adeste, Estudio-No1-Tarrega
With the Tarrega demo, you also get a stray courtesy treble clef in the upper stave just for good measure (or not, if you see the irony)
1.2 pre-release 1 win 7 64 bit
Still fixed in r5422. We'll have to take lasconic's word for it, or prove otherwise
I think my posting has cross posted with lasconic's fix and changed the status back to active.
Presumably its fixed...
Oh, OK.
I've updated the Release notes meanwhile ;-)
Now that Chen corrected my one faulty step, the patch Lasconic submitted for r5422 does seem to fix this.
1) Open demo sonata16
2) Select 1st bar of right hand
3) Create bars/insert measure
Expected - blank measure inserted at start of score
Actual - blank measure inserted at start of score
-Notes in measure 5 (after insertion), beat 4 of left hand move to new positions
as though they are now notated on a bass clef (there is no new clef visible at beat 3 of measure 5)
-The left hand of system 2 has changed to bass clef
All quite similar to the original bug report, except the corruption has moved further into the score
Musescore 1.2 pre-release 2, win 7
Confirmed BarryB's bug with a new score.
1. Create a new default piano score.
2. Drop a treble clef over the bass clef in the first system.
3. Drop a bass clef in the 4'th measure, bottom line
4. Add some notes to both clefs, including the 4'th measure.
5. Select measure 1 and press INSert to insert a new measure.
The bottom line will now show the notes in the 4'th measure as being in the bass clef, even though the bass clef moved forward to measure 5.
Confirmed using prerelease 2 on Vista. Notes appear as if in bass clef even though they are actually in treble clef.
I'm pretty sure I remember seeing something almost identical to this posted in the forum or issue tracker a few months ago, suggesting a) this is not a regression and b) it is not as common a problem it might seem like it would be. Still, it seems pretty serious to me.
I think this is the report from a couple of months ago:
http://musescore.org/en/node/14577
See measure 7 of the posted score - top staff displays as treble, but plays as bass.
I reported the keychange bug #12966: 1.1 r4846 Measure insert corrupts key changes where inserting from the first measure would cause the keychange to move forward, but the effect would stay at its original measure.
Still present in the release of 1.2. Since the description has changed quite a bit from the original, should we log this separately?
Here's an easier way to reproduce - create the new piano score, drop a treble clef to the bottom staff in bar 4, add notes before and after the clef change, then select bar 1 and hit Insert. That is, you don't need to do both steps 2 & 3 in schepers' description - a single clef change is sufficient.
Workaround: drop a totally different clef onto that bar (eg, tenor clef), then drop a bass clef back.
Can anyone confirm this bug in a nightly? If not we should close this bug since it's fixed for next version.
I was unable to reproduce in a nightly. Between that and the fact that the description of the bug has changed, I agree this one should be closed, so I am doing so. But I do still think it worth opening a separate issue for the bug as it currently stands for 1.2 (eg, the steps posted by schepers or as modified by me) with a note in the report that it works in the trunk, unless there is a clear policy that we are not to open issues for 1.2 on things already fixed in the trunk.