Imported PDF file always crashes program

• Dec 17, 2016 - 19:01

Hey guys.

I've just done my first ever test of converting PDF to MuseScore, and upon opening the resulting file, the program immediately crashes. I was just wondering if that's 'normal' behavior, and just something I should expect from some PDF converts?

It doesn't matter whether I use the latest stable version, or try to download the latest nightly, I get the same immediate crash.


Comments

In reply to by ArniVidar

Latest build from master, 67b1111, crashes with

1 Ms::Fraction::operator+= fraction.cpp 116 0x86579b
2 Ms::TimeSigMap::normalize sig.cpp 247 0x8d89df
3 Ms::TimeSigMap::add sig.cpp 220 0x8d88f1
4 Ms::readMeasure read206.cpp 811 0x9472f8
5 Ms::readStaffContent read206.cpp 1331 0x94a0d6
6 Ms::readScore read206.cpp 1434 0x94add2
7 Ms::MasterScore::read206 read206.cpp 1693 0x94ce3a
8 Ms::MasterScore::read1 scorefile.cpp 922 0x841556
9 Ms::MasterScore::loadCompressedMsc scorefile.cpp 780 0x840684
10 Ms::MasterScore::loadMsc scorefile.cpp 827 0x840b23
11 Ms::readScore file.cpp 2052 0x5a7bdc
12 Ms::MuseScore::readScore file.cpp 328 0x59866e
13 Ms::MuseScore::openScore file.cpp 309 0x59853a
14 Ms::MuseScore::loadFiles file.cpp 290 0x5981fc
15 Ms::MuseScore::cmd musescore.cpp 4641 0x49e758
16 Ms::MuseScore::cmd musescore.cpp 4496 0x49ddee
17 Ms::MuseScore::qt_static_metacall moc_musescore.cpp 733 0x69ce1a
18 ZN11QMetaObject8activateEP7QObjectiiPPv 0x68a08942
19 ZN12QActionGroup7hoveredEP7QAction 0x1c0e5295
20 ?? 0x226a4738
...

Prior to that it reports:
Debug: TDuration::setType(): unknown, assume "quarter" (...\MuseScore\libmscore\durationtype.cpp:282, void Ms::TDuration::setType(const QString&))
Debug: TDuration::setType(): unknown, assume "quarter" (...\MuseScore\libmscore\durationtype.cpp:282, void Ms::TDuration::setType(const QString&))
Debug: overlap measure 13200 at 1840-2640 track 4 (...\MuseScore\libmscore\check.cpp:368, void Ms::Measure::checkMeasure(int))
Debug: overlap measure 13200 at 2520-3160 track 4 (...\MuseScore\libmscore\check.cpp:368, void Ms::Measure::checkMeasure(int))

I think that the file may be corrupted beyond rescue. I decompressed it and looked at it with Bluefish editor. There are many very odd time signatures including several bars of 0/1. I replaced the 0/1 bars with 4/4 and got the file to open but there are still inconsistencies all through it. I'll keep looking but wouldn't hold your breath.

[Edit] Nah, it's wrecked. It seems that every measure has a different duration (15/8, 3/2 etc.) and some measures have different settings for different staves. Whilst this might be deliberate when creating a score I can't see how a scanned pdf could sensibly generate this unless the source file was wrong or the scanning had gone wrong.

Even the bits that I can read and hear are hopelessly messy and would take more time to tidy up than to enter from scratch.

In reply to by Jojo-Schmitz

Wow, that's one seriously powerful program, thank you!
It converted the score in no time, and even sang me the song (albeit horrendously!) :D

I'm looking for sheet music for my choirs, so the samples are all one or two pages anyway, so that's not a problem at all. I just need to hear whether I like the arrangement or not, before buying the X copies required :)

So for those purposes, that program definitely makes my life easier. I've been inputting all the various samples into MuseScore to hear them back :)

I have had the same experience. Constant crashing whenever I was editing staff elements in an imported from pdf file.

I found the following line in the ~score~.mscx file. This file is found inside the ~score~.mscz file. ... where ~score~ is the name of your file...
/tmp/audiveris-089611086f48f33a90a28b6d7599341e/score.pdf

"audiveris-089611086f48f33a90a28b6d7599341e/score.pdf" did not exist in my /tmp/ folder.

When I removed the contents of the source tag "" the crashing immediately stopped.

In reply to by RodneyOlivier

I would think after 7 years the original poster has moved on to other issues. Audiveris and Musescore have definitely updated since then. If this is a suggestion for anyone needing to fix current problematic files, it is generally best to start a new topic rather that resurrecting an ancient one.

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