'X' in front of notes - can I turn this feature off so it never occurs?

• Jan 25, 2024 - 05:51

I respect the needs of others to occasionally spell C as B#. Also, to notate double-sharps or double-flats. For my purposes, I never want the folks reading my horn charts to see these markings, regardless of their legitimacy. I always begin by writing for trumpet. Then I copy/paste that part into other instrument parts (to be tweaked harmonically). Almost always, when I select a note and 'arrow' it up or down the resulting note will have an X in front of it. Of course, I arrow that note up one half step and then back down to quickly solve the problem. It costs me time - going through this process over and over. Is there a plugin or a preferences change that will kill the above described notations? That would be just great, and make my life so much simpler. Thank you all very much.


Comments

In reply to by george1229

most often, the X does not appear when Pasting. It shows up just after: when 'arrow'ing individual notes up or down to become the desired harmony note. (I change the notes one at time like this so I can hear the chromatic rise/fall and land on desired pitch). Unless I fix the X's right then, on a note by note basis, I'm looking at a score full of what to me are mistakes. So yes, I can hit 'respell pitches' over and over, but am trying to learn a work around. Thanks for your suggestion, George.

In reply to by elsewhere

I would like to learn how to make use of a plugin. Can you help me please?

Your instructions:

"Comment/uncomment the lines thereafter as desired
(a commented line starts with // and does not execute)"

I don't yet know what it means to comment a line. Maybe I can find a tutorial somewhere that will bring me up to speed on how to install plugins?

In reply to by frontdrumpogo

See the manual. Basically: put the .qml file in the Plugins Folder and run. If you specify if you are on MU3 or MU4, and exactly which accidentals you want changed, and to what, I can adapt the code for you. Plugins are javascrtipt-like code. If a line reads:
do this, then on running the plugin it will: do this
If a line reads:
//do this
nothing will happen

In reply to by frontdrumpogo

See the manual. Basically: put the .qml file in the Plugins Folder and run. If you specify if you are on MU3 or MU4, and exactly which accidentals you want changed, and to what, I can adapt the code for you. Plugins are javascrtipt-like code. If a line reads:
do this, then on running the plugin it will: do this
If a line reads:
//do this
nothing will happen
EDIT: Plus you need to do some reading on basic music notation: The x you talk about is the double sharp ##, so that xF is equivalent of G

For your information, an "x" in front of a note means "double sharp". This is quite common in music and it might behoove you to do some research on that type of notation. Also, "bb" means double flat.

In reply to by xavierjazz

Quite common in certain circles.

I am schooled in music/music theory. Many horn players I work with are of an unwashed variety, not schooled at a conservatory, but nonetheless having amazing histories - many hit records, etc. There are a broad array of musician/types all of whom have a need to use Musescore for communicating with players in their given genres, instrument families, etc. be it tablature, or many other styles "I" am not necessarily fluent in.

The point of my original question - how to eliminate double sharps from appearing - comes from one of these fringe (but not 'inferior') sectors of musicianship.

I write charts to serve as pathways, not obstacle courses. I design them for fellow section mates to run on - often times in front of large audiences. Anything I can do to clear sticks and debris from the path will result in a safer run and clam-free players. Using this metaphor, feeding them double sharps, E#'s or Cbb's would be like installing tree roots and pits in the path.

If I'm being defensive, it wasn't my original intent. The tone of 'behoove you to do some research' is just sort of .... oh well. Good luck, and thanks for any helpful tips.

Please don't tell me you are copying a trumpet part into another instrument and then moving each note up or down to create harmony.

I think the only way you can turn off double accidentals is when you transpose a section.

In reply to by bobjp

I'm afraid its true..Please suggest a better way to go about this, as it sounds like you're less than thrilled by my (self taught) approach.

I most commonly write for Trumpet, Tenor, Bari and bone.

Being a trumpet player, I write the trumpet part first. Then I copy it and paste, for example, into the tenor sax part. Next, I 'select all', then raise the tenor's notes a full octave, correcting for the tenor sax's range. At this point, the trumpet and tenor are playing in unison. Very fast for me to get to this point, rather than writing a tenor part from scratch.

Unless the phrase I'm working on is to be a unison one, I then raise or lower each note..(one at a time - so I can hear the virtual instrument playing)..to it's desired pitch.

How would you suggest I go about this differently?

Pogo Joe

In reply to by frontdrumpogo

If you mostly move note up, consider transposing not just an octave but maybe less or more. Then move notes as needed. If most of your harmonies are lower (like maybe a third) Transpose by interval, some kind of sixth.
Although if you are moving every note anyway, what is an extra two clicks to get rid of the double sharp?
I didn't mean to criticize your method. Really. We all have to work the way that works for us.

> Almost always, when I select a note and 'arrow' it up or down the resulting note will have an X in front of it

Could you please provide the steps do this? I recall that is the exact feature some other forum user requested long ago, because arrow keys in ms3 refuse to create notes with accidentals other than sharp and flat.

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