Musescore crashes when I try to create pickup measures

• Mar 28, 2014 - 01:08

I have a piece in 3/4 time, but I want the first measure to be a pickup measure with only 1 beat. Whenever I change the actual value of the measure in the measure properties window from 3/4 to 1/4, Musescore crashes instantly.


Comments

I'm guessing you are on MacOS Mavericks? Lots of people seem to be having this and other problems since that update. Uninstalling MusEScore 1.3 and installing 1.2 seems to work around it.

In reply to by schepers

Indeed, with Promenade it crashes

Debug: insertTime -1920 at tick 480 (...\MuseScore\libmscore\score.cpp:3488, void Ms::Score::undoInsertTime(int, int))
Debug: TDuration(5/4): not implemented (...\MuseScore\libmscore\durationtype.cpp:431, Ms::TDuration::TDuration(const Ms::Fraction&))

Strange enough the next line (line 432 in durationtype.cpp)h as a commented abort()
However; changing to a supported type like 3/4 crashes too

Reported: #25165: crash when changing 1st measure to a pickup measure

In reply to by Jojo-Schmitz

Here is a link to a score I transcribed which I uploaded on August 13th, 2013. I successfully used the feature then: http://musescore.com/user/55939/scores/121950#

I am working on transcribing a score today and I am unable to change measure duration for the last measure.

I couldn't say what is causing the program to crash. I'm attaching the score if you are interested in seeing if you can duplicate the crash on your end. Let me know if I should send the error report.

In reply to by kerfuffle

Here's the top part of the error code

Process: mscore [5385]
Path: /Applications/MuseScore.app/Contents/MacOS/mscore
Identifier: net.sourceforge.mscore
Version: 1.3 (1.3)
Code Type: X86-64 (Native)
Parent Process: launchd [566]
Responsible: mscore [5385]
User ID: 501

Date/Time: 2014-06-04 15:16:50.016 +0200
OS Version: Mac OS X 10.9.3 (13D65)
Report Version: 11
Anonymous UUID: 0BC12DDE-CD0A-83FE-F507-5374E14BE2A0

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000500000002f

VM Regions Near 0x500000002f:
CG shared images 00000001c871f000-00000001c8727000 [ 32K] r--/r-- SM=SHM
-->
JS JIT generated code 00002dad43e00000-00002dad4be00000 [128.0M] rwx/rwx SM=PRV

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