Statistics better oriented for musical parameters.

[pikurasa]

Seeking proposals and input for this:

This is what statistics currently shows for Music Blocks:

Let's think of some parameters better oriented for music.

Some ideas off top of head:

• meter
• key
• what factor of note values are used (i.e. if factor of 2, then "duple". If factor of two "triplets". If factor of five exist, "quintuplets")
• pitch names used (ignore octave and duplicates)
• sharps/flats used
• highest note
• lowest note
• "musical form" (probably just chart out the action blocks)

...I will think some more about this, but wanted to get this started.

[pikurasa]

I reviewed this now. For the most part, I agree with what I said before. I might add:

meter

and "meters"

key

and "keys"
also, do the pitches in the code seem congruent with the key, and if not, which ones (not necessarily "good" or "bad" -- just an important stat).

what factor of note values are used (i.e. if factor of 2, then "duple". If factor of two "triplets". If factor of five exist, "quintuplets")
pitch names used (ignore octave and duplicates)

"pitch classes" (means ignore octave); we should put this info with "key". If there are multiple keys, we should compare the key and the pitch classes used for each section of music.

sharps/flats used

This should be with "key". This is redundant.

highest note
lowest note

This seems obvious, but is very important. It would also be helpful to know its location. For example, is it near the beginning, the end, or somewhere in the middle. "At what proportion through the piece do these events occur?" (e.g. two thirds to the end) would be helpful.

"musical form" (probably just chart out the action blocks)

This would be helpful. Also a note on whether the action blocks are transformed in any way (i.e. temporal or pitch)

I might add:

• rests used?
• ornaments used?
• dynamics used and where? (quietest spot and loudest also helpful)

(gotta go for now...)

[pikurasa]

@sksum I think this would be a good one to tackle before the end of summer.

@walterbender what do you think? Anything else to add?

[walterbender]

I think these are all great ideas... I do think it would good to still reflect some of the programming ideas too:
did they use actions?
boxes?
the heap?

Any advanced concepts such as recursion, the arg block, return values?

and anything about sensors...

[walterbender]

Another thing: was the music chromatic or in a key(s)? @pikurasa can you think of a simple algorithm for determining this? (I suspect we could do a simple statistical analysis.

[pikurasa]

@pikurasa can you think of a simple algorithm for determining this? (I suspect we could do a simple statistical analysis.

The simplest thing is to take the user's word for what key they are in. We could then come up with stats for how many notes are in the key, and how many are out of the key.

If we want a deeper dive, I suggest we start with the formula I gave to Aviral. Do you want the "deeper dive"?

[walterbender]

I'd love the deeper dive for my own education. But I think we can keep it simple here. The only tricky bit might be tracking explicit key changes.

[walterbender]

The basics are done now. We can perhaps open a new issue with explicit ideas for enhancements.