Does not play percussion correctly

• Apr 28, 2012 - 14:50

Hi,

I made a score for a percussion but it does not play the repetition. What have I done wrong?

Also, the first staff is not in line with the remaining sheet staff. Again what setting have I miss?

Regards

Attachment Size
Rock Around the Clock.mscx 58.69 KB

Comments

Currently, the measure repeat sign don't play back. What I usually if I want this kind of thing to playback is have an additional staff in my score for playback with everything all written out. I simply don't extract that part when extracting parts. When printing the score, I extract a "print score" that contains everything but the playback staves. I usually do this for all rhythm section part, since they'll all often have things that will want to playback differently from how they display (chord symbols, etc).

As for why the first system doesn't align the rest, I can't quite tell what you did. It appears you hid the staff name, but for some reason the staff name is overlapping the staff, which isn't normal. I can't tell what made that happen. How did you create this score? Was it perhaps imported from a MusicXML file created by a different program? If so, that might explain the unusual (for MuseScore) formatting. Or did you create this from someone's custom template?

Either way, what I'd do is simply copy and paste this into a fresh score that is set up more normally.

In reply to by Marc Sabatella

Its too bad that repeat does not play back it would have made things simpler for us. Is it something that can be done as a plug-in?

We imported the sheet from Finale through XML. this might explain why the staves are not aligned. I tried to copy paste the staves onto a new sheet, from a template or no template. Either the program crashes or nothing gets copied. I am pretty sure it is very simple, but been new to Musescore might explain why I have difficulties.

In reply to by Beaver

I don't see any way a plugin could address this, but playback of measure repeats is already implemented for the next major version, which should come out within the year.

Copy between scores does sometimes fail, and scores that have inherent problems like this one does probably trigger that more often than others. Unfortunately, MusicXML is still not perfect as a way of transmitting information reliably, and sometimes there is no choice but to re-enter certain parts.

In reply to by Marc Sabatella

The repeat worked nice with the nightly build version. Great look BTW. Hopefully the new version will come out sooner than later :)

Why not release what you have done so far and released the remaining later? Would you have any constraint for not doing so. This way we could start to use all the wonderful stuff you have implemented.

Is it possible to improve and detect defect while importing from xml format?

In reply to by Beaver

If we release a new version we need the next version to be able to open consistenly the files you created with the previous version. And that's a lot of work. So we prefer doing only one or two stable releases per year.

As stated, nightlies are not meant for serious work. You might loose compatibility. But nightlies are indeed done to report issues ! MusicXML issues are welcome. Regarding drums, there is already this one : #15472: [MusicXML] Import drumset information from MusicXML

In reply to by Beaver

"Why not release what you have done so far and released the remaining later?"

Because version 2.0 is not stable enough for general release - there are changes being made daily.

All users have access to the nightly builds though if they want to use them, but much care is needed in their use to make sure you don't lose your work - currently you can save your work in one version and then find that the developers have changed the file format slightly so it won't load into a later one properly, or crashes the program.

Having said that I am currently using 2.0 (carefully) for producing my guitar teaching worksheets, partly as a means of testing out the TAB facilities.

HTH
Michael

In reply to by Beaver

Well, whatever you have done should cause crashes and staves that cannot be realigned, so there's definitely bugs here - all you did "wrong" was perform the series of steps that triggers the bugs. Maybe someone else could figure out what happened just from looking the score, but it mystified me.

In reply to by chen lung

1- Load Rock Around the Clock sheet to copy from
2- Create a New score from scratch. Select only Drumset 5 lines then Add, Select default Key and Time Signature. Leave newly created score as is, go back to original score, Select all, Copy, go to new score, Paste. Application should display a runtime error and close after another error window.
3- BTW, if you have 2 scores open and delete everything on one of them, go back to first one Select All, Copy is grey out. Grey out even if leave application and go back.

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