Releases: looptailG/musescore-31edo-tuner
Releases · looptailG/musescore-31edo-tuner
31EDO Tuner - v1.5.0
- Added support for custom key signatures.
- Improved error messages.
31EDO Tuner - v1.4.0
- The plugin now keeps track of which microtonal accidental is applied to each note, and will automatically apply the correct tuning offset on the following notes without an explicit accidental within the same measure.
- Added support for the following accidentals:
ARROW_DOWN
LOWER_ONE_SEPTIMAL_COMMA
31EDO Tuner - v1.3.0
- Added support for tuning only the notes within the current selection.
- Renamed the function
getAccidental()
togetAccidentalEdoSteps()
, and used in more places where its functionality was previously implemented. - Reworked the
supportedAccidentals
mapping to use the accidental name as keys. Reworked the functions that interact with it accordingly.
31EDO Tuner - v1.2.1
- Removed the property
TPC
fromsupportedAccidentals
. ReworkedcalculateTuningOffset()
to checkDEFAULT_OFFSET
instead. - Removed the function
positiveModulo()
. Reworked the functiongetNoteLetter()
to not needpositiveModulo()
anymore. - Made the name of the release files consistent with the name of the plugin elsewhere.
v1.2.0
v1.1.0
- Updated the name in the Musescore3 menu to be consistent with the Musescore4 name.
- Reworked the function
getAccidental()
. Now it uses the mappingaccidentalsEdoSteps
, instead of a series of hard coded values. - Improved the handling of exceptions.
- Added a thumbnail image.
v1.0.2
stepSize
andfifthDeviation
are no longer hard coded, but are instead calculated from the definition of a 31EDO step being1200 / 31 ¢
.- Added the function
logMessage()
, which automatically redirects the messages depending on the Musescore version. - Introduced the function
getNoteLetter()
, and reworked the way note names are calculated. - Modified
getAlteration()
, so that it works for both Musescore3 and Musescore4 without having a separate logic for each one.