musescore-n-tet-plugins:Musescore插件可在任何EDO中重调音符

# n-EDO Retuner plugin for Musescore 3.4+ Musescore plugin to retune and pitch up/down notes in any EDO ranked from flat-2 to sharp-8. (Supports all EDOs from 5-72 except 59, 66, and 71. Also supports larger edos up to 117 that are rated with a [sharpness](#tuning-of-regular-pythagorean-accidentals) of up to sharp-8) [Here is the full list of supported EDOs and their respective sharpness values.](#appendix-a-list-of-supported-edos-according-to-sharpness-classification)  ## Features - Retuning note cent offsets to match any supported edo of choice - Special thanks to [Flora Canou](https://github.com/FloraCanou/musescore-n-tet-plugins) for providing the generalized method for evaluating cent offsets for any EDO. - Support for key signatures via [Key signature annotations](#key-signatures) - Transposing individual notes / selections by 1 EDO step, managing neutralization and correction of accidentals on following notes. - Tuning system, key signatures, and reference pitches can be changed mid score, and staves may be set to different tunings, key signatures, and reference pitches at the same time. ## Instructions **Make sure you are using MuseScore 3.4 or newer. The plugin will not work in previous versions** [Download the project](https://github.com/euwbah/musescore-n-tet-plugins/archive/master.zip) and unzip into MuseScore's plugins directory. [Install & Activate](https://musescore.org/en/handbook/plugins#windows) the following plugins: - `tune n-edo.qml`: - Tunes selected phrase (selection made with shift-click) / whole score (if nothing selected) - `pitch up.qml` & `pitch down.qml`: - Transposes up/down selected phrase (shift-click) / individually selected notes (alt-click noteheads). - `pitch up no dt.qml` & `pitch down no dt.qml`: - Same as above, but prioritizes up/down arrows over semi/sesqui sharp/flat symbols wherever possible. - Set up keyboard shortcuts for the plugins (optional, you can still access them in the plugin drop-down menu): - Go to Plugins -> Plugin Manager -> select plugin -> Define Shortcut - For Tuning, it is recommended to use Alt+R (for "Retune") - For Pitch up/down, we recommend up/down arrow keys - This plugin is built to work in place of the default up/down arrow key shortcuts in MuseScore (including repositioning other elements) - Before assigning the up/down arrow keys shortcut, you will have to clear or change the following shortcuts in the Shortcuts preferences menu (Edit -> Preferences -> Shortcuts) - _Pitch up or move text or articulation up_ (consider replacing with Alt+PgUp) - _Pitch down or move text or articulation down_ (consider replacing with Alt+PgDn) - _Select string above (TAB only)_ (suggest replacing with Alt+Up, which matches moving to next note above in staff) - _Select string below (TAB only)_ (suggest replacing with Alt+Down, which matches moving to next note below in staff) - Ensure only one variant of each plugin has the keyboard shortcut assigned at a time.\ If 'pitch up.qml' is assigned to the up arrow, then 'pitch up no dt.qml' cannot be assigned to the up arrow.\ Both plugins may be enabled simultaneously, but they must be assigned different keyboard shortcuts. ### Selecting the tuning system The plugin makes use of staff text annotations (Ctrl-T) and system text annotations (Ctrl-Shift-T) to configure which tuning system is used. Using staff text will apply the tuning system to only the staff that it is on, and using system text will apply the tuning system to the all the staves. Staff/system text will only affect the current and subsequent bars of music, but not the bars before, thus, it is possible to change the tuning system mid-piece, and have different instruments in different tuning systems concurrently. It is possible, but not recommended, to change the tuning system halfway through a bar, as accidentals may carry over and be applied in unexpected ways. There are 3 types of tuning system annotations that the plugin accepts, and each one has to be in its own separate staff/system text: - **EDO selector** format: `x edo` (e.g. `31 edo`) - Where `x` is the number of equally-spaced notes in the octave. - Spaces and capitalization are optional. Non-integer edos are not currently supported. - When the EDO is changed, any prior key signature must be redeclared as the step offsets of the key signatures would differ and has to be updated. - **Reference frequency selector** format: `x: y hz` (e.g. `a4: 440 hz`) - Where `x` is the pitch nominal such as `a4`, `y` is its frequency. Other notes will be tuned to that as reference. - Spaces and capitalization are optional. Decimals in frequency are supported. - **Key signature** format: `.x.x.x.x.x.x.x` (e.g. `.b.b.b.b.b.b.bb` is F-flat major in 12/19/31/50 edo) - Where each `x` represents the [textual representation of the accidentals](#key-signatures) applied on the notes C, D, E, F, G, A, and B in that order. - If a particular note is natural, leave the space after the dot empty or use any placeholder like '0' or 'n', but keep the dot there.\ In total, there should be 7 dots. - Key signature text must be denoted on **all** key signatures present in the score, whether custom, microtonal, or standard.\ If there are no key signatures for the score, there is no need to enter key signature text, but you can still enter a blank key signature text for future reference (e.g.: `.......` is a blank key signature) - Likewise, all key signature annotation texts **must** have a corresponding key signature element placed in that measure, especially if there are standard accidentals (bb/b/#/x) in the key signature. ## Notation system The plugin follows notation standards as per [NOTATION GUIDE FOR EDOS 5-72](http://tallkite.com/misc_files/notation%20guide%20for%20edos%205-72.pdf), which is a generalized system for notating any EDO. Here is a brief summary of the contents of the document: ### Tuning of nominals C D E F G A B In this system, the nominals F C G D A E B are tuned according to a chain of **best fifths**, which is the best representation of the perfect 3:2 just fifth that the EDO has to offer.\ The exact pitches of the notes are calculated based on the frequency of the reference note, which is defined by the reference frequency selector, or A4: 440 Hz by default. <details> <summary><em> How to calculate an EDO's best fifth? </em></summary> The number of steps a fifth is in x-edo = `round(x * log2(3/2))` `3/2` represents the frequency ratio of a fifth in just intonation.\ `log2(3/2)` represents how many octaves are there in a fifth (approx 0.584962)\ `x * log2(3/2)` represents how many steps of x-edo are there in a fifth\ `round()` rounds it up/down to the nearest whole edostep. </details> The best fifth in 12 edo is 7 steps. Thus, the distance between F-C, C-G, G-D, etc.. is 7 steps of 12 edo. The best fifth in 22 edo is 13 steps. Thus, the distance between C-G, etc.. is 13 steps of 22 edo. ### Tuning of regular pythagorean accidentals     The standard accidentals Double Flat (`bb`), Flat (`b`), Sharp (`#`), Double Sharp (`x`) are based on the circle of fifths. To give an example in 12-edo, going 7 fifths up from C4 yields C4-G4-D5-A5-E6-B6-F#7-C#8.\ A best fifth in 12-edo is 7 steps of 12 edo.\ Going up 7 fifths in 12-edo yields a total of 7*7 = 49 steps (which brings C4 to C#8)\ Going down 4 octaves to bring C#8 down to C#4 reduces the steps by 4 * 12 = 48 steps.\ Thus, a sharp symbol in 12-edo is defined as going up 49 steps, then down 48 steps, yielding a +1 step difference. The number of edosteps a sharp symbol raises the pitch by is known as an EDO's **sharpness** value, also known as the size of the **apotome**.\ Thus, the sharpness of 12-edo is 1, which classifies it as a **shar