No Playback Sound
Just downloaded MS2. something (.02?) My first attempt at editing a 1.3 file with 2.02-- 2.0 claims my 1.3 file "corrupted" pg. 12, Measure 60, checked it out, can't see anything wrong. Would this be why MS 2 won't playback my 1.3 score, Ansazi Act II file #5 "When Earth Was Younger"? (It works fine when I just open the original 1.3 file, and also worked on MS.com fine) on MS2.0 the metronome clicks, and you can select individual notes and they play, but it does not do playback when you click on the Play arrow, Just silence except for the metronome clicking . I tried another file and MS2.0 claims it's also corrupted, when I open the 1.3 file with MS 2.;0 If MS2.0 is going to see all my 1.3 files as corrupted, maybe I would be better off to ignore the new MS 2 and just use my 1.3 files--except any of those cannot be uploaded to MS.com after Sep 1st. My Opera was entered into MS 1.3 in the faith that those files would work with professionals for an operatic performance at some point--I do not need a bunch of buggy stuff showing up on 2.0 when I open and/or edit a 1.3 file with 2.0. Any advice/explanation anyone? Thank You Del Hudson
Comments
No sound on playback would mean somehow the installation did not go correctly. perhaps you had an older version of 2.0 also installed but in a different location and MuseScore is trying to use those settings instead instead. Anyhow, all should be well if you follow the isntructiosn under "Revert to factory settings" in the Handbook for 2.0.
As for the corruption, that is unrelated. Unforutunately, 1.3 had a number of bugs that could cause corruption, and it was not smart enough to detect them. 2.0 fixes most of those bugs, and it is also smart enough to detect the corruptions. Not loading a score into 1.3 won't eliminate the corruptions that are already present; they will remain there waiting to wreak further havoc on your score. So you definitely want to fix them rather than let set sit there just waiting for an opportunity to cause a crash or create worse problems.
See https://musescore.org/en/node/54721 for advice on how to fix these corruptions.
In reply to No sound on playback would by Marc Sabatella
OK, So i can't plan on ignoring the. corruptions.! I gather 2.0 only informs you of the corruptions it did NOT fix automatically? (I did not already have an older version of 2.0 downloaded already.) WIll go on the link you provided on fixing corruptions. I thought my labor was done on my 1.3 files--did not know 1.3 had some bugs built in.
In reply to OK, So i can't plan on by delhud2
To be clear: 2.0 won't fix corruptions that 1.3 already introduced. I just meant that 2.0 fixed the bugs that caused those corruptions in the first place, so hoepfully it won't create *more* corruptions.
All versions of all programs have bugs. Each new version usually fixes bugs that discovered in the previous version, but in the process of fixing them and adding new features, sometimes new bugs are introduced. It is not realistic to expect any version of any program to have *no* bugs. But 2.0 definitely fixed a lot of thr bugs in 1.3, just as 2.0.1 fixed bugs in 2.0 (some of which existed back in 1.3 as well, others of which were new), and just as 2.0.2 fixed bugs in 2.0.1.
In reply to To be clear: 2.0 won't fix by Marc Sabatella
OK, That makes it much clearer for me about bugs! I agree one would not want problems caused later by not fixing the bugs! i will experiment a bit more, and if I still have the above- mentioned problems, will post specific score/location.
1.x dodn't check for such corruptions, 2.0 does. See https://musescore.org/en/node/54721 for how to fix them.
Oops, too slow ;-)
In reply to 1.x dodn't check for such by Jojo-Schmitz
Hello to all.
@delhud2
Try if all goes well, I allowed myself to intrude to encourage you to download 2.0.2 ;-)
In reply to Hello to all. @delhud2 Try if by Shoichi
Hello, I did download 2.0.2-- it would not do playback sound. Marc says the installation may not have completed properly. OK--thanks, I will try your link to my file. I also found slurs not showing up properly on 2.0.2, though they are fine on 1.3! HEY-- I just tried your link, sound does play! How did you fix that? AM I going to have to fix all my files? (Marc says I should) I thought my labors were over on my ANasazi files!? I did find an anomaly on the file #5 Andante tranquillo quarter note=72--the 2.0 playback speed is way too fast! I have a precision electronic metronome which I use for settings--72 on it is way slower than on 2.0.2! ?? I hate strange things happening like this. On MS.com, the speed plays properly, and in my 1.3 file does also. Strange!
Thanks for getting the file to do playback!
In reply to Hello, I did download 2.0.2-- by delhud2
If you have sound, you should have sound for all scores. if not, you need to post the specific score that you are *not* hearing sound on in order for us help.
As for corruption, I certainly wouldn't want to have corruptions in my scores. Up to you whether you are willing to risk crashes and potential loss of work.
As for slurs and tempo, again, as always, it is difficult to offer help unless you post the actual score you are having problems with and *precise* step by step instructions to reproduce the problem.
In reply to If you have sound, you should by Marc Sabatella
have spent an hour deleting my original MS2.0.2 download, since still no sound on attached score. Could not get factory restart to operate.I re-downloaded 2.+ since you said the only possible reason for no sound would be faulty download of MS2+ etc. In my new download, the is STILL no sound--individual notes selected will sound, but nothing on Play button, measures light up as the playback scan is going on, but not a sound to be heard. Please see attachment below. In 1.3, the playback is perfect as always. Frustrating and time-consuming in MS2. Soichi got it to play for him, but did not tell me how he did it. What on earth is going on, I wonder?
In reply to have spent an hour deleting by delhud2
That file is corrupt... but it does play back when loading it anyway.
In reply to That file is corrupt... but by Jojo-Schmitz
I'm trying another download of the MS2 software. So far, it does not play for me either!
In reply to have spent an hour deleting by delhud2
What do you mean you "Could not get facotry restart to operate"? Which step of the instructions *specifically* did you have trouble with? What did you expect to see happen, what happened instead? Anyhow, re-downloading the software doesn't fix most installation problems - you *need* to do to revert, because settings are normally preserved no matter how how many tiomes you re-donwload or re-install.
But if you are hearing sound when clicking individual notes, that suggests something different might be going on. Perhaps you have muted or soloed tracks in the mixer? Your score plays back fine for me as well.
What soundfonts (if any) do you see listed in View / Synthesizer? Do you see sounds selected for each track in View / Mixer?
In reply to What do you mean you "Could by Marc Sabatella
I will try to explain-- on the 2.0.2 first download, I have MS manual which says to press the Windows key, then Browse, then search for mscore.exe in my computer.( I have Vista-tried those directions also) Tried different things like looking for MS programs in my computer, etc. Computer kept saying muscore.exe not found. This was for the 2.+ version. (Not my 1.3) I will check those things you suggested. It looks like I may have to find a way to factory reset 2+, I did notice my new download of 2.+ did not change anything--it seemed to know already about my 1.3 file being edited by 2.+, had it in my recent files already! (And still no sound, of course.)
SO when I look in view Synthesizer, etc., will those be what I had set in 1.3? Even though this score is now being edited by 2.0.2? Sorry, but all this is confusing for someone who did NOT major in computer science or something-- (I was a Music major) Appreciate your help.
In reply to I will try to explain-- on by delhud2
I think you must be looking at the 1.3 version fo the Handbook. The 2.0.2 version says to look for MuseScore.exe. See this link: https://musescore.org/en/handbook/revert-factory-settings-0#instruction…. it even tells you exactly where to look for it.
When you look i View / Synthesizer, what you *should* see is FluidR3Mono_GM.sf3, or something like this. That is the soundfont, the thing that allows MuseScore to play sound. If your installation is bad, you will probably see no soundfonts listed in that dialog.
If you don't see anything listed in the dialog, then the revert procedure *will* fix it. What probably happened is that at some point - perhaps months ago, perhaps more recently - you had installed an earlier 2.0 version - maybe the Beta version, or maybe 2.0 itself, or 2.0.1 - then deleted that installation, but now MuseScore is still trying to find the soundfont in that old installation.
In reply to I think you must be looking by Marc Sabatella
Hello, You hit it right on on one of your suggestions! I viewed Mixer and found at some point when checking voices I had 2 Trumpets set on Solo! I clicked on them, and now the score is playing fine! Hallelujah. However, I save all these threads in a folder on my gmail, and maybe your link to revert to factory settings will come in handy sometime. Synthesizer is set on Fluid3mono, etc. Wondering though, I had a setting before on 1.3 or earlier even "Sinfonia" sound or something like that. I remember it was supposed to make the sound better-would you know what that was all about? Thanks again. P.S. The MS Manual I have printed out is for 0.9.6.1. Pretty out of date! ( I will order your book in near future.)
In reply to Hello, You hit it right on on by delhud2
Glad the mixer suggestion did the trickl!
I am guessing maybe you had tried using the "Sonatina Symphonic Orchestra" soundfont? See the section on Soundfont in the Handbook for how to install it in 2.0. It should work the same basic way as 1.3, except now you can have multiple soudfonts installed whereas 1.3 only allowed one at a time.
But if that is the soundfont you were using, you would also have had to change all your mxier settings to get it it to work, and it wouldn't have sounded right when uploaded to msuescore.com. So perhaps it was something different you were using, not Sonatina.
Anyhow, the FluidR3 soundfont that is the default for 2.0 should already sound much better than the old default soundfont for 1.3. And it is what will be used on musescore.com anyhow. So it's not really worth the trouble of changing unless you have some specific need.
In reply to Glad the mixer suggestion did by Marc Sabatella
Hi again, This is going to be learning curve al lright-- Every time I quit the file mentioned, MS 2 resets the 2 Trumpets to SOlO, so no playback until unclicked each time you open it! Have never seen this before. Also, on Tempo marking, I right-clicked on it expecting "Tempo Properties" to display but it did not . For some reason quarter note = 72 is way too fast in 2.+ and I wanted to slow down the beats. On the Soundfont, I will just leave it on the 2.0.2 setting and let it be. It must NOT have been Sonatina--or I don't see how my stuff on MS.com would be listenable, or would it just be lesser quality? Hope this did not affect all the files uploaded to MS.com?! Questions, always more questions. Leading to headaches--
In reply to Hi again, This is going to be by delhud2
MuseScore doenn't "reset" the trumpets - if you change something in the score, you need to save it or it won't be remembered for next time. Same as any other change.
Tempo no longer requires a separate dialog - it's done through the Inspector now, which is normally always visible. See the section on "Tempo" in the Handbook.
The meaning of quarter note has not changed in 2.0, nor has the meaning of 72. But 2.0 now actually reads the text of your tempo marking, so a tempo marking of quarter note = 72 should now automatically produce the correct playback, no need to even touch the Inspector. You *can* use the Inspector to "lie" if you really want - having the tempo makring say 72 but really be 350 for playback. Without seeing your score, it's impossible to say for sure what might be happening, but I'm guessing it's something along those lines.
In reply to If you have sound, you should by Marc Sabatella
Sound problem fixed! I had 3 Trumpets set on SOLO! So happy I now have Playback on MS2.+
In reply to Hello, I did download 2.0.2-- by delhud2
@delhud2,
I do not think that you have learned to use 1.3 from night to morning but you used it very well. Get familiar with 2.0.2, which contains many improvements, and you will not regret it.
Note that you can create a folder in which to install the portable version 1.3 and save in it your old scores. Then you can burn into a CD these files and thus have an additional backup copy (in the attached image: an example of what I mean)
Finally a good investment would be to get a copy of Mastering MuseScore:
https://musescore.org/en/node/64711
I apologize for the 'OT
In reply to @delhud2, I do not think that by Shoichi
Yes, I will get Marc's book at some point. Right now I just want to get started editing my operatic 1.3 files and fixing the bugs that I did not know were hanging out in 1.3! Hard to do when you cannot even get any sound on playback of those files in 2.0.2 ! Apparently 2.+ is going to consider ALL my 1.3 files corrupt! I have faith that the new MS version will be marvellous once I get it working smoothly.
In reply to Yes, I will get Marc's book by delhud2
I wouldn't assume *all* your files are corrupt; 1.3 wasn't *that* bad. On average, I'd say there is probably a corruption once every 1000 measures or so (wild guess) at most.
In reply to I wouldn't assume *all* your by Marc Sabatella
OK- Am on Semi-break for late summer--maybe by Fall I will get bugs all fixed! However, on attached file (Same as you had earlier today) I clicked on "details" on the corrupt file notice, and it took me to : Measure 60, staff 5, voice 2 too long. Expected: 3/4; Found: 4/4
Measure 60, staff 6, voice 2 too long. Expected: 3/4; Found: 4/4 pg.60 on below attachment.I don't see anything wrong--unless I often set "invisible" for rests on separate voices. If I can't tell why something is bugged, I sure can't fix it. Please see attached file if you have time and see if you can see what is wrong with the "beats" it's talking about. Thank You
In reply to OK- Am on Semi-break for late by delhud2
I opened with 2.0.2;
Looked at the details and deleted the rests of the 2nd Voice in measure 60, staves 5 and 6,
Saved by adding a B to the name.
In reply to I opened with 2.0.2; Looked by Shoichi
Hello, Thanks for doing that-- but what do you mean by adding a B to the name? Did I have rests set on invisible that you deleted, or were they visible?
In reply to Hello, Thanks for doing by delhud2
I have attached the file that I have corrected and added the B final because you can recognize it.
As mentioned, I applied what is explained here: https://musescore.org/en/node/54721
In reply to I opened with 2.0.2; Looked by Shoichi
Thanks--So does that mean the file is now automatically corrected on my PC? (I usually don't do music technology on weekends, but nay try to occasionally.) Nice of you to help--
In reply to @delhud2, I do not think that by Shoichi
I often do not understand techno-speak. What are portable versions of 1.3 ? What does that mean?
As you say, I did work hard on understanding 1.3, but did not know more work would have to done later on it because of bugs in it!
In reply to I often do not understand by delhud2
I try with some "Illustrated" explanation
In reply to I often do not understand by delhud2
Not just because of bugs in 1.3; 2.0 adds many new features and therefore will require a bit of a learning curve. Same with any major upgrade.
Portable versions of software are versions explicitly designed to be soemthing you can install on a USB / flash drive (those things shaped like a stick of gum that you can store files on). With a portable version of MuseScore, you can just stick the flash drive into the USB port of any computer and run MuseScore without needing to fully install it on the computer. I don't think there is any particualr advantage to you in doing this.
In reply to Not just because of bugs in by Marc Sabatella
I have saved ALL my Opera MS files (1.3) to a "Memory Stick" that I keep in a Security metal Box.So I gather that those could be played on ANY computer if the "flash drive" was stuck into it. I guess memory stick is an old name of them?
In reply to I have saved ALL my Opera MS by delhud2
Not necessarily "old", just different. Memory stick = flash drive = thumb drive etc.
In reply to Not necessarily "old", just by Marc Sabatella
Hello everyone,
Thanks for all the further info given.
I am entering a short piano piece--my first score created on MS2. MS2 is really marvellous, a big improvement--I already noticed how on slurs its really gauges what you need across the notes! And on chords you don't need to use shift key , etc. Am just beginning to discover MS 2 +
I DO though already have a problem-- I ran into on SOUND. i set the dynamics on mf, and I have my volume turned up to 100% for the playback, but get on soft about mp or less volume of sound. Odd though, that on my Anasazi files from 1.3 , the dynamics/volume are normal on playback in MS2+. Since this piano piece (See below) is being actually created on MS2, it somehow does not have much volume on playback. ??? I looked in Edit Preferences but did not see anything about sound volume to choose.maybe there are new settings or something in MS2 that have to be done?
In reply to Hello everyone, Thanks for by delhud2
Open: View / Synthesizer (see attached image).
Do some experiment with the settings. Note that you can save the settings for the individual score (Save to Score) or default (Set as Default).
https://musescore.org/en/handbook/synthesizer
In reply to Open: View / Synthesizer (see by Shoichi
OK, I read the handbook info on Synthesizer. I will experiment with some settings, etc. Thank You. I am really excited about the MS 2+!
In reply to Hello everyone, Thanks for by delhud2
No, this is perfectly normal. Create the same music in 1.3 and it will play back at the same volume, more or less. When you say you have the volume set to 100%, I guess you mean the Play Panel, but be sure to check the overall volume in View / Synthesizer as well. Or perhaps you had long ago turned up the volume in the Syntheszier window in 1.3 and now simply need to do the same in 2.0 to get the same result. But I think maybe you are being fooled because you were listening to your scores that had lots of instruments and hence sounded loud for the same reason a full orchestra sounds louder than a single flute :-).
Also, the default soundfont for 1.3 and 2.0 is different, and each soundfont has different volume for each instrument in an effort to get what the soundfont designer thought would be a pleasing blend. This may result in some instruments being slightly louder by default in 1.3 than 2.0 as well as the reverse.
In reply to No, this is perfectly normal. by Marc Sabatella
Thanks for the reply--However, I understand what you mean by an orchestral score naturally sounding louder than a solo piano, \but I am a Pianist and I know when a piano is putting out the right volume, or is staying too weak for an mf setting. (I'm not trying to be a "smart alec") ha ha
Do appreciate your reply and I will try the suggestions you and Shoichi also sent me.
I wish MS2 had been out when I was doing the Opera files, some of the work would have been easier! Even from what little I have seen of it so far, it has a lot of big improvements! ON the volume, I meant I turned up my PC volume controls to 100% and still got very soft sound on piano playback.
In reply to No, this is perfectly normal. by Marc Sabatella
Exasperation-- I viewed Synthesizer, set the volume way up (it was about on 40%, then tried saving to score and also setting as default. All I am getting now is even fainter volume on playback. I also looked at Preferences under edit--looked at I/O, it had Microsoft Sound Mapper set on out put, I tried Input, no difference- I'm getting very faint now ppp sound on playback. It looks like the soundfont is Is the right MS2 soundfount.
Also, MS keeps setting the two Trumpets in opera file on Solo!! There is no Save on the Mixer box, so I used Save under File, then dialogue asked me if I wanted to Save again, and it said this file already exists, do you want to replace it? etc, Whenever the file is closed and reopened, the 2 trumpets are back on Solo. I NEVER had any trouble like this in 1.3 with Mixer Settings I simply do not GET it.
So now I am back again to No sound, basically, it's barely audible. Something somewhere must be turned way down.I understand the Mixer settings for each instrument, they're OK. Needless to say, it's not my PC speakers, they're way up to max. Could MS2 be doing some kind of bugs with the 1.3 file? THe Rondo piano file of course, is originally done on MS2, though. and it's inaudible almost too. Can anyone think of anything more on this? (The Sound is a more important problem than the trumpet thing.)
In reply to Exasperation-- I viewed by delhud2
When in doubt, follow the Handbook instructions under "Revert to factory settings". Hard to say what might be messed up, but this fixes anything that is under MuseScore's control. Realize also that Windows has its own system mixer and can set the volume for each application differently, you shoud also check that MuseScore isn't turned way down there.
If you are having problems with the solo control in a particular score, please start a new thread and post the specific score you are having problems with an precise step by step instructions to reproduce the problem. I'm guessing, though, it will turn out that you keep accidentally re-opening the original file rater than the new one you are saving.
In reply to When in doubt, follow the by Marc Sabatella
OK--where do I find the Windows system mixer volume controls? And I will later start a new thread then on the Solo control-- always before in 1.3 all I had to do was check for solo and after I was through using it, uncheck it, and everything was fine from then on.
In reply to OK--where do I find the by delhud2
The Windows mixer control is accessed differently for different versions of WIndows and different audio harward, so you might have to search around for information. Usually though there is some sort of volume control icon (eg, in the taskbar at the bottom of the screen), and often right-clicking it will give you options to display the mixer.
The solo buttons in 2.0 work *exactly* the same as 1.3. Again, I suspect you are simply being confused and accidentally loading the original version of the file again rather than the version you saved. Perhaps you have saved it to a different folder.
In reply to The Windows mixer control is by Marc Sabatella
Hello, I find that I have always been using the Windows control! I set it up to 100 %volume yesterday, and made no difference, so I can check that one off--So on the Solos control, if MS says after saving the change: "This file already exists. Do you wish to replace it?" Then I should click "yes"? I didn't think you would want to replace a whole larger orchestral file for one little change? Or maybe I should just click on the X and the message comes on, "do you want to save the changes you made to--_" and click Yes. Then the file closes, and I would have to reopen the new version and hopefully the Solos would be unchecked? Solos could be a problem if you had checked say, an entire brass section from the full orchestra, and had to uncheck all of those every time you opened it.
In reply to Hello, I find that I have by delhud2
Yes, just as with 1.3, or any program at all, really, if you make changes, you need to save the file or else the changes won't be remembered. Again, none of this is any different from any other version.
Now, that said, it's up to you whether when you save the file, you replace the existing file or not, but we have strongly advised you before *not* to save over a 1.3 score, and instead make a copy of it. That is why you see that dialog - MuseScore is trying to warn you against writing over your original 1.3 file. So save it to a different folder, or under a different name. You'll only see that warning on save the first time you try to save a score originally created in 1.3.
In reply to Yes, just as with 1.3, or any by Marc Sabatella
OK--understood. What I don't understand is I never had to go on Play Panel FIRST and reset volume every time before I can do Note Entry and/or Playback. I would think there would be a default option?
In reply to OK--understood. What I don't by delhud2
If the play panel is set to 0, it's because you set it that way at some point. MuseScore does not do this by itself - not in 1.3, not in 2.0.
In reply to If the play panel is set to by Marc Sabatella
OK.
In reply to OK--understood. What I don't by delhud2
"I would think there would be a default option?"
The interesting thing is that the volume slider in the Play Panel in reality controls exactly the same thing as the volume slider in the Synthesizer—so much so that if slide it up to the top in one window, you'll see it slide to the top in the other. So, the "Set as Default" button in the Synthesizer is probably what you need.
In reply to "I would think there would be by Isaac Weiss
OK, Zack, Thanks for the comment on this--i will try that. I really like MS2, the many improvements, etc.
In reply to The Windows mixer control is by Marc Sabatella
Hey, I feel really embarassed! Sound problem solved--The Play Panel volume was set to completely 0--off. I turned it way up and now the sound is fine on both files I tried it on.
Oh, OH, it turns out that the Play Panel Volume is resetting itself to 0 Volume . I don't remember having to set the volume every time you did a playback on 1.3. I never or seldom used the play panel, just the play arrow at the top. DO I now have to RESET the volume every time a Play a different file on MS2.0.2? Never had to to that before. I also find that every time I open the file below to do Note Entry, I must first go to view and Play Panel or the notes don't sound as they are being entered! Never had to do that before, either. What is wrong? I HOPE it's not a new feature of MS2.
In reply to Hey, I feel really by delhud2
Again, if you make changes to a file, you need to save it or those changes won't be remembered. This is not unique to 2.0, it was true of 1.3 and has been true of practically every computer program ever. If you change something in a file, you need to save it.
In reply to Not necessarily "old", just by Marc Sabatella
Don't forget "USB key." ;-)
In reply to Don't forget "USB key." ;-) by Isaac Weiss
What do you mean by USB key? Not surehow this relates to playback sound volume?
Just thought of something, maybe I did not click on piano keyboard in instruments after I clicked on"Grand Staff" when setting up the new score. Not sure. maybe Grand Staff comes with an automatic soft piano sound??
In reply to What do you mean by USB key? by delhud2
No, USB key is just another term for thumb drive or memory stick (flash storage).
The Grand Staff comes with the exact same piano sound as if you specified piano as your instrument—essentially, it is a piano template under a different name. But probably all you want to do is open the Synthesizer, raise the volume level a little, and press "Set as Default."
In reply to No, USB key is just another by Isaac Weiss
OK! I will try the Synthesizer. Good to know about the grand staff, as I did not remember going to instruments and keyboards/piano.! Thank You.