Lucius Chiaraviglio
Joined 12 February 2024
→Editing Tips: Convert ampersand into HTML form to avoid errors in future history display; add a bit more explanation |
Looks like backslashes do weird things in certain places if not converted to HTML form — intermediate save to see if this worked right |
||
| Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
Although I have yet to compose anything, I have on occasion thought that "notes between the notes" (to borrow a term from | Although I have yet to compose anything, I have on occasion thought that "notes between the notes" (to borrow a term from ''Hear Between the Lines'') would be fitting in certain circumstances. Several months ago, I stumbled upon the great radiation of microtonal music that is occurring on YouTube thanks to the advent of (semi-)affordable microtonal keyboards and software synthesizers that actually sound good. Surprisingly, the recent microtonal profusion seems to have a great overlap with a profusion of new classical music. In addition, I have found interest in old music that would now be thought of as xenharmonic, such as early Baroque works in quarter-comma meantone. And even if I never compose any microtonal music myself, this experience, including readings on this Xenharmonic Wiki, have been a wild ride in learning what it is that makes today's dominant system of 12 equally spaced notes per octave actually work well. | ||
Added: [[User:Lucius Chiaraviglio|Lucius Chiaraviglio]] ([[User talk:Lucius Chiaraviglio|talk]]) 10:14, 12 February 2024 (UTC) | Added: [[User:Lucius Chiaraviglio|Lucius Chiaraviglio]] ([[User talk:Lucius Chiaraviglio|talk]]) 10:14, 12 February 2024 (UTC) | ||
| Line 17: | Line 17: | ||
The case for [[23edo and octave stretching]] was more complicated, because the ratios were expressed with colons instead of slashes, and I needed to change them to slashes. This required the following "sed" command using capture groups (which Google's AI actually did a decent job of explaining how to use when I didn't know the name and was trying to look up "divided regular expression"): | The case for [[23edo and octave stretching]] was more complicated, because the ratios were expressed with colons instead of slashes, and I needed to change them to slashes. This required the following "sed" command using capture groups (which Google's AI actually did a decent job of explaining how to use when I didn't know the name and was trying to look up "divided regular expression"): | ||
<code>sed -E "s#([0-9]+):([0-9]+)#\[\[ | <code>sed -E "s#([0-9]+):([0-9]+)#\[\[\1/\2\]\]#g" 23EDOintervals.txt > 23EDOintervals.new.txt</code> | ||
The parentheses delimit the input capture groups (and note that the "+" needs to be inside each capture group or it won't work right, and if you need to look for literal parentheses you have to escape them with backslashes, same as with the square brackets), and the | The parentheses delimit the input capture groups (and note that the "+" needs to be inside each capture group or it won't work right, and if you need to look for literal parentheses you have to escape them with backslashes, same as with the square brackets), and the \1 and \2 indicate the output capture groups, which also gives you the option to reverse them (for instance, if the table contained the ratios inverted, which was not the case in this particular example, but is somewhat common elsewhere). Note that the capture groups replace the overall regular expression (which was represented by an ampersand in the first version of the command). | ||
Added: [[User:Lucius Chiaraviglio|Lucius Chiaraviglio]] ([[User talk:Lucius Chiaraviglio|talk]]) 07:20, 29 October 2025 (UTC)<br> | Added: [[User:Lucius Chiaraviglio|Lucius Chiaraviglio]] ([[User talk:Lucius Chiaraviglio|talk]]) 07:20, 29 October 2025 (UTC)<br> | ||