Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
brianwhitman
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
brianwhitman
14y ago
Maybe, would be cool to try it on location data! As I stated in there, we only used TPs that had US set as location, so the data will be very US-focused.
32.
▲
by
brianwhitman
15y ago
It's actually a "manifest" -- a list of things that are included (well, should be included) -- in any hack event.
33.
▲
Syncing Echo Nest analysis to Spotify playback to make a visualizer app
(musicmachinery.com)
1 points
by
brianwhitman
15y ago
|
0 comments
34.
▲
Spotify and The Echo Nest integrate APIs
(thenextweb.com)
2 points
by
brianwhitman
15y ago
|
0 comments
35.
▲
by
brianwhitman
15y ago
I disagree with this -- i was a very heavy Napster user in 99 and am a very heavy Spotify user (and, NB, they are a customer) today. Obviously it's a fun angle for a SXSW talk, but: - The "depth of catalog" is actually incorrect -- Spotify
36.
▲
Extracting musical information from sound (Adrian Holovaty PyCon)
(pyvideo.org)
5 points
by
brianwhitman
15y ago
|
0 comments
37.
▲
by
brianwhitman
15y ago
go make an app with another label's content, let me know what you think satire means then
38.
▲
by
brianwhitman
15y ago
http://developer.echonest.com/sandbox/emi/faq.html
39.
▲
by
brianwhitman
15y ago
more on the sandboxes: http://blog.echonest.com/post/12273084434/emi-announcement developer getting started guide: http://developer.echonest.com/sandbox/emi/guide.html
40.
▲
by
brianwhitman
15y ago
Use Safari. The video doesn't seem to be loadable in any other browser. It WFM in Safari and iOS Safari. Other browsers say "Check back soon."
41.
▲
by
brianwhitman
15y ago
Right, ISRC is somewhat useful for glue but is not in wide enough use that it covers the world of music. It also reflects "recordings" not "songs" which actually cause a lot of resolution issues (radio edits, clean vs. explicit and etc.) It
42.
▲
by
brianwhitman
15y ago
direct link to webapp: http://searchformusicbydrawingapictureofit.com/
43.
▲
Search for music by drawing a picture of it
(musicmachinery.com)
11 points
by
brianwhitman
15y ago
|
1 comments
44.
▲
by
brianwhitman
15y ago
Yes-- i pay $250/mo on my plan (international data & etc) and also bought the iPhone4 subsidized day 1, and my message says I am eligible for an upgrade now.
45.
▲
by
brianwhitman
15y ago
the EN song data is dense in the sense that there is far more "columns" than rows in almost any bulk analysis -- average song unpacks to ~2000 segments, each with ~30 coefficients + global features. however, in paul's case here he's really
46.
▲
How to process a million songs in 20 minutes
(musicmachinery.com)
141 points
by
brianwhitman
15y ago
|
15 comments
47.
▲
by
brianwhitman
15y ago
sorry guys... we got sick of it getting auto-linked in IRC and chat all the time and thought it'd be better if it pointed to the thing we were talking about! http://blog.echonest.com/post/9332881544/new-pyechonest-on-g...
48.
▲
Got sick of auto-linked README.md, did something about it
(readme.md)
1 points
by
brianwhitman
15y ago
|
3 comments
49.
▲
by
brianwhitman
15y ago
Same for me -- Chrome 12.0.742.122, MBA 2.13 GHz 13" latest, 4GB ram
50.
▲
by
brianwhitman
15y ago
can you file an issue on echoprint-codegen or write us at the google group so we don't lose that? That definitely shouldn't be happening, there's an issue somewhere for sure.
51.
▲
by
brianwhitman
15y ago
it is similar to our closed source FP ENMFP, which you can read about here: http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.185.... The codegen is very different (instead of relying on echo nest chroma, it does its own onset detec
52.
▲
by
brianwhitman
15y ago
oops! as you can tell, we're pretty good with music data and not so much on the web site design. i'll try to fix it :)
53.
▲
by
brianwhitman
15y ago
the dumps are in a format that other code understands (fastingest.py) The code data is compressed using zlib (and then base64'd.) It's all on s3-- in our experience, big data dumps like this get relatively little traffic after the original
54.
▲
by
brianwhitman
15y ago
No relationship. Obviously the intent is the same. Distinction: we handle small pieces of audio from anywhere in the song (20s), ours works "over the air" via microphone, we have a huge database via our content partners.
55.
▲
by
brianwhitman
15y ago
there's a google group-- that's probably the easiest for now. you can pester alastairp on the musicbrainz IRC channel too (he's our resident musicbrainz/EN liaison)
56.
▲
by
brianwhitman
15y ago
for more on the whys, here is the EN blog post: http://blog.echonest.com/post/6824753703/announcing-echoprin...
57.
▲
by
brianwhitman
15y ago
We invented everything about Echoprint from scratch, working with some awesome scientists and audio guys. I'm not a lawyer and won't comment on legal stuff here though.
58.
▲
by
brianwhitman
15y ago
if it's echoprint related, write echoprint@echonest.com -- otherwise contact@echonest.com (i'm brian@echonest.com but i doubt you want to write just me)
59.
▲
by
brianwhitman
15y ago
if you have any questions, let me know. we're very excited about this!
60.
▲
by
brianwhitman
15y ago
Yeah, and I love that half the posts are praising its lightweight nature while the other half are complaining about "obvious" features that it doesn't have :)
More ›