Veteze
My feedback
5 results found
-
7 votes
An error occurred while saving the comment Veteze
supported this idea
·
-
19 votes
An error occurred while saving the comment Veteze
commented
Anyone? ;) Would love this!
Veteze
shared this idea
·
-
25 votes
Thanks for the kind words Ben! We’d love to integrate with Band Camp, but they don’t have an API for their music catalog.
(Crates is powered by Beatport’s API. If BandCamp adds an API for their catalog, then we can explore integration with them as well.)
Veteze
supported this idea
·
-
9 votes
Thanks for the feedback Ryan – you’re right that we could capture a “Times Charted” every time we load the track, but tracks only get loaded when a user plays/selects them. This means the data would only get updated on tracks users are selecting, so I don’t think it’s that valuable.
The other thing is that not many DJs are posting Charts on Beatport right now, for various reasons, so I actually don’t think “Times Charted” is a very meaningful metric until Beatport expands their playlists/charts. It’s not a priority of theirs right now, unfortunately.
We’ll definitely keep an eye on this once we get access to the new Beatport API next year though, hopefully. :) Keep the feedback/ideas coming until then!
An error occurred while saving the comment Veteze
commented
http://crates.co/db.php?fetchRereleases !!! just a new column in here!
okay I'll stop.
An error occurred while saving the comment Veteze
commented
Oy, typpos!
On the call to beatport that gets the charts; you can get the chart count from that.
TrackId, ChartedCcount, LastUpdatedDate
An error occurred while saving the comment Veteze
commented
Really? I feel like it could be bolted on to what you're doing to mark the tracks as played.
On the call to beatport that gets the charts you get the chart count.
On http://crates.co/db.php?markPreviewed add a new property in there called charted.
{"result":10829287,"charted",99,"trace":{"connect":0.56290626525879,"query":2.2041797637939}}
Where 99 is the count of the JSON array elements returned by Beatport.
I imagine you're keeping a table of all the tracks I've played? Or is it more simple than that? json data?
Yeah I have no Idea what the DB structure is on your side. LOL.
I imagine you would have to create a table of tracks if you don't have one already.
TrackId, ChartedAccount, LastUpdatedDate
Insert a record if it doesn't exist.
Update a record if it's more than a day old (this would get around anyone who is trying to hack this obviously hackable system).You're already melding whether I've played a track nicely into the UI, so the played count could just float right on in there too no?
And then append a little filtery action up in the top right?
Anyway. I have ideas! ;) I'm a development director in Canada so let me know if you want any unsolicited input.
;)
p.s. I FUCKING LOVE YOU GUYUSSS!! :)
An error occurred while saving the comment Veteze
commented
Hey guys, this would be pretty awesome actually. I'm about 4 months behind in my list now and can't catch up and while I wouldnt always want to do this it would be nice to skip a couple months but still be able to filter out tracks have never been charted for example.
Store the number of times a track has been charted. Refresh the value once a day? And then give us a filter that lets us set how many chartings a track should have before we see it.
i.e. i'd love to filter out all the 0 charted tracks to get caught up to the current month. This would pull out about 80% of the songs I think.
-
50 votes
Out of curiosity, what interests you guys more:
(1) Infinite Scroll – more tracks constantly load, without you needing to click to the next page?
(2) More Tracks Per Page – Just more tracks per page, like 100 or 150, like the Beatport site?
Thanks for feedback!
An error occurred while saving the comment Veteze
commented
#2 definitely.
I see you guys fixed the sorting problems. Now we just need to be able to get past page 200 again! ;)