![]() So no good for Mozart's Queen of the Night aria. Arguably shouldn't be done, but for example try to get a "soprano" to sing higher than top C in MU4 and "she" won't. Also note that sometimes one has to go back to MS Basic in oder to get some "out of range" notes. I have been trying to mix Spitfire BBC SO Discovery with Muse Sounds and LABS. I suspect that this may be the root of many V4 problems But all but the desktop only have a 2 core CPU. All my computers have SSD's and at least 8 gigs of ram. DAW users will tend to have those as well as 32 to 64 gigs of ram. How many of us that aren't professional composers have a computer that has an 8 core CPU. Of my five computers, only one scrapes its way up to the minimum requirements. It is worth noting at this point the system requirements for V4. They have a lot more punch and power when needed. A phrase marked soft will get louder as it approaches a louder dynamic marking. Some sounds have a tendency to anticipate volume changes. ![]() As noted, solo brass sounds are pretty sloppy. MuseSounds are pretty good, but hardly the best of any notation software. ![]() ![]() Mixdown was OK but a real pain to use to make adjustments. Experimenting with sample rate and using my Focusrite finally let me hear playback in real time. Finally, after months, I can listen to V4 with almost no stutters. Below is the generated crash report which I have sent to Apple numerous times.Many thanks to the posters in this thread. I know others have had this experience, yet I don't see much attention in GitHub as a serious concern. Looks like I am, once again, going to have to resort to using TimeMachine to go back to when the program ran. I have changed sound output from digital to analog devices without effect. ![]() I have turned off/on the computer, deleted and reinstalled the MuseScore, MuseHub, Musehub instruments all to no effect. Now MuseScore 4.1.1 no longer opens at all in Mac OS Ventura, nor Sonoma (MuseScore 3.6 works perfectly). It was generated every time I quit the program. Prior to this event, simply quitting MuseScore4 generated a crash report on my Mac M1 Mini. I was trying to uncover the reason why my midi keyboard transport buttons do not function as toggles (I have to hold the buttons down continuously for them to work it works perfectly in MuseScore 3.6.+) Somehow resetting my MS4 preferences to "default" caused MuseScore to crash. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |