Distinguishing between settings in tunebooks

[jomimc]

I was thinking of writing an algorithm to generate sets. The basic idea is to start with a tunebook, but I realised I'll run into a serious problem since saving a tune in a tunebook doesn't distinguish between settings. Is there any chance of implementing something like that on the website? I notice that sets.json actually does include the setting ID.

I'm also curious about which settings are more popular, within a tune, so it'd be nice to know that.

[zmoon]

which settings are more popular, within a tune,

One thing you could do currently is to look at the existing tune sets, for which you do have to pick a specific setting. For example, according to the current sets data archive from this repository, Cooley's reel appears in 1617 sets, and these are the settings that have been picked 10 or more times (left is setting ID, right is the count; the original/first setting, posted by Jeremy, dominates):

1        1293
22061     105
12343      65
12342      21
31475      21
20796      20
24552      16
21423      10

Another data source, which we don't currently have easy access to but could be straightforward, is tune bookmarks (e.g. count of bookmarks for a given tune setting), which are setting-specific, as opposed to adding a tune to your tunebook.

[adactio]

There isn’t a way to include all the setting IDs of a tune in the tunebook information; you'd need to go to the individual tune page to get that information, e.g.:

https://thesession.org/tunes/1?format=json

As for figuring out which settings are most popular, you can order the output by popularity like this:

https://thesession.org/tunes/1?orderby=popular&format=json

[zmoon]

@adactio what is the popular sorting based on? Appearance in sets or bookmarks or something else?

[zmoon]

@adactio for the individual tune page JSON, would it be possible to include the number of bookmarks each setting has?

[adactio]

@adactio what is the popular sorting based on? Appearance in sets or bookmarks or something else?

Yes, number of times a setting has been bookmarked.

@adactio for the individual tune page JSON, would it be possible to include the number of bookmarks each setting has?

What would the use case be here? This isn't information that's exposed in the HTML so I'm reluctant to expose it in other formats.

[zmoon]

What would the use case be here? This isn't information that's exposed in the HTML so I'm reluctant to expose it in other formats.

That's understandable.

I think one use case is still distinguishing between settings. Although the popular sorting that you showed here does provide a lot of the power given that it's based on the bookmark counts, one could do it more precisely if the actual counts were available. For example, if setting #​1 and #​2 in a ranking have similar (or the same) bookmark counts, we might want to employ different logic than if there is a clear leader. Or if all settings have low or no bookmark counts.

And also I just think it could an interesting variable to analyze.