Musescore 1.1 in Ubuntu?

• Jul 29, 2011 - 09:57

Hi, great software. I'm music teacher and will replace finale with my students. I use 1.0 in Ubuntu 10.04. How can I switch to the new 1.1?

Comments

• Jul 29, 2011 - 13:04

The MuseScore packager for Ubuntu named Toby Smith has been informed about the 1.1 release, so we hope he can offer you a package real soon. Take into account is holidays right now so it might take some time.

Reply

• Aug 5, 2011 - 17:07

you can also
- download the bz2 file for linux ( mscore-1.1.tar.bz2)
- extract the files from the archive
- in a shell :
make release
make install

(look at README.txt)

I use ubuntu 10.10 .

ps : that didn't work the first time ..

I had also to execute :
sudo apt-get install libasound2-dev libsndfile-dev
make clean

all work fine.

Reply

• Aug 5, 2011 - 19:10

I'm trying to compile Musescore 1.1 in Debian (specifically AVLinux 5) which should proceed in a similar way to Ubuntu (or any linux for that matter). I have this non-informative error:

[ 86%] Building CXX object scriptgen/qtbindings/gui/CMakeFiles/qtscript_gui.dir/qtscriptshell_QDrag.cpp.o
Linking CXX shared library libqtscript_gui.so
make[3]: Leaving directory `/mdkhome/sound/software/mscore-1.1/build'
[ 86%] Built target qtscript_gui
make[2]: Leaving directory `/mdkhome/sound/software/mscore-1.1/build'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/mdkhome/sound/software/mscore-1.1/build'
make: *** [release] Error 2

I installed several packages with qtscript in the name, but this did not help. Any debugging suggestions?
I have to say I find the build process of Musescore to be rather primitive to other packages I've built. There is not much configuration checking and the build always starts from scratch so each build attempt is a ~1 hour process (in my case) to see if I manage to fix the problem.
I see have have made ./scriptgen/qtbindings/gui/libqtscript_gui.so so it does not look like compiling i/libqtscript_gui. is the problem. Also scriptgen/qtbindings/gui/CMakeFiles/qtscript_gui.dir/qtscriptshell_QDrag.cpp.o exists.

I'm using gcc 4.6.1. Thanks for suggestions

Reply

• Aug 5, 2011 - 21:09

Ok, I captured my whole output and found this compilation error:

