Score created using a mouse to place notes doesnt match the midi nor the XML file also rest problems.

• Apr 19, 2013 - 20:55

I have had this problem since version 0.9 of the software.

When inputting the notes manually everything on the page looks correct. (see picture - Untitled1.jpg).

When I export to Midi or xml to use in Cubase I get unusual sounds.

On check the midi track in Cubase I notice loads of erroneous notes that do not exist in the score I have prepared.

When I go back to musescore and check the piano editor the midi select mirrors what I can see in Cubase. (see second picture. yxbl2.jpg)

I attach the part of the file that is affected. (Test.mscz)

In addition I also get problems where there is a rest in the bar the wrong rest is added or it changes for some reason thereby knocking out the whole score. (see image untitled3.jpg and Untitled3.mscz)

Note these are not the actual scores but mess around notes from the original so it bears no resemble to the original.

Any ideas??

The reason I am using musescore to notate is these where created here first before I got Cubase.

Help!

Attachment Size
Untitled1.jpg 21.51 KB
Test.mscz 1.52 KB
Untitled3.mscz 2.27 KB
Untitled3.jpg 109.56 KB
yxbl2.jpg 98.06 KB

Comments

• Apr 19, 2013 - 21:22

I am currently on version 1.3.

I am using windows 7 latest services pack.

I unistalled and reinstalled but same issue.

Is there a file that could be left from a previous installation of this software?

Reply

• Apr 19, 2013 - 21:28

If I am understanding correctly, the rests shown in Untitled 3 are completely normal - that's the result of deleting notes individually. If you then want to clear the measures completely, select them and hit Delete. However, I can tell you that attempts to copy and paste empty measures in irregular time signatures is problematic in MuseScore. Can lead to score corruption. I don't see it in your score or your picture, but I can create it by copying and empty measure onto another within the 21/16 section. There were some fixes in this area for 1.3, I think, but it still appears glitchy.

As for the MIDI issue, I can't tell you how created the original file. Was it the result of MIDI input? I hear notes overlapping on playback, so this can't have been the result of ordinary note input.

Reply

• Apr 19, 2013 - 22:00

On the silent bars I sometimes get a 4/4 time bar in all the staves but in say bar 8 where timpani is tacit that bar may show 3 rests or 2 rests in total instead of 4/4. f you press delete on the erroneous bar the error moves into the next one. Does that part now make sense?

The mscz file is how I manually input the notes, when you play it back you here the additional stuck notes. That isn't how I input it though. Does this part now make sense?

Thanks

David

Reply

• Apr 19, 2013 - 23:19

Still doesn't really make sense, sorry. It shoild ot be possible to enter overlapping notes like you have apparently done. an you list steps to reproduce? Are you really starting with a band new score and then entering notes?

As for the rests, that also is ery inclear. Surely when you first ceate the scorw, there is nothing but whole measure rests. *Something* you are doing is causing the i idivual ests to appear. Again. If you start from a coml,eely empty score and start entering notes, at what point do those extra rests appear? As I said, it's normal if you enter notes then delete them one by one. Nothing else I an thimk shoild ause those ests to appear. So, assuming you had a score that was was completely enter, then you started doing things, and the those rests appeared, what was he last thing you did that made those rests appear?

Reply

• Apr 19, 2013 - 23:38

Inputting notes I do the following:

I go through the wizard and add instruments.

I create time per bar as this varies.

I input using my mouse dragging from the note length bar ie crotchets, quavers, semi quavers, dotted notes etc......
On the score it looks correct. When you play back it looks like some of the notes are stuck. Also if you note the last 3 notes they so not match the piano role where they should be.

Reply

• Apr 20, 2013 - 04:25

Hmm, I don't know that dragging notes from the palette to the score is even supported, that could perhaps be part of your problem. Have you tried reading the Handbook on Note entry , or watching the tutorial videos from the main musescore.org page, and entering notes as documented (eg, clicking on the ataff or simply typing note names)?

Reply

• Apr 20, 2013 - 09:31

Hi David,

The first score you posted has obviously developed a corruption - the length of the dotted crotchet D when played back reveals this, as also when played back the playback cursor sticks on the last note and the bar is unselectable.

I have noticed that when working in time signatures other than the norm (I work a lot with plainchant so am using constantly changing actual time signatures) these corruptions are more prone to creep in, and you also get problems with rests not displaying properly as you have noted in your second clip.

I was able to select the bar and use delete to get MuseScore to display the proper full bar rest for the first 2, but a corruption became apparent in the last bar which insisted on displaying as a semibreve rest followed by quaver.

IME the only way round these corruptions is to delete the offending bar having first manually copied the notes to a fresh bar inserted before it, which is how I achieved this corrected version of your first clip.

HTH
Michael

Attachment Size
Test_20-1a.mscz 1.51 KB

Reply

• Apr 20, 2013 - 14:17

Hi

Thanks for your reply.

I have gone back to the original score and I deleted the offending notes out of the bar by highlighting that bar.

As I noticed last night that the last 3 quavers and a bit did not match the semiquaver placing below it. Why would musescore allow that to happened. Surely 21 16ths are equally placed on each stave.

Anyway when I delete this I note the same problem as in the second part of my question about bars going out of shift. My note that was a crotchet disappears and becomes a 1/16th note. That bar is now out of synch by one less 1/16th.

This is a bug gong back to 0.9 when I first started to use musescore.

Now when I delete the notes it removes part of a note from the next bar.

To me this suggests that bars are easily corrupted for what ever reason whey you manually input them.

In theory with the xml file the line of script should say this note has to be here it cant go elsewhere. The xml file recreates the same error.

