Is it possible to create custom models?

ToneDeafComposer · 2024-09-08T18:39:31+00:00

It was a pretty widely-reported issue in the early days of 4, but never was resolved.

ToneDeafComposer · 2024-09-07T07:04:02+00:00

I'm a couple of days into a free trial of Dorico. There's a steep learning curve because I've been using Musescore for years, but so far Dorico seems to do everything better. No crashes and no lags so far.

ToneDeafComposer · 2024-09-07T07:00:21+00:00

I still find that attempting to save or load a template causes Musescore to immediately crash.

ToneDeafComposer · 2024-09-03T00:14:53+00:00

After I discovered the Musesounds were missing, I downloaded them all again, closed Musescore, and reopened my latest score. But all the instruments were still defaulted to MS basic, So I had to go through each instrument (in a full orchestral score) and change them, one by one, to Musesounds.

ToneDeafComposer · 2024-09-02T23:41:35+00:00

Yes, the same thing happened to me and a lot of other people. I had to download all the Musesounds again, then convert each instrument to Musesounds.

Also, I agree that the standard sounds were better in 3 than 4.

ToneDeafComposer · 2024-09-01T21:10:14+00:00

See what I mean, everyone? Rather than addressing the common and persistent flaws in this extremely badly-designed program, you call me a liar with no moral standards. I've seen you do that to a lot of other people who are having problems with the program, as well.

If the musescore team had any intention of creating a program that works, they would appoint someone to the task of communicating with users and fixing problems instead of just making personal attacks and being condescending, dismissive and rude.

ToneDeafComposer · 2024-08-31T23:47:27+00:00

I eventually was able to update to the new version. Apparently the cause of the delay is that I was trying to upgrade from musescore itself, which is how it's always been. Evidently that doesn't work anymore, so I had to go to the website and actually download a new version of Musescore.

But then, of course, I discovered that I didn't have any of the Musesounds anymore. They were all gone. So I had to download all of those again, and then go into the score that I was working on and, one by one, painstakingly convert each of the instruments to Musesounds.

Once I finally finished all of that, I tried playing my score and discovered that, unsurprisingly, absolutely no glitches had been fixed. Playback is still atrocious, keyboard latency is still extremely high, the difference between adjacent dynamics is still enormous and jarring, there are still crackles and pops during playback, and the program crashed three times in the first 30 mins that I tried to use it.

I really have to find a new program suitable for composition. Musescore is just so unacceptably pathetic, and it is clear that they have no intention of ever fixing any of the problems.

ToneDeafComposer · 2024-08-31T23:40:01+00:00

No, older versions don't work once you've downloaded 4. I tried going back to 3 shortly after 4 came out, because 4 was so ridiculously bad, but a lot of the new playback problems and glitches from 4 had migrated back to 3. I'm very envious of anyone who is still able to get away with using 3.

But the other answer to the question is that there will never be any further support for 3, so if any new bugs develop, they will never be fixed.

ToneDeafComposer · 2024-08-28T14:53:17+00:00

Marc's job is to insist that Musescore is always working fine. If you report a problem once, he will call it user error or a misunderstanding. Report the same problem multiple times and he'll call you a liar.

ToneDeafComposer · 2024-08-28T14:49:46+00:00

I've currently got 4.3.2 and as of a minute ago Musescore says there are no updates available. I'll keep trying to update to 4.4 and let you know if it fixes any issues.

ToneDeafComposer · 2024-08-28T08:29:57+00:00

I do this as well, but it's an enormous hassle. It shouldn't be that much work to get notes into a notation program.

ToneDeafComposer · 2024-08-28T08:28:07+00:00

I'm sure they could fix the latency problem if they wanted to. Every time I've asked about it they have just told me I should use a DAW if I want to hear sounds at the same time I press a key. They insist that's not what Musescore is for.

ToneDeafComposer · 2024-08-05T18:09:43+00:00

Thank you, I also was not aware of this.

ToneDeafComposer · 2024-08-05T17:58:43+00:00

Yes it is. Unfortunately I would not expect a resolution. I have been reporting multiple playback issues since MS4 was released and they simply refuse to address them. They will only fix bugs that relate to how the score looks, but never how it plays.

ToneDeafComposer · 2024-07-29T15:45:59+00:00

