[Mac 10.4] Exporting audio file causes crash
Steps to reproduce bug
1. Open score
2. Save As any of these audio formats: Flac, WAV or Ogg
Result: The program crashes without saving the file
MuseScore version: 0.9.6.3
(Operating System: Mac 10.4.11)
Was fine on 0.9.6.2, so this appears to be a regression.
I reported it initially in the forum: http://musescore.org/en/node/6972
Comments
Your Mac is a PowerPC right?
I can't reproduce on 10.5 intel.
No, it's Intel (both MacBook and MacPro are).
I have 10.5 (MacPro) as well - it's fine there. It must be just 10.4.
Does this happen with the demo "promenade" score?
Yes.
Do you use the default soundfont?
Tried both soundfonts (GM and Tim).
Also see duplicate thread .
If you restore the session, nothing appears.
Reinstating priority.
Well it can be critical, I can't reproduce... Anyone can reproduce? If we can't reproduce we can't fix. Any other info we should know ?
Ask people on 10.4 - seems to be fine on 10.5.
I've attached a log - could be missing component files required to produce the audio?
(Couldn't open attached .txt file, so uploaded it in .zip instead)
To help debug this issue.
cd /Applications/MuseScore.app/Contents/Frameworkand returnotool -L libsndfile.1.dyliband return. Paste the result in a comment.Last login: Fri Jan 28 02:48:36 on ttyp1
Welcome to Darwin!
scott-napiers-computer:~ chenlung$ /Applications/MuseScore/MuseScore.app/Contents/Framework
-bash: /Applications/MuseScore/MuseScore.app/Contents/Framework: No such file or directory
scott-napiers-computer:~ chenlung$ otool -L libsndfile.1.dylib
-bash: otool: command not found
scott-napiers-computer:~ chenlung$
Ok ... again. You don't have
otoolso you need to install the developer tools.Next
cd /Applications/MuseScore.app/Contents/Frameworkand return. It should output nothing, or you write it wrong.otool -L libsndfile.1.dyliband return. Paste the result in a comment. It should give you more than one line and no "Command not found" if otool is installed correctly.Installed xTools (from installation disc).
Last login: Fri Jan 28 14:09:12 on ttyp1
Welcome to Darwin!
scott-napiers-computer:~ chenlung$ cd /Applications/MuseScore.app/Contents/Framework
-bash: cd: /Applications/MuseScore.app/Contents/Framework: No such file or directory
scott-napiers-computer:~ chenlung$ cd /Applications/MuseScore/MuseScore.app/Contents/Framework
-bash: cd: /Applications/MuseScore/MuseScore.app/Contents/Framework: No such file or directory
scott-napiers-computer:~ chenlung$ otool -L libsndfile.1.dylib
otool: can't open file: libsndfile.1.dylib (No such file or directory)
scott-napiers-computer:~ chenlung$
Still crashes outputting WAV.
Where is MuseScore installed on your Mac? What the name of the MuseScore application when you go to Applications in your dock? I'm not trying to solve your problem on your mac specifically... I'm trying to understand why you have a crash.
First thing first you have to find where the MuseScore application is installed.
Applications>MuseScore>MuseScore.app
There is a folder in Applications.
Ok. My mistake.
cd /Applications/MuseScore/MuseScore.app/Contents/Frameworksotool -L libsndfile.1.dylibYou didn't know I had it in a folder - so not your mistake :)?
Last login: Fri Jan 28 18:22:20 on ttyp1
Welcome to Darwin!
scott-napiers-computer:~ chenlung$ cd /Applications/MuseScore/MuseScore.app/Contents/Frameworks
scott-napiers-computer:/Applications/MuseScore/MuseScore.app/Contents/Frameworks chenlung$ otool -L libsndfile.1.dylib
libsndfile.1.dylib:
@executable_path/../Frameworks/libsndfile.1.dylib (compatibility version 2.0.0, current version 2.21.0)
@executable_path/../Frameworks/libFLAC.8.dylib (compatibility version 11.0.0, current version 11.0.0)
@executable_path/../Frameworks/libvorbisenc.2.dylib (compatibility version 3.0.0, current version 3.7.0)
@executable_path/../Frameworks/libvorbis.0.dylib (compatibility version 5.0.0, current version 5.4.0)
@executable_path/../Frameworks/libogg.0.dylib (compatibility version 8.0.0, current version 8.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.5)
scott-napiers-computer:/Applications/MuseScore/MuseScore.app/Contents/Frameworks chenlung$
Were you able to find anything :)?
I had a thought - instead of crashing, a warning could appear if components needed to produce it are missing?
Crash also reported at http://musescore.org/en/node/9593
In 2.0 Nightly Build (4979), there's no crash, but the file doesn't appear either.
This remains, however:
#8998: [Trunk] Exporting MIDI causes crash
All using Mac 10.4.11.
In 2.0 nightly build (4989), there's a crash.
Using 10.4.11.
fixed in trunk in revision 4092
Hangs, then crashes.
Using 2.0 nightly build (4095) and Mac 10.4.11.
With some scores, it'll crash (producing an empty file). With others, the program will hang as it exports an MP3 (one score exported it partially once, but attempts after were fine).
Using MuseScore 2.0 nightly build (4141) and Mac 10.4.11.
The problem here is identified. Exporting to ogg, flac, and wav using MuseScore 1.0 and nighlies on Mac 10.4 does not work because the library used by musescore to provide this facility (libsndfile) is not compiled for 10.4 on my computer (and I built MuseScore 1.0 and build the nightlies). I didn't find a way to do it yet and it's a minor issue for me.
The new MP3 export in trunk does not rely on libsndfile and should not have this same issue.
Change title
I have upgraded to 10.6.7 (no problems), so I can't check on 10.4.
I know some other people have had problems (possibly on different OS) and I've linked to this issue, but I'm unsure overall what to do now.
10.4 ppc is no more supported. A package might come in the future but this bug should be fixed.
This was tested with Intel.
I think 'won't fix' is more appropriate.
I've had this problem, too. Just remove the empty measures at the end of your work and save the file: it works !
Then I tried for a longer piece - it crashed twice, but the third time it was completed successfully. I think this could be a temporary solution before a new update.
NB: I use Windows 7, Intel Pentium CPU - P6100 - 2GHz
Hope it would be helpful !
This bug report was about Mac 10.4 specifically and it's not fixed, and will not be fixed.