Create add/show implied accidentals within measure
I am requesting someone capable of creating a plugin for Musescore with one simple function: showing implied/hidden accidentals that carry through a single measure. No parameters, perhaps not even a window, simply run the plugin and accidentals assumed within a measure are added to recurring notes so that there are redundant accidentals (an accidental is carried for an entire measure, I want these carried accidentals to be added). An G# followed by three more G notes in the measure, played as G#'s, would also be written with 3 additional # symbols.
I have 400 routines in a book I have completed for saxophone but I will have to manually add these accidentals without the plugin/function. There are over 40k notes so this function would save me tons of time and eliminate errors. Please respond to roostarrmuzic@gmail.com if you are willing to create the plugin. Thank you!!!
In both summary and example, Please create a plugin with one simple function, when the plugin is enabled, an F# at the beginning of the measure also appears on another F note in the measure even though it is normally implied and unmarked.
Thank you so much!!!
Andrew Beal
Comments
What about the Configure Courtesy Accidentals plugin from https://musescore.org/en/project/courtesyaccidentals, selecting the "all notes (dodecaphonic style)" option?
In reply to What about the Configure by Isaac Weiss
Unfortunately this option marks every natural as well. I don't want every single note to have an accidental inclluding sharps, I want repeat accidentals within the measure to have an accidental. Good suggestion, but it does not worked. I have already tried this.
In reply to Unfortunately this option by Andrew Beal
I have to say, that's a rather strange need, and if you want if for the reason I think you want it, I would like to dissuade you from it. A student using your saxophone book would become accustomed to reading music like that, and could have a serious struggle the next month reading normal music—playing four F#s as one F# and three FNs. I've never seen even the most beginning book try to avoid the conventions for notating accidentals.
But, at any rate, perhaps a plugin developer will provide what you asked for.
In reply to I have to say, that's a by Isaac Weiss
This convention is occasionally used in extremely complex atonal music. A plugin to do this automatically isn't a bad idea IMHO. Or, if we ever do implement a built in courtesy accidentals facility, it could even be incorporated into that.
In reply to This convention is by Marc Sabatella
Thank you, and the music is definitely for advanced players. It is an complete documentation of every interval pair in every cycle, ascending and descending, written for saxophone (but any musician could use it, save notes out of the instruments written range)
I might be able to give it a try later this week. But first I'd need at least one more detail: In case a sharp is canceled later in the same measure would you also want the natural sign to be repeated in that same measure? Example: G# G# Gnat Gnat, all in the same measure.
The first G# gets a necessary accidental. You'd want the second G# to have one as well. The following first Gnat of course gets a needed accidental. Now: would you want the natural sign repeated for the following Gnat? Or should only accidentals differing from the current key signature be repeated?
In reply to I might be able to give it a by heuchi
I work 12 hour days construction, sorry for the delayed reply. Bad wifi at my hotel.
In reply to I might be able to give it a by heuchi
To answer your question, the naturals would not be necessary. A second natural in the same measure would would be instinctively read as a natural. #'s and b's however would not be easy to remember as in many cases, they occur after 2-3 key changes and come as a surprise during large pairs of intervals that are not diatonic (in the key). (Key signatures are not written only implied by the notes)
The entire book is written in eighth notes and rhythms are to be manually applied to the melodic lines which can change key as often as every 2 notes, hence there are no key signatures. Every thing is in "C" but the cycle implies the keys. 5ths cover 12 keys, one cycle. Major thirds cover 3 keys, 4 cycles, etc. It is for advanced players who know all 12 keys by heart and it is designed to be read through for exercise, and memorized for practical application, and extracted from for phrase developnment.
It is for complex mathematical lines, not atonal, but based on interval cycles (like the circle of keys). Do you play sax? It works for all instruments, but it is written in the range of the saxophone. I could send you a copy when it is complete (I am only editing now, I have a printed copy of the rough edit already,
THANK YOU SO VERY MUCH!!! I would be happy to return the favor in some way if possible.
I just realized (once more), that a plugin currently has no access to the current key signature. So the plugin I wrote is probably of very limited use and very specific to your case. That's why I'll only attach it here and not open a new project page.
I don't need to tell you, that it may contain bugs. So make sure you don't loose any data when using it.
If you find problems, report them in this thread. I do of course hope, that it works well, and that I completely understood what you need it to do... ;-)
In reply to I just realized (once more), by heuchi
Heuchi, I am extatic!!!!! It works and it works INSTANTLY. It is so awesome. I can open each of my files and run the plugin for perfect result without having to check every page, every note! I would like to hire you for your going rate in the future to create a complex and more univerally desirable plugin. I believe you could sell it to a wide audience of composers as it assists with generating compositions lightning fast. I have the concept already worked out and we should discuss it and your thoughts, terms, and opinion of the plugin/possible standalone program. Thank you!!
I hope that sharing my concept with you will benefit you, excite you, and perhaps bring you more reward for your hard work than just my gratitude. THANK YOU THANK YOU!!!
You deserve more than this so lets speak here in the near future. I will message you directly as soon as I am able. I will be free AMerican time PST Sunday afternoon, but I can wait for your reply.
Andrew Beal
In reply to Heuchi, I am extatic!!!!! It by Andrew Beal
Dear Andrew,
you're most welcome. I'm really glad the plugin works for you. Since I already
have created some plugins dealing with accidentals, it actually wasn't so much
work to get this one done. I just copied some of the code I already had and
did some investigation about key signature changes (as stated above), because
I wanted the plugin to be more flexible than it currently is.
I've been using free open-source software for quite some time now and
MuseScore has already helped me a lot. Therefore I'm very happy to be able to
give something back to the community, that made it possible for such a
great piece of open-source software to exist.
While I'm really excited some of the code I wrote made its way into MuseScore
and some people like the plugins I wrote, I must say that my time is limited
and that I cannot take the responsibility to develop, document, maintain and
support a piece of software in a commercial setup.
Heuchi