User:Godtone - Revision history

Godtone: /* zeta and optimal_edo_sequence */ more data

2026-06-22T20:36:20Z

zeta and optimal_edo_sequence: more data

← Older revision		Revision as of 20:36, 22 June 2026
Line 9:		Line 9:
	* [[User:Godtone/zeta]]		* [[User:Godtone/zeta]]
	Whose significance is backed up by the more psychoacoustically-informed tuning metrics I've designed (<code>optimal_edo_sequence</code>s from [[#My Python 3 code]]):		Whose significance is backed up by the more psychoacoustically-informed tuning metrics I've designed (<code>optimal_edo_sequence</code>s from [[#My Python 3 code]]):
	* [[User:Godtone/optimal edo sequences]]		* [[User:Godtone/optimal edo sequences]] (and [[User:Godtone/strict_optimal_edo_sequences]])
	...as well as by my own knowledge of tuning theory.		...as well as by my own knowledge of tuning theory.

Godtone: /* My Python 3 code */ clarification

2026-06-21T02:40:32Z

My Python 3 code: clarification

← Older revision		Revision as of 02:40, 21 June 2026
Line 466:		Line 466:

	== My Python 3 code ==		== My Python 3 code ==
	IMPORTANT NOTE: there seems to be ~~a bug~~ for subgroup mappings at the moment, pending investigation, but ideally usage of subgroups should be made far easier too:		IMPORTANT NOTE: there seems to be bugs for subgroup mappings at the moment, pending investigation, but ideally usage of subgroups should be made far easier too:
	<syntaxhighlight lang="python">		<syntaxhighlight lang="python">
	>>> sg = [2, 3, 7, 11, 13, 17, 19]		>>> sg = [2, 3, 7, 11, 13, 17, 19]

Godtone: /* My Python 3 code */ explain the mediant_complexity

2026-06-20T18:03:44Z

My Python 3 code: explain the mediant_complexity

← Older revision		Revision as of 18:03, 20 June 2026
Line 1,518:		Line 1,518:
	return result		return result

			# the length of the mediant path of whichever octave-revoicing gives the interval x the least length
	def mediant_complexity(x,revoicing_octs=7):		def mediant_complexity(x,revoicing_octs=7):
	mincomplexity = 2**30		mincomplexity = 2**30

Godtone: /* My Python 3 code */ there is only finitely many EDOs which provide some simplification of a set of intervals as contrasted to all-distinct

2026-06-20T17:07:49Z

My Python 3 code: there is only finitely many EDOs which provide some simplification of a set of intervals as contrasted to all-distinct

@@ Line 1,550: / Line 1,550: @@
 		print()
 	return spaces
 </syntaxhighlight>

Godtone: /* Novation Launchpad Pro MK3 isomorphic keyboard code */ move error

2026-05-28T19:19:10Z

Novation Launchpad Pro MK3 isomorphic keyboard code: move error

← Older revision		Revision as of 19:19, 28 May 2026
Line 1,622:		Line 1,622:

	'''It should be compatible with any Launchpad that has [[#Putting the Launchpad in programmer mode\|programmer mode]]; it has been confirmed to work for the Launchpad X so will likely also work for a Launchpad Mini MK3.'''		'''It should be compatible with any Launchpad that has [[#Putting the Launchpad in programmer mode\|programmer mode]]; it has been confirmed to work for the Launchpad X so will likely also work for a Launchpad Mini MK3.'''

	~~'''A strange error has been found: Python 3.14 and later versions have deprecated a functionality used, so downgrading to Python 3.12 may be required if nothing here works.'''~~

	ALSO: This should go without saying but take care of your launchpad! If you wipe it don't expect it to be properly responsive until fully dry and even then wiping it can have risks if the liquid goes inside. Similarly, do not bang it and probably don't leave it upside down (especially if for long periods of time) in case it causes the velocity sensitivity to go weird. Treat it as an instrument. If you do all this, it should be fine to use it for its intended purpose: just don't press ''too'' hard; try not press with more velocity than the buttons actually require, if possible. (Because of my silliness (not heeding such obvious procedures) there is a possibility that I may have weared my launchpad slightly in that I think I now require more pressure for the pressure-sensitive pads. I thought it responsible to add this note about taking care of your launchpad, as we are technically using it in a nonstandard way by treating the buttons as though they were just insensitive pads that require extra velocity/pressure.)		ALSO: This should go without saying but take care of your launchpad! If you wipe it don't expect it to be properly responsive until fully dry and even then wiping it can have risks if the liquid goes inside. Similarly, do not bang it and probably don't leave it upside down (especially if for long periods of time) in case it causes the velocity sensitivity to go weird. Treat it as an instrument. If you do all this, it should be fine to use it for its intended purpose: just don't press ''too'' hard; try not press with more velocity than the buttons actually require, if possible. (Because of my silliness (not heeding such obvious procedures) there is a possibility that I may have weared my launchpad slightly in that I think I now require more pressure for the pressure-sensitive pads. I thought it responsible to add this note about taking care of your launchpad, as we are technically using it in a nonstandard way by treating the buttons as though they were just insensitive pads that require extra velocity/pressure.)
Line 1,631:		Line 1,629:
	=== Installation issues/troubleshooting strategies/recommendations ===		=== Installation issues/troubleshooting strategies/recommendations ===
	The most potentially difficult part is that depending on what OS you are using, how you have Python installed, what version, etc. there can be complications so that running <code>pip install rtmidi</code> and <code>pip install mido</code> in a terminal does not work, or only appears to work so that there's issues when the code tries to use mido. I list potential issues below, so please read carefully for something applicable to your case if it isn't going smoothly.		The most potentially difficult part is that depending on what OS you are using, how you have Python installed, what version, etc. there can be complications so that running <code>pip install rtmidi</code> and <code>pip install mido</code> in a terminal does not work, or only appears to work so that there's issues when the code tries to use mido. I list potential issues below, so please read carefully for something applicable to your case if it isn't going smoothly.

			'''IMPORTANT: A strange error has been found: Python 3.14 and later versions have removed a functionality used by mido internally, so downgrading to Python 3.12 is required if nothing here works.'''

	'''IMPORTANT:''' Before deeming an installation of mido/rtmidi to "not be working", make sure that the issue is not just one of what MIDI ports are being autoselected; see (6.) onwards for details.		'''IMPORTANT:''' Before deeming an installation of mido/rtmidi to "not be working", make sure that the issue is not just one of what MIDI ports are being autoselected; see (6.) onwards for details.

Godtone: /* Novation Launchpad Pro MK3 isomorphic keyboard code */ catalogue inconsistency error that may occur

2026-05-28T19:17:29Z

Novation Launchpad Pro MK3 isomorphic keyboard code: catalogue inconsistency error that may occur

← Older revision		Revision as of 19:17, 28 May 2026
Line 1,622:		Line 1,622:

	'''It should be compatible with any Launchpad that has [[#Putting the Launchpad in programmer mode\|programmer mode]]; it has been confirmed to work for the Launchpad X so will likely also work for a Launchpad Mini MK3.'''		'''It should be compatible with any Launchpad that has [[#Putting the Launchpad in programmer mode\|programmer mode]]; it has been confirmed to work for the Launchpad X so will likely also work for a Launchpad Mini MK3.'''

			'''A strange error has been found: Python 3.14 and later versions have deprecated a functionality used, so downgrading to Python 3.12 may be required if nothing here works.'''

	ALSO: This should go without saying but take care of your launchpad! If you wipe it don't expect it to be properly responsive until fully dry and even then wiping it can have risks if the liquid goes inside. Similarly, do not bang it and probably don't leave it upside down (especially if for long periods of time) in case it causes the velocity sensitivity to go weird. Treat it as an instrument. If you do all this, it should be fine to use it for its intended purpose: just don't press ''too'' hard; try not press with more velocity than the buttons actually require, if possible. (Because of my silliness (not heeding such obvious procedures) there is a possibility that I may have weared my launchpad slightly in that I think I now require more pressure for the pressure-sensitive pads. I thought it responsible to add this note about taking care of your launchpad, as we are technically using it in a nonstandard way by treating the buttons as though they were just insensitive pads that require extra velocity/pressure.)		ALSO: This should go without saying but take care of your launchpad! If you wipe it don't expect it to be properly responsive until fully dry and even then wiping it can have risks if the liquid goes inside. Similarly, do not bang it and probably don't leave it upside down (especially if for long periods of time) in case it causes the velocity sensitivity to go weird. Treat it as an instrument. If you do all this, it should be fine to use it for its intended purpose: just don't press ''too'' hard; try not press with more velocity than the buttons actually require, if possible. (Because of my silliness (not heeding such obvious procedures) there is a possibility that I may have weared my launchpad slightly in that I think I now require more pressure for the pressure-sensitive pads. I thought it responsible to add this note about taking care of your launchpad, as we are technically using it in a nonstandard way by treating the buttons as though they were just insensitive pads that require extra velocity/pressure.)

Godtone: unfinished sentence

2026-05-01T14:01:51Z

unfinished sentence

← Older revision		Revision as of 14:01, 1 May 2026
Line 105:		Line 105:
	* 31: The next EDO that melodically approximates the 11-limit, and considerably better. Extremely nice arrangement of intervals that feels weirdly intuitive and ideal. Colourful EDO. Basically ideal meantone tuning as more notes than this is overkill for meantone if you don't specifically want meantone.		* 31: The next EDO that melodically approximates the 11-limit, and considerably better. Extremely nice arrangement of intervals that feels weirdly intuitive and ideal. Colourful EDO. Basically ideal meantone tuning as more notes than this is overkill for meantone if you don't specifically want meantone.
	* 32: 16 EDO with a sharp fifth. I like it primarily because of it being a power of 2. Exploration into this EDO could be interesting. 80 EDO offers a reasonably good approximation of it through a 16L16s MOSS.		* 32: 16 EDO with a sharp fifth. I like it primarily because of it being a power of 2. Exploration into this EDO could be interesting. 80 EDO offers a reasonably good approximation of it through a 16L16s MOSS.
	* 34: The first good approximation of the 5-prime-limit due to being the first reasonably accurate tuning of [[Kleismic family\|kleismic]] and [[srutal archagall]] which are IMO the best 5-limit temperaments that observe the [[81/80\|syntonic comma]]. 19 is also a tuning for kleismic but feels like it doesn't do justice to the accuracy and pristineness of kleismic to me, plus its harmonic interpretation is pretty lacking. And 22 is very obviously to Has the sharp 3/2's of 17 EDO, and as 17 EDO is a good colour system, 34 EDO is a natural extension. Also is a very logical "completion" of 17 due to giving a very logical 2.3.5.13.17(.23)-subgroup interpretation of the sqrt(2).sqrt(3) subgroup with some really intriguing possibilities. If you're lacking in inspiration and its wide array of supported MOSSes aren't inspiration enough, try taking a look at the diaschismic-tetracot continuum ([[2048/2025]])<sup>n</sup> / ([[20000/19683]]).		* 34: The first good approximation of the 5-prime-limit due to being the first reasonably accurate tuning of [[Kleismic family\|kleismic]] and [[srutal archagall]] which are IMO the best 5-limit temperaments that observe the [[81/80\|syntonic comma]]. 19 is also a tuning for kleismic but feels like it doesn't do justice to the accuracy and pristineness of kleismic to me, plus its harmonic interpretation is pretty lacking. And 22 is very obviously too high-damage for srutal archagall. Has the sharp 3/2's of 17 EDO, and as 17 EDO is a good colour system, 34 EDO is a natural extension. Also is a very logical "completion" of 17 due to giving a very logical 2.3.5.13.17(.23)-subgroup interpretation of the sqrt(2).sqrt(3) subgroup with some really intriguing possibilities. If you're lacking in inspiration and its wide array of supported MOSSes aren't inspiration enough, try taking a look at the diaschismic-tetracot continuum ([[2048/2025]])<sup>n</sup> / ([[20000/19683]]).
	* 35: A subset of 140 EDO, a ridiculously strong generalist system, which endows it with magical tuning qualities.		* 35: A subset of 140 EDO, a ridiculously strong generalist system, which endows it with magical tuning qualities.
	* 36: Because of being a superset of 12, quite overlooked. It is actually a very good subgroup temperament! A natural extension of 12 EDO's colour palette, preferring to avoid the neutral and semi- intervals of 24 EDO. I should note though that while both 24 and 36 are reasonably good systems, I do not think they should be used together, as there are preferable EDOs in the high end range, such as 80 EDO.		* 36: Because of being a superset of 12, quite overlooked. It is actually a very good subgroup temperament! A natural extension of 12 EDO's colour palette, preferring to avoid the neutral and semi- intervals of 24 EDO. I should note though that while both 24 and 36 are reasonably good systems, I do not think they should be used together, as there are preferable EDOs in the high end range, such as 80 EDO.

Godtone: /* My Python 3 code */ fix again... defaulting an argument in Python 3 apparently works to do the equivalent of capturing a variable

2026-03-02T17:23:02Z

My Python 3 code: fix again... defaulting an argument in Python 3 apparently works to do the equivalent of capturing a variable

← Older revision		Revision as of 17:23, 2 March 2026
Line 1,356:		Line 1,356:
	weighting = -0.5 # as we may square after when doing a MSE, we use the square root		weighting = -0.5 # as we may square after when doing a MSE, we use the square root
	if type(weighting) in [int,float]:		if type(weighting) in [int,float]:
	weighting = lambda x: iv_complexity(x)**~~weighting~~		weighting = lambda x,w=weighting: iv_complexity(x)**w
	global ivs_cache		global ivs_cache
	global ivs_int_cache		global ivs_int_cache

Godtone: missing punctuation lol

2026-03-01T18:59:22Z

missing punctuation lol

← Older revision		Revision as of 18:59, 1 March 2026
Line 1,349:		Line 1,349:
	if weighting in [None,'none','unweighted','trivial','basic','constant']:		if weighting in [None,'none','unweighted','trivial','basic','constant']:
	weighting = 0		weighting = 0
	elif weighting in ['','default','proportional']		elif weighting in ['','default','proportional']:
	weighting = 1		weighting = 1
	elif weighting in ['sensitive','dyadic']:		elif weighting in ['sensitive','dyadic']:

Godtone: helper function i wrote for finding useful commas in sets of intervals

2026-02-24T20:06:36Z

helper function i wrote for finding useful commas in sets of intervals

@@ Line 1,524: / Line 1,524: @@
 		mincomplexity = min(mincomplexity,len(mediant_path( mul_iv(x,(2**octs,1)) )))
 	return mincomplexity
 </syntaxhighlight>