anyway, just throwing out some random ideas. if the data transfer continues to be a sticking point it might be worth revisiting, but it sounds like it's a bunch extra work that we don't want to poke right at the moment
iliekcomputers: no need for a discussion tomorrow, thanks :)
ruaok
I *think* that if we improve the logging on the request consumer to identify each client correctly, we can understand things better.
In general I am happy with how things are working -- that isn't to say that we don't have a pile of improvements to make.
also, remember that we're just now putting things into production on this front. still things to be ironed out.
pristine___: your jobs ran.
shivam-kapila: how are you? how is the PR? should we have meeting or do you instead want to work on the PR?
pristine___
ruaok: seen. They are within the range. No negatives.
ruaok
ok, cool. lets undo the debug statements then.
also, I asked for 200 recs from the API, but only got 100. Is that intentional?
As per our discussion a few weeks ago, our next step is to generate similar artists using CF. But I was thinking of playing with the current data and get a playable list before moving to that. What do you think?
I am also interested in the algo to get a playlist of 25 or something from these 200 recs for a user.
shivam-kapila
ruaok: sorry. I was away for dinner
Are you free now
ruaok
shivam-kapila: here yes. how is that PR?
shivam-kapila
Multiple PRs
ruaok
pristine___: hang on a sec
shivam-kapila
1 is almost ready
2 on it
3rd tomorrow
ruaok
shivam-kapila: then I think you should focus on those PRs and keep moving.
shivam-kapila
I will post the screenshots in the PRs itself
pristine___
Hanging.
shivam-kapila
1 thing I had in mind was that I am using Spotify to fetch cover arts
all it does is debug things, but its not used right now.
pristine___
Hmmm. So what should be the next step? Making the playlist playable or an algo for choosing tracks for playlists.
ruaok
instead the last element take the recording list and makes a "playlist" from it and then launches it to the brainzplayer.
pristine___
I guess the former.
> instead the last element take the recording list and makes a "playlist" from it and then launches it to the brainzplayer.
Ooooo
ruaok
the list is "playable" its just, not very smart.
outsidecontext
ruaok: bei Mainz
pristine___
ruaok: okay. So I understand the general flow.
ruaok
outsidecontext: ahhhh, ok.
pristine___: great.
we've basically done all of the hard work -- and now we can be creative.
to make a playlist you'll need to add... something else.
there are endless possibilities.
pristine___
Like
ruaok
one suggestion is to make a playlist generator for jogging.
start kinda slow. pick up the pace, then wind down and chill out.
you could give as input: warm up: 8 minutes. ramp up: 4 minutes, steady: 10 minutes. cool down 10 minutes.
each of these sections could have BPM associated with it and then you could find tracks in the recommended tracks that fit the profile.
pristine___
BPM?
ruaok
one thought I had is this: (might be of interest to alastairp too) What if we had a personal music collection that we submitted to AB.
beats per minute
then we could download all of the acoustic data from AB and create our own Annoy indexes.
alastairp
yep, perfect usecase for unifying the brainzes
ruaok
then a user could pick a seed track and have troi generate a similar track playlist based on that seed song, based only on what is available in the local collection.
MusicIP's tool used to do that really well. I miss that!
CallerNo6 joined the channel
CallerNo6 has quit
CallerNo6 joined the channel
ruaok waves at CallerNo6
CallerNo6
oh hey boss!
alastairp
ruaok: I worry about saying it out loud, but it kind of feels like we need a local collection management app :(
I wonder how much of this you could do with a picard plugin
beets seems pretty well suited to do something like that. amarok too, probably
in terms of keeping a database of mbids of your local tracks
it turns your music collection into an API with search.
pristine___
ruaok I guess we should make a plan so that we are not lost in the endless possibilities :p I will generate a playlist for myself tomorrow and get back to you for further discussion.
alastairp
well, problem solved then. just finish that in all of the copious spare time that you have, and we can use that
ruaok
next step: AB submission and brainzplayer support.
alastairp: that's the plan!
alastairp
so, see you in 10 years then? :D
ruaok
pristine___: good plan. there are so many possibilities it is easy to get lost!
alastairp: far less than that!
picard does so much of the work, a chunk is done.
pristine___
nn!
ruaok
I'm curious to see if I can generate annoy indexes for a private collection.