I could really use a little app (or something) for Mac that does a kind of "quantizing" (or averaging, smoothing) that I can't do with Little Miss Scale Oven.
I want the user to be able to input two lists of pitches in cents (701.95, for ex.). The lists have the same number of items. They can be large lists (say, up to 256 pitches) as long as the pair is matched.
The first list (any in-order set of pitches in cents) would called something like "list of pitches to be changed".
The second list would be any in-order set of pitches in cents of the same number of items as the first. It would be called "target list" or something.
The program would rank (simply by quantity) the items in each list. (I suppose that since the lists are already ordered, the program can simply go by the order.) The items ranked 1, or 7, in "list of pitches to be changed" would always and only be altered by moving it some ways toward the respective items ranked 1 or 7 in "target list". This is different from how quantizing usually works in several ways.
There would be a box to fill in a % of how much of the way to the target the first list moves.
Because "proximity" quantize is already available in LMSO, there's no reason to do that. This little app would do what LMSO doesn't currently do.
So, input, two matching lists of numbers. Next the user chooses "how much" shift of the first list according to the second, and hits "go", or something.
I have no idea if this is easily do-able with some other calculator, and I'm not good with spread-sheets, etc.
Anybody interested in coding this? Should I ask my usual coder (who I pay) former active member 69dodge?
example:
"list of pitches to be changed"
0., 36., 72., 96., 120., 156., 180., 204., 228., 276., 288., 312., 348., 372., 396., 432., 444., 480., 504., 528., 576., 600., 624., 660., 684., 696., 744., 768., 780., 828., 852., 864., 912., 936., 948., 996., 1020., 1032., 1068., 1104., 1116., 1152., 1188.
"target list"
0., 27.264, 65.337, 84.467, 111.731, 138.573, 165.004, 203.91, 231.174, 247.741, 289.21, 297.513, 347.408, 359.472, 386.314, 417.508, 435.084, 464.428, 498.045, 536.951, 551.318, 582.512, 617.488, 648.682, 663.049, 701.955, 735.572, 764.916, 782.492, 813.686, 840.528, 852.592, 902.487, 933.129, 952.259, 968.826, 996.09, 1034.996, 1061.427, 1088.269, 1115.533, 1134.663, 1172.736
"% move first list to target":
75. Underlining purely to make it seem like an active box.
I want the user to be able to input two lists of pitches in cents (701.95, for ex.). The lists have the same number of items. They can be large lists (say, up to 256 pitches) as long as the pair is matched.
The first list (any in-order set of pitches in cents) would called something like "list of pitches to be changed".
The second list would be any in-order set of pitches in cents of the same number of items as the first. It would be called "target list" or something.
The program would rank (simply by quantity) the items in each list. (I suppose that since the lists are already ordered, the program can simply go by the order.) The items ranked 1, or 7, in "list of pitches to be changed" would always and only be altered by moving it some ways toward the respective items ranked 1 or 7 in "target list". This is different from how quantizing usually works in several ways.
There would be a box to fill in a % of how much of the way to the target the first list moves.
Because "proximity" quantize is already available in LMSO, there's no reason to do that. This little app would do what LMSO doesn't currently do.
So, input, two matching lists of numbers. Next the user chooses "how much" shift of the first list according to the second, and hits "go", or something.
I have no idea if this is easily do-able with some other calculator, and I'm not good with spread-sheets, etc.
Anybody interested in coding this? Should I ask my usual coder (who I pay) former active member 69dodge?
example:
"list of pitches to be changed"
0., 36., 72., 96., 120., 156., 180., 204., 228., 276., 288., 312., 348., 372., 396., 432., 444., 480., 504., 528., 576., 600., 624., 660., 684., 696., 744., 768., 780., 828., 852., 864., 912., 936., 948., 996., 1020., 1032., 1068., 1104., 1116., 1152., 1188.
"target list"
0., 27.264, 65.337, 84.467, 111.731, 138.573, 165.004, 203.91, 231.174, 247.741, 289.21, 297.513, 347.408, 359.472, 386.314, 417.508, 435.084, 464.428, 498.045, 536.951, 551.318, 582.512, 617.488, 648.682, 663.049, 701.955, 735.572, 764.916, 782.492, 813.686, 840.528, 852.592, 902.487, 933.129, 952.259, 968.826, 996.09, 1034.996, 1061.427, 1088.269, 1115.533, 1134.663, 1172.736
"% move first list to target":
75. Underlining purely to make it seem like an active box.
via International Skeptics Forum http://ift.tt/2sPxGap
Aucun commentaire:
Enregistrer un commentaire