Musescore: can not delete

• May 14, 2010 - 07:02

... just upgraded to latest build ... (on ubuntu hardy)

not sure whether this interest anybody: if not, would you mind commenting and i will keep quiet ... :-)

for the life of it i can not delete any erroneous notes. neither with del, backspace, nor ctrl-x. after hitting del i have to hit N twice to be able to do anything at all again, and then the cursor jumps to the beginning of the score.

should i better go back to 9.5 ?

error messages on start up are the following ...

... and no, i can not play my scores, but would that have anything to do with the problem above ? likely not.

the sound issue, i will figure out eventually, i am sure ...

Suspending PulseAudio
ALSA lib confmisc.c:768:(parse_card) cannot find card '0'
ALSA lib conf.c:3513:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:3513:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name
ALSA lib conf.c:3513:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:3985:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM default
Alsa_driver: Cannot open PCM device default for playback.
init ALSA audio driver failed
init ALSA driver failed
init audio driver failed
sequencer init failed

ingo


Comments

To delete measures please read New features in MuseScore 0.9.6 , "Important information for people upgrading from older versions".

Deleting individual notes works the same as version 0.9.5. To delete a note (and turn it back into a rest) you have to select the note and press delete. You can also replace wrong notes with new notes in note entry mode. See note entry in the handbook for details.

In reply to by David Bolton

O.K. thanks for the reply. That is good to know.

But i was not even trying to remove a measure, just single notes. I verified my approach to deleting single notes with the "promenade" and there it works, just in my own score it would not.

I deleted the last three measures in xemacs, but then, when I generate a new measure and add a single note, after hitting "a" for my next note, mscore adds an a stretching over 3 measures ... oh my ...

Exporting it to .xml and re-importing would not fix it. Now I exported to .mid and opened in Denemo, and, my ... the score has some 30 measures and Denemo tries to import over 2000 before I kill it. Uh oh ....

Ingo

... i have now banged my head against this and can't seem to be able to continue.

Attached screenshots of the smcx file after opening and after trying to add the next note. The only thing happening between the two screenshots is me hitting the "a". What comes out does not seem right.

If some kind soul can try this on their installation. Maybe it is just Ubuntu 8.04. Mscore is latest stable (9.5).

Clearly my score must be corrupted somewhere in there. Starting over does also not seem like an option, unless I know this will not happen again ...

Ingo

Attachment Size
d1.png 262.93 KB
d2.png 263.43 KB
Django.mscx 32.38 KB

In reply to by ipk

I opened your score in r2811, XP.

1. As your score ended with no bars after the notes, I first appended 8 bars. What appeared is in the attachment, Django1 - 8 bars as an 8 bar rest.
2. I tried to delete the 8 bar rest - I selected the bar and tried to delete it. it turned into a 7 bar rest. I continued through 6, 5 etc. until there was only one bar.
3. I then tried to add a quarter note "A". The result is attachment 2.
4. I then undid the last few steps until a 2 bar rest was back.
5. I then tried to delete it again, and the result was attachment 3.

No real help I'm afraid.

Regards,

Attachment Size
django 1.png 144.39 KB
django 2.png 175.59 KB
django 3.png 158.59 KB

In reply to by xavierjazz

The latest revision shows some weird rests in the last measure. The last two or three measures are somehow confused. You should delete them and try entering again.
Maybe this has to do with the "create multi measure rests" style flag you have set. You should reset this flag when editing.

In reply to by [DELETED] 3

I went through the whole score and deleted measure by measure (in xemacs).

Attached is the score containing the faulty measure.
Adding a new measure here and inserting a note creates weiredness.

Truncating the attached score back in the editor by one measure allows adding a new measure in mscore and notes, and things seem to look o.k.

The relevant measure looks just fine to me, also in the editor. But I am not quite fluent in mscore speak, so i might miss something ...

What could that be ?

Ingo

Attachment Size
Django3.mscx 17.27 KB

In reply to by ipk

It sounds like you upgraded to 0.9.6 prerelease and then downgraded to 0.9.5. If you saved any of your scores in 0.9.6 then they are no longer editable in 0.9.5 as I mentioned in my comment above ("important information").

Occasionally people have shared scores on the forum that were corrupted using only 0.9.5. However they have not given step-by-step instructions for developers to reproduce the corrupt measure starting from a new score. See http://musescore.org/en/handbook/how-report-bug-or-ask-support

In reply to by ipk

ipk, Exporting to MusicXML from 0.9.6 and then re-importing the MusicXML in 0.9.5 would work. Maybe the file was corrupted for another reason. If you discover the steps starting from a new score that cause the problem please share.

In reply to by David Bolton

you are right ... there were a few 6 digit ticks and 6 digit ticklengths in the file that likely cause the 3000 page midi import into denemo. i also edited these out, when i ran into trouble again in measure 34 or so ...

will keep my eyes open ... but it is running well for now ...

ingo

In reply to by David Bolton

I think I did not quite grasp what "not editable" means. After all, it is not that it could not be opened. Just can not be edited. And going via xml or even midi would not rescue it.

I could now rescue the score by generating a new one and via text editor inserting the finished measures, Easy enough and fair with me.

(b.t.w, what i thought above would fix it, did not in the end. even after truncating back to 1 measure weiredness would still come up in measure 18 and always and only in measure 18 ... that is when it began to dawn on me what you meant with altered structure and not editable ... :-)

1000 thanks to everybody for taking their time. Hopefully the discussion will not have been completely in vain for the rest of the community.

Ingo

Do you still have an unanswered question? Please log in first to post your question.