48kHz instead of 44.1kHz functionality
Maybe there's a way to change this that I don't know about...but I think it's ironic that I was just redirected to a tutorial video about Musescore that wouldn't play back BECAUSE I had Musescore open. It would be great to not have the software hogging the audio card - seemingly because it functions in 44.1 instead of 48. Everything else on my computer functions at 48. It's pretty frustrating to have to shut down the software so that I can run other things. Of course, once you've got other stuff running, you can then restart Musescore and it works fine. Just a nuisance to have to go through that every time.
...and...on top of that, the video was for version 2, not 3. So the search continues. Can anyone tell me how to put in chord symbol text for version 3? I'm looking for that "fake book" font for "F#7" and the like.
Thank you for your attention!
~Aaron
| Attachment | Size |
|---|---|
| MusescoreFail1.JPG | 78.52 KB |
Comments
I can't answer about the sample rate for the synth, but nothing has changed about chord symbol entry between MuseScore 2 and 3 aside from the name of the menu to go to - it's Format / Style instead of Style / General. Then select Chord Symbols and the "Jazz" option as before. Or, make life simpler and just create your score using one of the three "Jazz" templates that have this and more set up for you already.
In reply to I can't answer about the… by Marc Sabatella
A very belated thank you, Marc!
I don't know if you're using Linux, WIndows or Mac because you didn't tell it.
I use MuseScore 3.0.2 into Ubuntu Studio 18.04.1 LTS (64 bit Linux), and this is the same in MuseScore 2.3.2, you can change the audio resolution very easy!!!
Go to the "PREFERENCES" menu, tab "INPUT/OUTPUT".
You have to use "ALSA Audio" and, then, you can change the sample rate at your will.
That's all, folks!!!
In reply to I don't know if you're using… by jotape1960
And if you prefer to use jack than musescore uses whatever frequency the jack server was configured to run with (jack forces all clients to use the same sample rate).
In reply to I don't know if you're using… by jotape1960
Thank you for your responses! Sorry, I should have specified. I'm using Windows, but I'm also using an audio interface (Roland OCTA-CAPTURE) that defaults to 48kHz (because all of my other software does) until I initiate Musescore, which then hijacks the audio to 44.1kHz. If I want to use any other software, I then need to close Musescore, open that other software (at which point it returns to 48kHz), and then reopen Musescore, which will then function in 48kHz. I just wish I could set the default in Musescore to 48kHz. Does that make sense?
In reply to Thank you for your response!… by aaron.c.samuels
Yeah, I'm having the exact same problem. I'm experimenting with Asio, I'll try later with Jack audio. I never used jack in windows, only linux, but it should work as well. I just find it funny having to use jack in 2019...
Call the inspector (not F8)! Call the gendarmerie at once! MuseScore has been found with its hand in the till; this is (as Jeetee suggested) why other apps' audio is corrupted when MuseScore is open. This just cannot be right. This is a red-flag emergency, MS corrupting the behavior of other apps (although one could claim it is a flaw in MacOS).
Are my forensics not in order?
In reply to Call the inspector (not F8)!… by [DELETED] 1831606
Amused, are we? Hehe
Also, Windows, not MacOS. Which, to speak the truth, could be worse. But still...
In reply to Amused, are we? Hehe Also,… by pirosonico
These audio corruptions have been plaguing me since 3.0; My recent discovery that they were reliably inflicted on other apps when and only when MS was open was both a source of relief (that my new Mac was not faulty) and dismay.
In reply to Call the inspector (not F8)!… by [DELETED] 1831606
Assuming this is in fact what is going on, to me it seems that would indicate a bug in the OS. An application requesting to change the sample rate it uses should not even have permission to change it on a system-wide level.
In reply to Assuming this is in fact… by Marc Sabatella
I could not agree more, but I have no access to the MacOS bug forum....(it is likely there is already a lot of dependence on this behavior). The best we can ask for is a way to opt for 48 in MS.