[ 68%] Building CXX object scriptgen/qtbindings/gui/CMakeFiles/qtscript_gui.dir/qtscript_QTextObjectInterface.cpp.o
/mdkhome/sound/software/mscore-1.1/mscore/mscore/exportxml.cpp: In function ‘void directionTag(Xml&, Attributes&, Element*)’:
/mdkhome/sound/software/mscore-1.1/mscore/mscore/exportxml.cpp:2366:59: error: invalid conversion from ‘const SLine*’ to ‘SLine*’ [-fpermissive]
make[3]: *** [mscore/CMakeFiles/mscore.dir/exportxml.cpp.o] Error 1
make[3]: Leaving directory `/mdkhome/sound/software/mscore-1.1/build'
make[2]: *** [mscore/CMakeFiles/mscore.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs....

Not quite sure what to do about it or why I get this error and not others (gcc version?). I've attached the entire output too, but that was the only error I found.

By the way, I think I could do the apt business, except none of the repositories I know about have Musescore 1.1 available.

Attachment Size
compile.zip 17.64 KB

Reply

• Aug 9, 2011 - 02:29

I was able to get Musescore 1.1 to compile and run by changing this line in exportxml.cpp

if (el->type() == HAIRPIN || el->type() == OTTAVA || el->type() == TEXTLINE) {
// SLine* sl = static_cast(el); //original line
SLine* sl = static_cast(el); //new line

Reply

• Aug 6, 2011 - 01:55

Thank you.
I didn't know this option for 'sudo apt-get'.

My problem was to use musescore with ubuntu
I guess that musescore was compiled with qtCreator ; so I "apt-get install" qtcreator.
but I had to install also libasound2-dev and libsndfile-dev

i had a problem with sound ... no sound !!!
solution:
in the menu
edit->preferences->IO
replace
"default"
with
hw:0

Reply

• Aug 12, 2011 - 09:42

Hi cgueganno, i've tried it and also tried to compile from svn following these steps:

http://musescore.org/nl/developers-handbook/compile-instructions-ubuntu…

but i always get the same error:


[ 75%] Building CXX object scriptgen/qtbindings/gui/CMakeFiles/qtscript_gui.dir/qtscriptshell_QDrag.cpp.o
Linking CXX static library libqtscript_gui.a
make[3]: uscita dalla directory "/home/yuri/Scaricati/software/linux/musescore/build.release"
[ 75%] Built target qtscript_gui
make[2]: uscita dalla directory "/home/yuri/Scaricati/software/linux/musescore/build.release"
make[1]: *** [all] Errore 2
make[1]: uscita dalla directory "/home/yuri/Scaricati/software/linux/musescore/build.release"
make: *** [release] Errore 2

i'm under linux mint 10 (julia), an ubuntu-based distro.

it seems to me i've installed all the dependencies but obviously something is missing.

any ideas?

thank you in advance.

y

Reply

• Aug 12, 2011 - 13:31

My solution is suitable for geeks, but as stated Lasconic, the best solution is really to have
the proper debian package.
=> Next work : learn how to build debian package ...

What I did ..

I had the same kind of errors (exiting directory .. Error 2 ...) while following the instructions
The error messages are not explicit .
The only way that I found was to compile ms1.1 with qtcreator.
(just opening a file and click one button ..)
* Project->open file called CMakeLists.txt located mscore directory)
* compile (green button)
And when the first error occurs , the messages is explicit and looks like
"cannot find file xxxx.h" or something like that
So, I googleize this file name (ubuntu xxx.h) an found the package witch contains this file
I "sudo apt-get install" it (its name is generally something-dev)
And I go again to compile stage.
When the compilation sucess, qtcreator launchs mscore .

After this work, the official instructions are ok, and after the 'make install' old icon launch
the new version.
(I start official instruction with : "make release)

These lines summarize what I did :
sudo apt-get install cmake qtcreator libasound2-dev libsndfile-dev libfreetype6-dev
make release
sudo make install

You should try that before using the qtcreator IDE !

ps:
qtcreator (includes all the dependenciies for qt dev.) : all for compiling a qt application + IDE
libasound2-dev for alsa

Reply

• Aug 11, 2011 - 12:26

Is it possible...or do you thing that is necessary to write down a detailed instruction about building mscore from source code for people (like me) who never try to install something from source code? I am an Ubuntu and Debian user.

Reply

• Aug 11, 2011 - 13:14

I think it should be useful to have detailed instruction for ubuntu . I was a 50 % ubuntu and 50% windows user.
50% windows were for Finale from MakeMusic ( music editor software) . With musescore I am now 100% ubuntu.
The problem is to get the last version !

For 1.1, the solution is to re-build mscore ..

But, If you build it for the first time and follow the instructions, it does not work : you have to install also special packages
for development.
( Older version of mscore installed with "ubuntu" (package management) have installed all the dependencies for
mscore, but the other packages are binary packages : they don't include the source )

Compiling for the next version ( 2.0 ?) should be easier and faster (I expect!)

If you want I can retrieve all the commands I used to compile my 1.1 , and write them in this thread.
I am not sure to propose the best solution , but it works for ubuntu .
I also used it on a netbook.

Reply

• Aug 12, 2011 - 07:23

MuseScore is looking for an Ubuntu/Debian package maintainer. The current maintainer has done a very good effort over the years, but it appears his time and interest have shifted to something else. Someone?

Reply

• Aug 12, 2011 - 10:00

Hi, I got a suggestion for lasconic: since nobody in this thread seems to have the skills-time to compile MS 1.1 for Ubuntu. Why not asking for help to the people that can do it?

http://lau.linuxaudio.org/
http://music.columbia.edu/mailman/listinfo/linux-audio-user

On the mail lists there, there are many skilled linux audio users, used to compile and work in linux. Maybe someone can help. Just a suggestion.

Reply

• Aug 12, 2011 - 14:29

It's also important to bear in mind that these problems have rational causes. The stable PPA is updated fairly regularly, and published packages for Ubuntu releases which do not offer the most recent version officially. The unstable PPA is updated when the trunk is in a fit state to build and publish.

If the PPA falls behind, it is because this is a volunteer project, and personal reasons often get in the way. Despite that, I am always aware that I have a responsibility here, and will try to get to things in a timely way. I have been rather unwell for the past few months, and I would have hoped that, especially within a project without a time-based release schedule, a delay of around a fortnight on the availability of binary packages on one platform should not cause too much distress, even in these days of instant gratification. I would be more concerned about the distress were the source not available, but fortunately, this is an open source project.

All that having been said, of course, I would like to make it clear that I do not feel that I kept the project sufficiently up to date on my status, and so a certain amount of confusion was caused. I do take responsibility for that, and I can understand why people would ask, "where is the new release?" Naturally, there were reasons for the delay, but it would have been better to make those reasons public as soon as possible.

The best documentation for how to build MuseScore on Ubuntu is contained in the source to the Debian package, because that tells dumb computers what they need to do to reproduce a sound package. I do not have enough time to produce that documentation online as well, but the "rules" file should give a comprehensive explanation as to what goes on during the build process, and the "control" file should give an adequate list of build dependencies. The wiki is open for editing: if anyone wants to keep the build instructions up to date, feel free to do so.

Reply

• Aug 12, 2011 - 22:27

I just want to say, the build instructions for Ubuntu may be out of date, but they are by no means "out-of-date", and what I mean by that, is even though they are meant for an older version of Muse Score and Ubuntu, they work perfectly none the less. I followed the instructions on musescore.org, using the " sudo apt-get build-dep mscore " command, and all the make and make install is no different from building anything else in Ubuntu. Building is really not that hard, like I said earlier, I know how to build, and make install and everything, Muse Score is VERY easy to build from source, it's just making .deb packages that I don't know how to do.

Reply

• Aug 12, 2011 - 23:57

Ah, but building deb packages is fairly easy, too! Especially if you're using the apt-get commands to help. The way I usually start with a new upstream version is this:

1. I make sure I have the build dependencies for the old version
2. I make sure I have the source for the old version
3. I get the new source from upstream
4. I copy the "debian/" folder from the old source package to the new sources
5. I update the "debian/changelog" file to reflect the updated version
6. I ensure that all my patches still apply (usually by trying to edit the most recent one, ie "dpatch-edit-patch 23-fix-bindings")
7. I make sure that the new upstream source complies with the Debian Free Software Guildelines
8. I build an orig tarball
9. I attempt to build a test package using pbuilder or dpkg-buildpackage

Then, if anything goes wrong, I fix it, document it in the changelog, and try step 9 again. I also usually try and fix all outstanding bugs in the Debian and Ubuntu bug trackers. Once that's done, I run lintian to check for policy compliance, and then build a final set of source packages for uploading to Debian, Ubuntu and the PPA. Finally, I do the upload, including requesting exceptions to whatever freezes are applicable.

All that can be simplified into four steps:

1. Get build deps
2. Get new source
3. Update debian changelog
4. Build new package, fixing any problems encountered along the way.

The reason why MuseScore is easy to build from source on Ubuntu and Debian is that I make sure that the packages are well constructed over time.

Reply

• Aug 14, 2011 - 00:30

I'm confused, to build from source all I had to do was use the command to get dependencies, then make, and make install, if it worked so well just doing that shouldn't you be able to just build a .deb package? Did the source already have the patches that you're talking about? And if it did, I don't see why there wasn't already a .deb package.

Also I see there still isn't a .deb package for the latest version, however it was very easy for me to build it on my computer, like I said, all I did was make and make install, wouldn't I be able to just download the source and create a .deb package?

Sorry for my ignorance, I'm just trying to understand this better. If making a .deb package requires writing patches, then it would probably be over my head.

Reply

• Aug 14, 2011 - 14:58

The Debian Policy stipulates certain fairly strict requirements on the package build process. For instance, the list of build dependencies must be completely specified, and the package must be able to be built entirely from source without an active internet connection during the build process. On top of these requirements, the package is patched and constructed in such a way as to make the life of the user easier; as examples:

it includes patches and a wrapper script to set the right start-up options to ensure audio playback works;
it splits out architecture-dependent and -independent files into separate packages (amongst other things, to minimise wasted space and to reduce conflicts on upgrades);
it splits out the MuseScore soundfont into a separate package (so it can be installed separately);
it includes patches to make sure the sources build in an appropriate way for Ubuntu and Debian;
it is modified to comply with the Debian Free Software Guidelines;
the about box is patched to provide information about help and bug reporting in Ubuntu and Debian;
the package source contains information on copyright and licensing.

None of this is particularly difficult, and it's all documented in the Debian changelog (found at /usr/share/doc/musescore/changelog.Debian.gz) and the package source (apt-get source musescore). But it is rather more than just "make; make install" - how do you think apt knows what the build dependencies even are? A "deb" package is just one part of the system: it is just an "ar" archive containing two sub-archives, one for data and one to describe the package. The repository extracts the "control" information from the source package (which is not a "deb" file but a collection of archives and patches) and the binary deb package, and seeds that information to your computer, so that your system knows about how to download and build and install and describe the package.

Reply

• Aug 12, 2011 - 14:17

Hi everyone,

Sorry for the delay - I've been rather ill recently. I'll have packages built soon. The mscore-stable PPA should provide packages that are usually fairly up to date. The unstable PPA hasn't been updated for a while due to build difficulties and instabilities in the trunk code. I'll try and get that going again over the weekend.

If anyone wants to help out, please feel free to contact me. Really, you would need at least some knowledge of Debian packaging - I don't have the resources to teach about that, though if you are interested, I would suggest reading the Debian and Ubuntu Packaging Guides, and looking at package source code and the Policy.

Reply

• Aug 14, 2011 - 15:00

Packages are available for lucid, maverick and natty in the mscore-stable PPA, and should appear in Debian and oneiric shortly. (In the meantime, I am considering uploading a version for oneiric to the PPA as well).

Reply

• Aug 19, 2011 - 16:11

EDIT: Sorry for the following confused posting.
I just got an automatic update which did indeed install v1.1.
I'll leave the following posting anyway, in case it sheds light
on something about the install process.
-------------------------

Thank you very much for providing this PPA.
But is the 64-bit Lucid package working?
I installed from the PPA, getting this as the final message:
> Setting up mscore (1.1+dfsg-0ubuntu~lucid1) .

running 'dpkg --list mscore' gives:
> ii mscore 1.1+dfsg-0ubuntu~lucid1 Dummy transitional package for musescore

but:
- 'mscore -v' gives :
> Unstable Prerelease for Version 0.9.6; Build 2613
- /usr/bin/mscore and mscore.real are both still dated 2010-02-23
- 'apt-file list mscore' lists just changelog and such, which in fact
ARE up-to-date.
EDIT: I see that the real file-list is under musescore, which lists the
the same /usr/bin files, which are NOT updated, as I reported above.

I am running Ubuntu 10.04 (lucid) for x86_64

Thoughts?
-LenW

Reply

• Feb 4, 2012 - 22:52

follwoing information provided when install music score 1.1 in ubuntu 11.?

This error could be caused by required additional software packages which are missing or not installable. Furthermore there could be a conflict between software packages which are not allowed to be installed at the same time.

The following packages have unmet dependencies:

musescore: Depends: libc6 (>= 2.4) but 2.13-20ubuntu5 is to be installed
Depends: libgcc1 (>= 1:4.1.1) but 1:4.6.1-9ubuntu3 is to be installed
Depends: libportaudio2 (>= 19+svn20101113) but 19+svn20110326-2 is to be installed
Depends: libqt4-network (>= 4:4.5.3) but 4:4.7.4-0ubuntu8.1 is to be installed
Depends: libqt4-script (>= 4:4.5.3) but 4:4.7.4-0ubuntu8.1 is to be installed
Depends: libqt4-scripttools (>= 4:4.5.3) but 4:4.7.4-0ubuntu8 is to be installed
Depends: libqt4-svg (>= 4:4.5.3) but 4:4.7.4-0ubuntu8.1 is to be installed
Depends: libqt4-xml (>= 4:4.5.3) but 4:4.7.4-0ubuntu8.1 is to be installed
Depends: libqtcore4 (>= 4:4.7.0~beta1) but 4:4.7.4-0ubuntu8.1 is to be installed
Depends: libqtgui4 (>= 4:4.6.1) but 4:4.7.4-0ubuntu8.1 is to be installed
Depends: libqtwebkit4 (>= 2.2~2011week34) but 2.2~2011week36-0ubuntu1 is to be installed
Depends: libstdc++6 (>= 4.6) but 4.6.1-9ubuntu3 is to be installed
Depends: zlib1g (>= 1:1.1.4) but 1:1.2.3.4.dfsg-3ubuntu3 is to be installed

Reply

• May 22, 2012 - 17:31

To summarize this thread which is spread out over a year:

ubuntu 10.04 (Lucid Lynx) and 10.10 (Maverick Meerkat) run MuseScore 1.1 just fine.

Some problems getting a build of MuseScore 1.2 for those older ubuntu versions but I can report that MuseScore 1.2 runs well in ubuntu 12.04 (Precise Pangolin) without any apparent difficulty..

There appear to be issues with sound volume in 12.04 (everything seems a bit quiet) but I'd blame ubuntu, not MuseScore for that and it's probably fiaxble with a bit of ubuntu forum searching.

Reply

• Jul 3, 2012 - 22:31

gia sas ipoxreosi mou einai na epeneso to programa einai para poli kalo. exo omos mia diskolia . 1/me ton oplismo se vizantines klimakes paradigma otan gia oplismo vazo [Bb+ Eb +F#=D XITZAZ] to programa den mou diavazi kai eno iparxoun ston ston oplismos gia na mou tis peksi vazo pano sti nota ksana tin ifesi i tin diesi kai etsi akouo tin melidia kai meta ksana zvino tis aliosis. mipos iparxi kapios tropos na bori na akousti i melodia me diaforetiko oplismo apo tous klasikous dioti stis vizantines klimakes ston oplismo bori na eina mazi kai IFESIS DIESIS
2/sta sintheta metra opos 7/8- 9/8- 11/16-15/16 kai alla mou enoni olla ta ogdoa kai dekata ekta se ollo to metro kai anagazome meta na ksexorizo ana tis notes analoga me ton xrono paradigma [7/8= 3/8+2/8+28] an kai gia afto gnorizi kapios tha me efkolini afantasta

Reply

• Jul 4, 2012 - 09:14

I apologise in advance if my post is a bit off-topic, but perhaps it can help with using the latest version of MuseScore.

Many people might use older versions of Ubuntu like 10.04 because it does not run Unity, or perhaps because they need to customise it for a more Windows-like feel. Another reason might be that they cannot support graphic acceleration.

If that is the case, perhaps Lubuntu is a good option. It runs on old hardware, needs no graphics acceleration, has a look and feel that is familiar to Windows users, and yet it is based on the latest Ubuntu release, so it will have the latest gcc, Qt and MuseScore available in the repositories - no compiling necessary.

Ignore my post if not relevant...

http://lubuntu.net
http://en.wikipedia.org/wiki/Lubuntu

Reply

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