User talk:Aura: Difference between revisions

Line 267:

::: It maybe true that these discrepancies won't be noticed by listeners, but the fact that I'm the one doing the tuning and cent-size look ups for various intervals means that I would feel as if I were being somewhat disingenuous to the more strict analysts who use computers for their analysis if I didn't add that disclaimer. I hope this makes some degree of sense. --[[User:Aura|Aura]] ([[User talk:Aura|talk]]) 03:17, 19 February 2021 (UTC)

== MuseScore 159edo retuning plugin... ==

Hey Aura, I’ve been thinking about how a 159edo retuning plugin for MuseScore could be made, so I want to explain the main issue and offer 3 potential solutions. This block of text comes directly from the n-tet retuning plugin README. “A maximum of 3 arrows are allowed on each accidental, as MuseScore currently does not provide accidentals with more than 3 arrows. Due to these limitations, and with the help of quartertone accidentals, the plugin can only handle EDOs with a sharpness rating of up to 8.” The main problem here is that 159edo has a sharpness rating of 15 (one sharp equals 15 steps), meaning that there would have to be support for septuple up and septuple down accidentals in MuseScore for each note in 159edo to be accessible. (Assuming usage of ups and downs notation without lifts and drops). Here are my three solutions. The first solution is to come up with a notation system for 159edo using accidentals that can be found in MuseScore’s advanced palate. Then, a fork of euwbah’s n-tet retuning plugin would have to be made which could map all of the accidentals to edostep offsets. (Sharp equals 15 steps, triple up natural equals 3 steps, etc) The second solution is to use ups and downs notation from 53edo combined with “+” and “-“ symbols to indicate 1 step offsets for 159edo. For this to be effective, the plugins which raise and lower a note by one edostep (these plugins are included with the n-tet retuning plugin) would have to be modified to add and remove the “+” and “-“ symbols as necessary as well as changing the accidental and the pitch offset. The third solution is to use polychromatic notation for 53edo and to use the up and down arrow accidentals to access the notes in 159edo. Again, the pitch up and pitch down plugins would have to be modified. This time, these plugins would have to change the note head color as well as changing the accidental and the pitch offset. I would like to know which option you think is best for making 159edo compositions in MuseScore. In addition, since the programming language for MuseScore (Qt) is a bit too confusing for me to make anything meaningful in, you’ll have to ask FloraC to do the actual coding. I might be able to help a little bit, but not much.

@@ Line 267: / Line 267: @@
 ::: It maybe true that these discrepancies won't be noticed by listeners, but the fact that I'm the one doing the tuning and cent-size look ups for various intervals means that I would feel as if I were being somewhat disingenuous to the more strict analysts who use computers for their analysis if I didn't add that disclaimer.  I hope this makes some degree of sense. --[[User:Aura|Aura]] ([[User talk:Aura|talk]]) 03:17, 19 February 2021 (UTC)
+== MuseScore 159edo retuning plugin... ==
+Hey Aura, I’ve been thinking about how a 159edo retuning plugin for MuseScore could be made, so I want to explain the main issue and offer 3 potential solutions. This block of text comes directly from the n-tet retuning plugin README. “A maximum of 3 arrows are allowed on each accidental, as MuseScore currently does not provide accidentals with more than 3 arrows. Due to these limitations, and with the help of quartertone accidentals, the plugin can only handle EDOs with a sharpness rating of up to 8.” The main problem here is that 159edo has a sharpness rating of 15 (one sharp equals 15 steps), meaning that there would have to be support for septuple up and septuple down accidentals in MuseScore for each note in 159edo to be accessible. (Assuming usage of ups and downs notation without lifts and drops). Here are my three solutions. The first solution is to come up with a notation system for 159edo using accidentals that can be found in MuseScore’s advanced palate. Then, a fork of euwbah’s n-tet retuning plugin would have to be made which could map all of the accidentals to edostep offsets. (Sharp equals 15 steps, triple up natural equals 3 steps, etc) The second solution is to use ups and downs notation from 53edo combined with “+” and “-“ symbols to indicate 1 step offsets for 159edo. For this to be effective, the plugins which raise and lower a note by one edostep (these plugins are included with the n-tet retuning plugin) would have to be modified to add and remove the “+” and “-“ symbols as necessary as well as changing the accidental and the pitch offset. The third solution is to use polychromatic notation for 53edo and to use the up and down arrow accidentals to access the notes in 159edo. Again, the pitch up and pitch down plugins would have to be modified. This time, these plugins would have to change the note head color as well as changing the accidental and the pitch offset. I would like to know which option you think is best for making 159edo compositions in MuseScore. In addition, since the programming language for MuseScore (Qt) is a bit too confusing for me to make anything meaningful in, you’ll have to ask FloraC to do the actual coding. I might be able to help a little bit, but not much.