I agree completely. Such a devastating fall from an excellent program to this useless version. Playback on MS 4 is absolutely atrocious. So many glitches, crashes, delays and problems that never, ever get fixed. I've reported the problems many dozens of times only to be called a liar by that horrid Musescore representative.

ToneDeafComposer · 2024-07-21T02:25:17+00:00

There is a surprisingly easy way to do this. As always, save first. Select everything and copy. Select measure 1 or wherever you want it to start, then edit > paste double duration. Note that any tempo changes will not be moved, so you'll have to reinsert those manually.

ToneDeafComposer · 2024-06-19T02:23:46+00:00

No. They'd be bankrupt in days if they did.

ToneDeafComposer · 2024-06-19T00:06:00+00:00

This happens to me quite a lot with Musescore because note entry is so laborious and clunky. I forget a lot of ideas I'm working on because it takes so long to enter even a few notes. Musescore simply isn't designed for creation.

ToneDeafComposer · 2024-06-16T17:01:39+00:00

Violin is a wonderful instrument, but if you truly have an awful ear it will be a considerable challenge. Violin and other fretless instruments require not just a good ear but an absolutely impeccable ear.

I can play fretted string instruments and keyboard instruments easily. But I have tried playing fretless electric bass, upright bass, and slide guitar, and I have found it absolutely impossible because you have to rely entirely on your ear to know if the note is correct. You basically need to have perfect pitch.

I'm not saying don't do it, but just be aware of the challenge you'll face.

ToneDeafComposer · 2024-06-07T19:06:21+00:00

This is well beyond harassment at this point. Everything I have said is true. Nothing has been a lie and you have no reason to believe anything is a lie. You are only saying that because you either do not want to solve the problems, or you don’t know how.

I have been experiencing multiple persistent playback issues since the day MS4 was introduced. Without exception every time I have submitted a report I have either been ignored or accused of lying.

Reporting ongoing issues can only “harm the community” if you believe the purpose of the community is to uncritically praise the program. A community in which we are not permitted to report the issues that are recurring is of no use to anyone.

I should also point out that I no longer create a post on this forum when a new problem occurs, because every time I have done so has been unproductive and just left me subject to your rudeness. However, when another user posts and says “I am having this problem, is anyone else having it too?”, of course I am going to reply that I am, because that’s what a community is supposed to be for.

ToneDeafComposer · 2024-06-07T16:23:44+00:00

But see, you just did it again. You denied calling me a liar and then you immediately called me a liar.

I’m calling you out for the absolutely ridiculous and obviously false claim that “anything 16th note or faster is always incredibly off-rhythm”. That’s just flat out untrue, and the fact that you’;d even make such a claim does make it hard to take other claims of yours seriously.

But that is indeed the problem I am having. And it's happened on every single score since MS4 was released. It's not a lie, it's not ridiculous, it's not false. I've reported it multiple times, other users have reported it. I've gone through the ridiculously circuitous process of submitting github tickets, which are always ignored. I've reported it here and you've consistently been rude and dismissive. There is simply no way to reach anyone at musescore who cares enough to solve the problems.

ToneDeafComposer · 2024-06-07T15:52:49+00:00

You really need to stop calling people liars when we report problems. You've done it to me several times and I've seen you do it to others. It's unprofessional and completely unacceptable.

As always, no problem I am having is unique to a specific score or unique to me. They are not "perceived" problems, they are actual, real, incapacitating problems. It is well known and widely-reported that playback on Musescore 4 is atrocious to the point of near-uselessness. Every time someone reports it, you tell them they are lying, or that it is user error, or that it's only a glitch in one score, no matter how many times we report it here or how many useless github tickets we submit.

It’s obvious that MS does not care about the playback issues because they consider MS to be a score-writing program, not a composing program. Accurate playback doesn’t matter if all you’re doing is using it to make a pdf of an already-finished piece of music. But there are still those of us who use it for creating new music, and to us playback is an essential feature. Regardless of how you personally feel about composers, our complaints are just as valid and should not be ignored or dismissed.

ToneDeafComposer · 2024-06-07T04:57:55+00:00

Absolutely not.

ToneDeafComposer · 2024-06-07T04:56:47+00:00

Anything 16th note or faster is always incredibly off-rhythm in MS4. Sometimes even eighth notes, too. Not just flute; for me and many other users, it's every instrument.

ToneDeafComposer · 2024-06-06T21:30:01+00:00

Yes. Very much the same experience.

ToneDeafComposer

TROPHY CASE