Nightly build - no sound because of missing lib files

• Oct 12, 2014 - 12:34

I'm trying out a nightly build from 11 October 2014 (2.1x). I can't play my score, and the reason seems to be that the playback lib files are not included in the nightly-build download.

I imagine it is not too difficult to copy over files from 2.0b1 to allow playback. Can someone confirm or deny, and if that is so, tell me which subfolders the nightly build wants?


Comments

check in Preferences if the folder Soundfont is correct;
If the soundfont is present in Syntethizer tab;
If the directory tree is like the one in the attached image.

Attachment Size
dman S.png 217.07 KB

In reply to by ChurchOrganist

OS = Win 8.1 64-bit. Sorry for not mentioning that.

I'll check later for the soundfont folder later tonight. (Right now I have an hour to practice pieces for a concert.)

Thanks, all.

In reply to by dman

Which build was it? There are three Nightly builds listed for 11th October all with different commit numbers.

Really if you want to keep up with the cutting edge you should start self-compiling.

Once it is all set up it takes two mouse clicks to do, and you can be sure nothing has been left out of the package accidentally :)

The are a number of us from the community who would help you get that set up on your system :)

In reply to by dman

The Windows builds do include the necessary soundfonts. If you don't have sound, it's more likely a question of settings you have left over from some older incompatible build. First thing to try is running mscore -F to start MuseScore with all settings reset to factory defaults.

In reply to by Marc Sabatella

[Edited twenty minutes later: see my next follow-up! /dman]

Hmm. The executable is "nightly.exe"; I tried adding "-F" to that from the command line in Win 8, but there still is no sound. Note that this is the first nightly build I had tried. It's MuseScoreNightly-2014-10-11-1907-daf97e1. I also have 2.0b1 and 1.3 installed normally on this OS.

When I pull up the Mixer, it says the instrument is piano, but there are no sound fonts seen down below in the dialog box. Now I see from looking in the paths under Preferences (following up on @schoichi's reply to me in this thread) that there possibly some kind of a bug in how the path to the sound fonts got populated.

I extracted the compressed build-compile under drive "S:\" (my "scratch" drive) and ran the executable from there (under "S\bin\"). The other preferences paths look normal to me, and are under my %USERPROFILE% path on "C:\". But the entry for the soundfont folders says:

S:/sound;C:/Users/[my name]/Documents/MuseScoreDevelopment/Soundfonts

And there really is a "S:\Sound" [FN 1] dir that was created, although -- as stated -- the extracted build is otherwise found under "S:\bin\"

In any case, both "S:\Sound\" and "%USERPROFILE\Soundfonts\" are empty.

This is all not so important in the greater scheme of things. It's now a day later, and I will go look for a newer nightly build.

Meanwhile, sotto-voice to @churchorganist, I may try compiling later if I see the need. I run a whole, uh, church pew full of operating systems, both real and virtual, so I'm sure I'll get around to the compiling "jazz" ("all that jazz") vis-a-vis MuseScore soon enough...

Thanks to all.
/d

[FN 1]: I know that Windows convention is to use backslashes in paths and I know, as well, that modern Windowses can understand the normal-slash convention used for most other OSes, but I do find it slightly odd that the preferences file for a Windows build uses the forward- instead of back-slashes. Not important, just a remark I'm making.

In reply to by dman

I looked in the compressed archive and saw that the soundfont files are, indeed, there. I re-extracted the build (MuseScoreNightly-2014-10-11-1907-daf97e1) and now the sound plays normally. I'm not sure why those files weren't extracted along with the rest of the build last night when I first did it.

Anyway, now everything's copacetic. Thanks.

In reply to by dman

Computer science for me is mysterious.
Following a suggestion by Marc I created this situation:
1.3 and 2.0 b1 normally installed (C: Program Files);
Nightly, I created a folder named MsS Nightly. I delete the contents and then I extract the downloaded versions in it.
The folder (hidden) AppData / Local / MuseScore / MuseScoreDevelopment contains only the custom workspace and little more.
This solved for me a few minor problems.
Buona musica.

Attachment Size
folder.png 132.89 KB

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