-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Part names are not synced with instrument names / mixer #16962
Comments
This is tricky to solve because it is often desirable to have parts named differently to instruments (e.g. if the part contains multiple instruments), which means we can't just link the part name to the instrument name all the time. However, we could potentially implement a partial link like this:
|
Otherwise is there a way to change the part name? I couldn’t find it anywhere, it seems that once it is created it’s fixed. |
Great! thanks, I didn't see that. |
I think it is a valid issue, though obviously not as serious as if the name couldn't be changed at all. At some point we will improve instrument naming and numbering to make it even more automatic than it is now, although still just as overridable. We should try to do the same for part names as well. |
If I remember correctly, this was changed by design, when multiple parts bugs were fixed #14288 ? |
I'm not sure. It looks like names of parts were unlinked from instrument names because the automatic logic was causing problems. But maybe we could come up with better logic, or maybe when the user edits an instrument name we could offer to take them to the Parts dialog so that they can check the part names themself. |
Ì only wish that renaming Parts actually would be possible. Currently it works only when you at least have generated all parts once. If you only go into the dialog and rename the parts, save the score and re-open, then it reverts back to the initial name used. Hoping the name sync'ing gets included in the release as it will make my life a lot easier. Currently have to manually rename all instruments in 3 places... |
Is there a reason why we can't do the following? (points 4 and 5, at the very least, which are straight up bugs):
|
@oktophonie, those points all sound good to me!
|
I was directed over to this thread from a question I posted in the online forum - my apologies in advance for the length of this note, and I hope that these thoughts are helpful: From what I can see, there seem to be a couple of different issues with how staff lines and parts are named in MS4.1. The first may be the use of the name "part", which appears at the top of the interface screen to open the "Parts Dialog", and also when right-clicking on a staff line to select "Staff/Part Properties". Because of this, there can be confusion when the word "part" is used - for these comments, I will use "staff line" to refer to a single instrument line that appears in the main conductor score, and "part" to refer to what would be printed for individual players in an orchestra. For clarity, today right-clicking on a "staff line" allows you to open the Staff/Parts Properties window. While there is a clear connection between staff lines and parts, today they are named / modified using two different interfaces. The thread above proposes ways to automatically populate one field when manually changing another, etc., and also points out that there may be circumstances where the instrument name on staff line (in the main score) would be different from the name given to that Part. But this situation is further complicated by the fact that there really can be two different types of "parts" - parts directly associated with a staff line ("Staff Parts"), and parts that manually combine two or more staff lines, such as making a percussion part that includes Bass Drum, Cymbal, and Triangle ("Multi-instrument Parts"). Here's a proposal that may allow this to be managed in a more integrated way: As there is today, let there be a one-to-one relationship between staff lines and staff parts. For every instrument that appears in the main score, a Staff Part is created. But the option to rename the Staff Part would move into a new input field in the Staff/Part Properties dialog (in addition to the long and short instrument names that appear there now). This would allow users to modify all of this information from a single location - when you add an instrument, you can change how the instrument is named on the main score (viewed by the conductor) as well as the part viewed by the individual musician from a single location. In addition, the Staff/Part Properties dialog could add a second new field to modify the name that appears for this staff line in the mixer. I have been unable to find a way to change / override this name today, and adding it here would again consolidate these inputs to a single location. For the Parts Dialog screen, these Single-Instrument Parts would be listed as they are now, but could only be deleted by deleting the instrument from the main score. In addition, it would not be possible to add additional instruments to the Single-Instrument Part - it's always 1:1. Instead of selecting "Rename" for the Part, this option would say "Staff / Part Properties" and would point to the Staff/Properties window discussed just above. The Parts Dialog screen would, however, allow you to create Multi-Instrument parts - parts that include two or more instruments. (There's no need to create single instrument parts, as they are always created when a new instrument is added to the main score.) This could operate very similarly to the current Parts Dialog - create the new part, add two or more instruments, rename, etc. As noted above, the key benefit here is that this scheme allows users to modify all information associated with an instrument (how it is named on the staff line in the conductor's score, how it is named in the mixer, and how it is named in the part) from a single location, while preserving the ability to create and appropriately name multi-instrument parts for distribution. Lastly, I know that work is underway to allow voices in a staff line to be "exploded" into separate staff lines, or for separate staff lines to be "imploded" to a single line - so you could start with separate lines for "Horn 1" and "Horn 2", but then combine to a single line for "Horn 1 & 2" (as often appears in conductor scores). As I am not familiar with the specifics of this work, I can't comment on how this this proposal would work (or need to be modified to work) with that new feature. |
Same problem here. Instrument name, if renamed doesn't match the mixer name. When you attempt to do some mixing with several instruments, that's pretty difficult to do so. 2 possibilities :
Thanks for all work developpers are doing ! |
This doesn't work for me, using It looks like this is a separate bug, reported here: https://musescore.org/en/node/360213
Perhaps the Part and Mixer name not syncing is yet another separate bug? |
As recently discussed in #21839, Mixer names are (completely unrelated to part names and) separate from instrument names. Mixer names are yet another set of names, and currently the UI to edit them is nonexistent. |
Issue type
Other type of issue
Bug description
If you edit the name of an instrument then the part name is not updated to match, and vice versa.
The problem is particularly bad when changing instrument numbers (e.g. renaming "Flute 2" to "Flute 1"). After renaming the instrument, the part will still be called "Flute 2", which is confusing.
Also, if you subsequently add another flute instrument then the newly generated part will also be called "Flute 2", so now you have two parts both called "Flute 2".
This file had some instruments that I deleted and created new ones. The new instrument are numbered in addition to the old (deleted ones), I then changed the name of the instruments to what I need but in exportation MU does not update the changed names.Steps to reproduce
MuseScore Version
4.0.2
Regression
I don't know
Operating system
MacOs 13.2.1
Additional context
Instrument names are displayed inside the:
Part names are displayed inside the:
The text was updated successfully, but these errors were encountered: