When extracting parts program crashes.
I have recently started using version 1.2 revision 5470. I had previously not had a problem extracting parts. I changed my operating system and had to reload programs so I got your latest version. I am using windows 7 64 bit. I made a score from a jazz combo template. I had only used tenor sax and piano. I followed the normal steps to create parts but when I push the create button an error window comes up saying that musescore had to close. I have tried to copy the individual parts to a lead sheet template and the program also crashes. this never happened with the older version. Is it the 64 bit windows 7??
Thanks! Frank
| Attachment | Size |
|---|---|
| Varouka The Goat - score.mscz | 10.97 KB |
Comments
Nope, it crashes for me too extracting the tenor part with regular old 32-bit Windows Vista. Probably something specific about this score, since I've created many scores from that same template and never had problems extracting. Not sure what, though. I tried fixing some of the errors I saw, but none made the crash go away.
One thing I saw right off the bat is that you seem to have done something very odd to create the tempo marking. I'm guessing you aren't aware you can hit F2 while typing text to bring up a palette containing various symbols including a quarter note. Looks like you created the quarter note as an ordinary symbol attached to the top staff, but that wouldn't have showed up in any of the other parts even if the extra worked. But this isn't what caused the crash.
I also see a whole bunch of chord symbols you've typed that MuseScore doesn't recognize them because you didn't enter them the way it expects. See the Handbook entry on chordnames, or the tutorial I wrote on lead sheets, for more on entering chords and the various chord styles available. The chord style you are using does not use parentheses for alterations, and if you type them, the chord is not recognized, and this causes problems (b and # not turned into flat and sharp, chord won't transpose, won't export to MusicXML, plugins or other utilities that can play back chords won't work, etc). But again, this wouldn't have caused a crash.
There are also notes outside the playable range of the tenor sax - these are shown are colored. But again, that wouldn't have caused a crash.
At letter B, you have some strange hidden accidentals entered. It appears you tried adding these as courtesy accidentals - using the palette - rather than correct way using the arrow keys, and that is why you then had to hide them. Once again though, that doesn't cause it to crash. Also some oddly manually adjusted ties on page 8. These weren't the source of the crash either.
I did find the if you delete all but the first couple of pages, the problem goes away. So the issue, whatever it is, happens somewhere after that. I would recommend continuing with that approach in hopes of figuring out what is triggering the bug. The reporting back and submitting a formal issue to the tracker.
In reply to Nope, it crashes for me too by Marc Sabatella
Thanks for your observations Marc! I will move down deleting more pages and hopefully find what actually made the crashes. I actually did look at the tutorial for chords at one point but obviously I have forgotten some of the things this program is unable to do. Jazz chord symbols like the a dash for a minor seventh, a triangle for major seventh, a circle for diminished, a plus sign for augmented and a larger circle with a slash through it for minor seventh, flat five, have been around for 70 years. They save space and make lead sheets easier to read. I will look again and see if Muse has anything usable. If not I will just do what I have been doing which is to fix the chords on every part I copy. The tenor sax line is written an octave higher than it will be in the part. Just a mistake not an obsession with altissimo range. Nice to know about the F2 key for getting additional symbols when typing text!
Thanks again for your time, Frank
In reply to When extracting parts program crashes by Frank Southecorvo
As the Handbook and my tutorials explains, you *can* use the old-style dashes and troanlge and so forth if you prefer them over the more modern standards of ma and mi. You just have to change your chordname general style to cchords_sym. But be aware, those old style symbols might be easier to read for older musicians accustomed to seeing those symbols, but they are not used much by modern publishers or musicians who have come through music schools over the past couple of decades. Not saying ma and mi are becoming universal - that would be a huge overstatement - but dash and especially triangle are pretty clearly on the way out in my experience. I certainly wouldn't assume that because you are more accustomed to triangle, that's what other musicians will prefer also.
Btw, I have now learned that a typo on the word "musicians" will often cause the iPad auto spell correct to change it to "suicides". So heads up on that if you see that word showing up at random places in my posts now that I've decided to try turning that option on.
It's the nightly builds (what will become 2.0 - released later this year) that matter now, as no fixes will be made to the branch (there won't be a 1.3 version).
When I open the file, the parts are there already. Can you find any problems?
Using MuseScore 2.0 Nightly Build (5663) - Mac 10.7.4.
Can some explain why the A (or visually, G) in bar 4 of Tenor Sax sounds in bars 5-7 too, despite no indication? Unless that is what the little horizontal line (in bar 4) is for? The latter doesn't seem to be clickable, either.
Using MuseScore 2.0 Nightly Build (5663) - Mac 10.7.4.
In reply to Can some explain why the A by chen lung
The last couple of nightlies I have installed crash on startup for me, which is something I need to look into, but anyhow, I can't verify what you're saying. In 1.2, though, I don't see or hear any problem with bars 4-7. The tenor has a written A (sounding B) whole note, followed by three bars of other notes, no unusual horizontal lines, and it all plays fine.
Could be, though, that there is is some internal score corruption in the file that manifests itself as a crash in 1.2 and as messed up display/playback in 2.0.
In reply to The last couple of nightlies by Marc Sabatella
I've realised the problem in bar 4 of Tenor Sax and Piano (only in trunk): The notes has moved away from the ledger line (explains why we have reported different notes visually) - they aren't correctly positioned either in 1.2 (misaligned with other notes). In 1.2 and the trunk, I hear A (not B).
Another problem: If I click on 'Concert Pitch' and 'Undo', there's a crash. I'm not really familiar with what 'Concert Pitch' does, but I'm not sure it functions correctly either - the notes move an octave up when I click it.
I'll file reports when the new Mac builds begin, if the issues still exist.
Using MuseScore 2.0 Nightly Build (5663) - Mac 10.7.4.
In reply to I've realised the problem in by chen lung
Tenor sax sounds a major ninth lower than written. When Concert Pitch is turned on, you see the pitch that sounds. When concert pitch is turned off, you see the note that is written for that instrument. so what should happen - and does in 1.2, at least - is that with Concert Pitch turned on, you see the A just above the table clef staff - the intended sounding pitch. when you turn Concett Pitch off, you see the pitch that would have to be written in order to get that sound - the B an octave and a whole step above that. Well beyond the normal playing range of the instrument, so you wouldn't ever normally write that pitch, although many players would probably be able to hit the note via altissimo techniques and might do so at a climactic point during an improvised solo.
So anyhow, A is definitely what you are supposed to hear. and since pressing Concert Pitch doesn't actually chane the score - just how it is displayed - I wouldn't necessarily expect Indo to do anything at all, although of course it shouldn.t crash either.
#16835: Opening this score causes crash
#16928: [Regression] Note head positioned away from ledger line in 1.2 score
#16929: Disabling Concert Pitch causes crash