nightly downloads for linux

• Jan 2, 2015 - 12:34

As Marc Sabatella suggested I open an new topic as I think I have found where my problem (http://musescore.org/en/node/42001) is coming from.
1. When I open Edit>Preferences>Score I have:
Default Files:
Instrument list 1: :/data/instruments.xml
However, as :/ refers to the root which is ~/Downloads/mscore (the name of the directory where I have extracted mscore 2.0) there are no directories installed so also no directory "data".
All newly created directories by the nightly downloaded mscore are created in: /home/joep/Documents/MuseScoreDevelopment/
Those are the directories: Images;Plugins;Scores;SFZ;Soundfonts;Templates.
However all are empty. I have stored 2 soundfonts in the directory Soundfonts but that has no effect.
I assume that the directory structure made is not correct. Therefore there is no file instruments.list and no data directory that is filled by the nightly build.
To show the procedure I've used:
1. Download mscore.64bits-2015-01-01-14-37-4f4115b.tar.bz2 to directory ~/Downloads
2. Extract using Archive manager to directory mscore ~/Downloads/mscore
3. Use script (see http://musescore.org/en/node/42001) to start mscore-2.0.
My OS is ubuntu 14.04 and the processor is 64-bit AMD Phenom-II, 4 GB memory and a 256GB SSD.
Hope somebody knows how I can install the missing files & directories.
Joep


Comments

Right, instruments.xml is compiled right into the application, and that is what MuseScore uses.

It isn't clear which problem you are referirng to; there are a number of unrelated ones mentioned in that thread. But as I suggested there, please post the specific score you are having issues and the specific step by step instructions to reproduce the problem. That's always the quickest path to a solution.

In reply to by Marc Sabatella

Marc,
Thanks for your reply. I will attach the score - which runs OK in 1.3 - but as a new test score gives the same problem I think it has nothing to do with the score but with the fact that mscore doesn't find the relevant files. In 1.3 I have a file instruments.xml that is located in the directory /usr/share/mscore-1.3/templates/ together with other centrally located directories like plugins, wallpapers, etc.
From your remarks I assume they are embedded in the build but it a mystery for me why running program can't/won't access these embedded directories.
I'll add the score which is an arrangement for 2 piano's of "April in Paris" by Vernon Duke and comprizes 17 pages (170 bars) with 64 bars of free improvisation. In the original score the chords are visible as they are written on layer 4 (but there is some misplacement in the later parts of the score as the score originally was written in Finale and transported using mxml).
It is perfectly displayed in 1.3 (which I use to split parts and printing and works perfectly).
Hope you have a solution for my problem as I start to like Musescore more and more.
Joep

In reply to by J.L. Blom

Looks like the part isn't linked to the main score at all.
Well, this linked parts being a 2.0 feature, it might have to be that way with a score created in 1.x?

BTW: I don#t see anything in voice 4 (assuming that is what you mean by layer), but a whole buchn of unneeded invisible rests in voice 3.
Also invisible rests in voice 1, these might be a candidate for slash notation?

Attachment Size
april-in-paris-2pno.mscz 166.58 KB

In reply to by J.L. Blom

OK, I have the score now, but what about the specific step by step instructions to reproduce the problem? I have opened it, I look around and don't see obvious problems other than the unnecessary rests that Jojo mentioned - not sure what they are there for, but they are there in 1.3 as well, so I guess you entered them on purpose for whatever reason [EDIT: oh, I see, it's because this was an imprt from Finale, and Finale required you to enter rests in order to be attach chords]. So what do I need to do next?

If you are saying that on your system, you don't see any chord symbols, that could indeed be due a bad installation. MuseScore needs to be able to load the chord description file you have defined for the score - in this case, cchords_muse.xml. That is located in MuseScore's own "styles" folder. Assuming you run "mscore" from MuseScore's own "bin" folder, that should be all that is needed. But if you are running that file from some other location, that would cause a whole slew of problems, with playback, chord symbols, templates, etc.

In reply to by Jojo-Schmitz

Jojo & Marc,
Thanks for the reply.
Jojo, at your first answer, that is the problem for me too! In 1.3 I have the layer/voice 4 with the slash notation and the attached chords but in 2.0 I see invisible rests and no chords. Apparently there is a difference in format between 1.3 and 2.0.
Thanks for your comment-194191! That solves the reason why I cannot hear any sound and cannot change instruments. Regarding your comment-194211, the chords are in Jazz. I will attach a .pdf of 1.3.
To Marc, I think you opened my score in 2.0 under Windows and apparently there the display is correct(?) see the .pdf file.
Joep april-in-paris-2pno.pdf

Attachment Size
april-in-paris-2pno.pdf 178.74 KB

In reply to by J.L. Blom

No, there is no "difference in format", at least nothing relevant here. Both 1.3 and 2.0 require the presence of the cchords_muse.xml file in order to render the chords - it is what contains the rendering instructions. The difference is simply that your 1.3 installation is correct so it contains this file but your 2.0 installation is apparently not correct so it does not contain this file.

I opened your score in Linux with no problems - the chords show up just fine - but I have MuseScore installed correctly. It is not enough to have the executable file itself. You need to have an entire /opt/MuseScore2 folder structure with "bin" and "share" subfolders folders and eventually down to the subfolders "styles", "templates", "sound", etc. This is all setup automatically when you build MsueScore itself and run "make install". And it is also done automatically in any "official" package made for an actual release. But for the unoffical beta builds, I think you need to create that structure yourself somehow - perhaps by first doing a full build on your own at least once. That's just a guess, though. I really don't know anything about the process by which the Linux builds ahve been made available.

In reply to by Marc Sabatella

Marc,
Thanks! for your elucidation. I know know what to do and will do it today. Time is somewhat pressing as we want to perform my arrangement of "A Foggy Day In London Town (G. Gershwin)" at the end of this month together with "April in Paris" and some older arrangements and we both are not very good "prima vista" players (most jazz pianists seldom are!).
Thanks again,
Joep

In reply to by Jojo-Schmitz

As you can see in the attached script (mscoremaj), «make install» is run, line 42 (or at least I think that it is)
But, to use mscore (trunk) on my computer I use another script (lancemscore) who doesn't launch the «installed» mscore.
And, moreover, searching for files named yesterday «mscore» in the whole tree I find only the one in ~/musescore/MuseScore/build.release/mscore/

you surely understand that I don't master compilation mysteries.....

Attachment Size
mscoremaj.txt 2.2 KB
lancemscore.txt 207 bytes

In reply to by Jojo-Schmitz

Thanks. Indeed this ~musescore/MuseScore/build.release/install_manifest.txt
gives the list of installed files.

However the 2 first ones are
/usr/local/share/applications/mscore.desktop
/usr/local/bin/mscore

the .desktop one should in my opinion translate in a menu command for mscore. However I can't find it in my menu.
And if I dblclick the second one nothing happens
I tried also to run it from terminal
leleu@leleu-portable:/usr/local/bin > ./mscore
This application failed to start because it could not find or load the Qt platform plugin "xcb".

Reinstalling the application may fix this problem.
Abandon (core dumped)
with no more results
I tried through a script
#!/bin/bash
#lancemscore

export QT_PLUGIN_PATH=/home/leleu/Qt5/5.3/gcc_64/plugins/
export LD_LIBRARY_PATH=/home/leleu/Qt5/5.3/gcc_64/lib/

cd /usr/local/bin/
./mscore
also without result/// edit this script does launch mscore trunk (When I first tried there was a running instance of mscore)
and I notice that this /usr/local/bin/mscore is only 20.7 Mio , which seems silly.

I'll check next occurences

In reply to by robert leleu

Maybe this is naive, but if you are running "make install", you should have a full installation at /opt/MuseScore2. That is where you should be running from, not build.release. And that is what you should be tarring up and uploading. Is there some reason you aren't doing it that way?

In reply to by Marc Sabatella

The only reason to do it my way is that I don't understand compilation, and that I survived the evolutions of git and Qt by trials and errors. My beginning being a script received from the previous compiler.

And one of the results is that there is no «/opt/MuseScore2» (and in fact no ..../MuseScore2) on my computer.

In reply to by robert leleu

Marc, Jojo, Robert,
I thank you all for the valuable comments that together gives me the complete information to build MuseScore 2.0 from the source.
I have incorporated all advices and in short:
1. I have modified the Path to point to where I had installed Qt5.3 (/opt) and followed the instructions (as per thread .../compile-instructions..) and all seemed OK.
However a last stumbling block occurs in the last make step where it says:
"Building CXX object manual/CMakeFiles/genManual.dir/genManual.cpp.o"
Ther it gives the following error:
"In file included from /opt/Qt/5.3/gcc_64/include/QtQuickWidgets/QQuickWidget:1:0,
from /home/joep/MuseScore/build.release/all.h:159,
from :0:
/opt/Qt/5.3/gcc_64/include/QtQuickWidgets/qquickwidget.h:101:40: error: ‘QQuickWindow::SceneGraphError’ has not been declared
void sceneGraphError(QQuickWindow::SceneGraphError error, const QString &message);
^
In file included from /opt/Qt/5.3/gcc_64/include/QtQuickWidgets/QQuickWidget:1:0,
from all.h:159:
/opt/Qt/5.3/gcc_64/include/QtQuickWidgets/qquickwidget.h:101:40: error: ‘QQuickWindow::SceneGraphError’ has not been declared
void sceneGraphError(QQuickWindow::SceneGraphError error, const QString &message);"

So it seems some text is not declared but honestly that is at this moment a little beyond my understanding. Maybe someone with a deeper knowledge of the compilation knows how this can be solved.
But up till now many thanks,
Joep

In reply to by robert leleu

Yes, sorry, I forgot "make install" only uses /opt/MuseScore2 if you set it up that way; otherwise it uses /usr/local on Linux and your files are intermingled with other files. So definitely, use the option to specify the install folder. Doesn't have to be /opt/MuseScore2, but make it somewhere that no other application will also be using. Then you have a full tree you can tar up and upload.

In reply to by Marc Sabatella

Marc,
Thanks. I saw than when I "burn the midnight oil", you're on ~midday so your replies come when I sleep. I erroneously thought you were located her in Europe (your name sounds italian).
But thanks for the reply concerning the QWidget. I have the impression that the Qt library is rather complicated as nowadays systems are. I originally programmed in the '70 and '80's using FORTRAN and PASCAL, and originally ALGOL, in my eyes the mother of all well-thought programming languages, but I seldom program nowadays, only sometimes some scripting but that's only to make things easy. Otherwise I have to wait until the final 2.0 is released.
I now must finish my arrangement otherwise we have serious problems.
Thanks for now for all the help. I definitively switch to MuseScore and won't use Finale anymore. I even am so accustomed to the navigator that I find that much easier than the continuous display (which now is available in 2.0!!).
I'll keep you and everybody who has helped me the past 2 weeks, posted.
O and of course to everybody "A HAPPY AND VERY MUSICAL 2015"
Joep

In reply to by J.L. Blom

To give a follow-up:
I installed Qt5.4, removed a directory that belonged to "root" (which was strange) and used "make clean". Then the compilation began and took I think > 30' but now I have a running MuseScore 2.0 Beta2!. I still have to get accustomed to various - in my eyes - "quirks" e.g. the mysterious way to remove notes placed in error and the fact that I doesn't seem to be allowed to continuously vary screen size an also some matters with the layout, but I first have to study more thoroughly the program and, hey, I can write with it and the only impediment is in choosing the right notes/chords.
I will not make suggestions before I know the program better.
Thanks for now,
Joep

In reply to by J.L. Blom

Nit sure what you mean about note removal being mysterious - should be the same as previous versions. That is, select the nite, press delete. Or don't bother, just replace it with whatever different or not you intend to replace it with. If you need further help, don't hesitate to start a new thread with a title descriptive of the actual actual, sample score, etc.

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