All I can do is redo the score from scratch again so no corruptions are evident.

I also attach a screen capture to show you what happens when the notes are deleted.

if you set a bar as 21/16 your bar should therefore set space for 21 16th notes to fit logically on each stave at the same position not any where the software places it.

eg 1st 16th note has to match each stave

Note I am note complaining as you guys have done this without charge (or from donations you have received) so I didn't expect a free Cubase alternative with all singing and dancing features.

David

Attachment Size
Untitled new.jpg 55.69 KB
Untitled new 3.jpg 41.95 KB
Untitled 19.04.13.mscz 1.62 KB

Reply

• Apr 20, 2013 - 14:25

Hi Micheal

I think my response actually matches what you hade tested on the file I uploaded. Your explanation did help. I was just repeating what I had remembered from last before bed (sorry TMI)

I am familiar with plainsong.

how do you input this without having a time signature?

The score I am working from has no key sigs at all. I merely broke down the component parts for each bar which just happened to contain 16ths. easier to count as well.

Thanks in advance.

David

Reply

• Apr 20, 2013 - 17:26

how do you input this without having a time signature?

There is a bug/feature in MuseScore in which inserting an empty bar at the beginning of the piece and then deleting it deletes the time signature as well as the bar.

I simply use this at the end of the note input process, and use changing Actual Time Signatures in measure properties to have the correct number of notes per bar.

Reply

• Apr 20, 2013 - 15:25

I have *never* seen a score become corrupt simply from entering notes. The known causes of corruption, as far as I can recall, are all related to copy and paste, and are only rare corner cases at that - past of an empty bar in an irregular meter, paste of a partial measure containing tuplets to a different beat position, etc.

IN your case with Untilted 19.04.13, something seems to be very wrong with the dotted quarter G. I can't say what exactly happened, because I am unable to reproduce it. When I try to enter exactly what you have, it works just fine. So let's try it step by step, starting with a fresh clean score in 32/16 (or, just use the bottom staff of your current score, which seems uncorrupted)

Here's the steps using the keyboard:

N 4 F up
B ctrl-down D 5 dot A down 5 plus A down 5 dot G 4 B down G down G

Type exactly that and I get what I expect. The same happens if instead of typing, I click the corresponding icons or places on the staff.

So I'm guessing that what you are seeing this resulted from trying to enter notes into a measure that was *already* corrupted by some previous operation (probably involving copy/paste). If you can recreate the measure in question in a score created from scratch, please list *exactly* the steps you used. Either there is an as-yet-undiscovered bug in note entry, or you are doing something wrong - but actually, even doing something wrong shouldn't cause corruption.

Reply

• Apr 20, 2013 - 16:08

I am have just proved that my musical education and O level in maths was all in vain and wasted!

Officially I am unable to count to 33.

When I looked back at the score and counted how many actual 16ths there were to the bar there were infact 33/16ths not 32/16ths.

I was pasting a bar of 33/16ths into a 32/16ths bar. How that was allowed to happen I don't know. perhaps a corrupted bar has been copied over from a previous version of this software. (eg 0.9)

when you delete the phrase with what appears to be 32 notes it is acutally deleting 33 notes hence the next bar loses a 1/16th. It just happens that the next bar is the same note.

I am going to relook at the score and recount all the 16ths per bar correctly and see if this matches what I have put in musescore and update.

I think what I have done is visually count the 16ths instead of actually properly counting them.

If this is my fix I will update all.

Thank you.

David

Reply

• Apr 20, 2013 - 18:16

Thank you for your time and looking at this for me.

It is me and my counting at fault the file now works correctly.

Somehow all those years back musescore obviously allowed me to create a 33/16th bar within a 32/16th bar. Some of the other bars had the same error or corrupted bar. Once all cleared no problem.

This corrupted bar copied over to the newer version with the same mistake(s).

The only problem I now have is with latency which is not this forums problem.

Perhaps a debugging or warning message would be an idea for future updates?

Thanks

David

Reply

• Apr 21, 2013 - 01:11

Actually, the ability to copy a 33./16 bar onto a 32/16 bar is meant to be a feature, not a bug. Well, in general, the ability to copy a passage of any given length to any particular time position is the feature - MuseScore really ins't copying measures, but rather, regions that may or may not correspond to measures. So what *should* have happened is your first region of 33/16 should have copied just fine - the first 32/16 in one bar, the last 1/16 in the next. For that matter, you should be able copy any arbitrary passage of 33 beats onto any arbitrary position of the score, and it should just fill measures from that point on until the 33 beats are used up. You could copy a bar of 33/16 onto beat 3 of a 4/4 bar and it will put the first 8 sixteenths in that bar (3e&a 4e&a), 16 in the next bar, and 9 in the next.

But there are indeed some corner case issues where scores can become corrupt when doing certain copy/paste operations like this. So I'm guessing you ran into one of these. A bunch of these bugs were found and fixed over the past couple of releases, and a bunch more have apparently been fixed for the upcoming 2.0 release. Feel free to nightly build of 2.0 if you haven't already - although when I say "try", I mean "experiment with" - I don't recommend it for real work. If you still find issues of this nature in one of these nightly builds, that would definitely be worth reporting.

Reply

• Apr 21, 2013 - 19:35

I have just had a look at version 2.0

Nice layout I have to say.

Also I note that the XML file now exports correctly to Cubase which it didn't before. Some of my pedal notes where wrapped around each other and it was funny to see Cubase cursor move along and then back around the wrapped around notes.

When I saved and exported to xml in the nightly version the same eratic behaviour was not noted and the pedal notes were in the correct place as were the note lengths.

That was without me having to do anything to the score before hand.

Reply

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