What are /r/microtonal's favorite Products & Services?

From 3.5 billion Reddit comments

"If we take, e. g. 8 = L, 1 = s, does that mean that in 42-tet there exists a superpyth tuning?"

This would imply that the fifth (3/2) is 25 steps. This is the patent val for 3-limit, but this superpyth scale also implies 7/4 is 34 steps, which is also the patent val, so 42edo tempers out 64/63. It is true as seen when entered 64/63 in https://scratch.mit.edu/projects/413222959/ that 42edo is in the list. When going to superpyth with 5, it implies 5/4 is 13 steps. This is not the patent val of 42edo, so the patent val does not utilize 7-limit superpyth. However the alternative val of 42c (named so because the third prime of 5 (c in the alphabet) is instead mapped to the second nearest step) does have superpyth. Technically it's possible to have a superpyth tuning in any edo, but not necessarily in patent val and not necessarily accurate, and the resulting scales may have negative intervals.

At present, it is the source code for a computer-only (desktop) program. I haven't added automatic builds for Windows/Linux/Mac yet, sorry.

To build the program from the source code you need to install rust-lang and follow these instructions.

I know that this is not as easy as just downloading an executable file but this is an ongoing project and automatic builds weren't on my priority list yet. Maybe I should put them there?

>I think explicility writing functions would be too demanding?

Definitely too demanding. Timed global events, like crescendos, don't need a non-linear curve, as it should be left up the player's interpretation. Though, if we're talking computer synths, there's a lot to handle. There's no way to tell a computer how to do phrase expression besides using global data.

Music trackers are a great source of inspiration for defining how a note works, like Famitracker. Each line is a tuple of data: (note, instrument, volume, fx1, fx2, ...). However, while each fx slot has a defined triple (fx#, op1, op2), there's no guessing what option 1 and option 2 do until a user guide is looked up.

Therefore, a tuple system for human readable notes shouldn't specify data that the person can interpret himself. For example, vibrato could be specified for a computer as (attack time, vibrato speed, vibrato amount), but a person just needs a "do vibrato here".

With Sonic Pi, you can code microtonal music by defining MIDI notes with decimal points in them. For example, 69.50 is 50 cents sharp of the MIDI note A 440. I used this method to play with the Bohlen-Pierce scale on my Mac.

Thank you so much for catching this!!! u/chaintip

The plugin has been updated, would you mind sanity-checking me and letting me know if everything works as expected now? Thanks again!

https://musescore.org/en/project/porcupine-tunings

My version of the plugin has no support for non-standard accidentals. The 31/22-tone plugin implemented a bunch of accidental-related stuff I didn't really follow, but if you're curious you can check out what they did to make it work:

https://musescore.org/en/project/2231-edo-retuning-plugins-suite