New parts don't follow existing settings. Program crashes when applying from a different part.

• Apr 2, 2025 - 06:08

I have a score with a few parts already set up.
When adding new parts, they don't follow previously existing settings.
When applying pre-existing settings from an older part ("apply to all parts"), the program then crashes.


Comments

In reply to by lbonocchi

Indeed I got a hang here that ended up crashing. But there are so many parts... (I've given up trying to count them!) and so many settings that can potentially be incriminated. Too cumbersome and complex to check. Others maybe, but for me, I give up.

Are you able to reproduce the issue from scratch with a short score (one page or a few measures), with one-two-three parts, to understand what might be setting it, or what settings might be triggering it?

In reply to by cadiz1

OK, so here is when I lose it a little.
You see, this is what I have to deal with every time I want to perform a serious piece I made in Musescore.
Since I began using it in 2013, parts have been buggy as hell and caused all kinds of problems.
But instead of fixing those like any serious notation program, muse group rather make hardware-intensive paid sounds for people to play composer.

Every single serious piece that I made (especially the larger ones like this one) naturally ended up having technical issues related to parts. Either parts never conforming to my settings, or were never named the way I named them, or always looking horribly squished and claustrophobic.

It's funny how Musescore has all these new expensive orchestral sounds, but every time you try to actually write for a large ensemble, it slows down to a crawl when it gets to the part extraction phase - And in this file I'm using MS basic.

I am also having issues converting to music xml. Musescore isn't exporting the instrument changes in the percussion parts properly. Some programs like Dorico refuse to even open it. Finale does, but without the percussion parts (and it's Finale... I'd rather format the score by hand in quill and ink than use it).

I will end this rant here and see if I can replicate this crash in a new project... (more time wasted)

In reply to by lbonocchi

I made a new file with three parts. One of them added after the two first parts were generated.
The new part still didn't conform to my settings. But after hitting "apply to all parts" in styles, it did not crash.

The project that I attached was being worked on since version 4.1. Think that could be the issue?

In reply to by lbonocchi

"as you can see, tuba does not conform to settings."
It's obvious for you, not for someone discovering the piece :)
So, what settings are you referring to exactly?

"The project that I attached was being worked on since version 4.1. Think that could be the issue?"
This may be part of the problem, but at this stage, it's only a guess.

In reply to by cadiz1

open the tuba part and you will see it has no measure numbers, the spacing between measures is way tighter, and it's displaying the instrument name despite being just the tuba in the part. those are the settings (in "style") that aren't conforming when it was created.

In reply to by lbonocchi

FWIW. I opened you Ode and the trumpet part just before the 3 trombone parts. I opened Style and hit "Apply to all parts". It took a while, but no crash. The style properties were applied to the trombone parts.

I kind of wonder why trombone 3+4 ( 2+3) are the same.

It seems like you are creating so many different combinations of parts to meet different situations. Do they all need to be in the same file? Just wondering.

Sibelius was able to open an xml. I didn't really check the percussion parts. But I was able to listen to a little bit of the score. I could hardly stand MuseScore playback. I realize playback isn't what you are after.

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