6 ms·

Wow, this is crazy because I'm working on a streaming music player of my own, also using HTML5, Backbone and Flask. (As well as Flask-SQLAlchemy and Mutagen, bu

by graue 14y ago

Wow, this is crazy because I'm working on a streaming music player of my own, also using HTML5, Backbone and Flask. (As well as Flask-SQLAlchemy and Mutagen, but those are obvious choices given Flask.) Congrats on shipping first. How long have you been working on this? I might actually use yours until my take on this is done. It certainly looks superior to Subsonic in every way. I'm still going to finish mine, because I have some different UI/design ideas. For instance, I want a visually-oriented player with cover art very prominently featured, whereas yours doesn't show art at all. But on the technical side of things, the concept is rather identical. Have you tested it on a smartphone browser and does it work/look good? I didn't use Bootstrap like you, so I'll probably have to create a totally separate mobile interface. Anyway, well done!

clicks 14y ago
Heh, that makes the three of us. Though, I also was using Bootstrap in addition to HML5+Backbone+Flask. But I think I'll abandon my project (I was in the earlier steps either way), study you guys' efforts, and work on something else.
mikevm 14y ago
Wow, so many technologies. How do you people find out (and keep track) of these frameworks?
- zanny 14y ago
  Read a lot of HN, and as a general principle, whenever you are about to write a novel application, google for it, because someone already did it and its on github. Then read a lot of code and framework manuals.
- zx2c4 14y ago
  I asked Jack Groetzinger from Seatgeek.com, "what do web people use these days?" And he said, "Flask and Backbone, use Flask and Backbone," so that I did.
monus21 14y ago
cool.I made one that streams from Google Drive on top of App Engine using Backbone. http://tunebanda.com http://tunebanda.com
- graue 14y ago
  Nice. Do you pay for Google Drive? My music collection is too large to store in the cloud affordably. But this looks cool, I'm uploading an album to my (previously unused) Drive to try it out. Edit: Hmm, seems glitchy. The music is playing but tags won't load and a random textbox is obscuring part of the UI. http://i.imgur.com/sJwd2.png http://i.imgur.com/sJwd2.png
  - monus21 14y ago
    No I don't.I'm using the Drive API https://developers.google.com/drive/ https://developers.google.com/drive/ which is free.I'm still very much testing it out but there's a lag in retrieving tags.I'm curious though how it works for you now?
bocmaxima 14y ago
let us know when you finish your cover art version. I'd love to see one that let's you sort the albums by the color of the cover art.
zx2c4 14y ago
> How long have you been working on this? Initial frontend prototype took about 30 minutes, and backend about the same. Then I spent a few hours polishing. Was mostly done in between other tasks over the course of a couple days. It's a tiny simple-ish project. But there's a lot of work to be done and things that can be added. > I want a visually-oriented player with cover art very prominently featured I'd love to have this! Please feel welcome to submit any patches or improvements from your own project. It'd be nice to have some help on it.
samps 14y ago
Crazily, I have also built a (rudimentary) similar project out of Flask, Backbone, and HTML5 audio (and Mutagen, of course). It's a piece of a larger music-management puzzle: http://beets.readthedocs.org/en/1.0rc2/plugins/web.html http://beets.readthedocs.org/en/1.0rc2/plugins/web.html Anyway, zx2c4's project is obvious slicker than mine. It's somewhat crazy that all the people on this thread saying "hey, me too" are only now finding each other. I think there are some pretty clear opportunities for collaboration here. In particular, I think it would be prudent to informally standardize a REST/JSON API for music collections so these tools can interoperable. (I'll send you email about this, zx2c4.)
- graue 14y ago
  I've looked at this one, actually! Are you the author of beets itself? beets is a great music importer. A few months ago I wanted to write something like that — looking up releases in a central repository, automatically correcting tags and renaming. But I hadn't got very far, so I abandoned the project when I saw you had already done it way better. I would prefer if it pulled data from Discogs instead of MusicBrainz. Have you considered using the Discogs API? In my limited experience, MusicBrainz disappoints me by "correcting" tags to something wrong because there's a typo in the DB, or changing the typography ("and" -> "&", "... (Part One)" -> "..., Part 1") in a way that doesn't match the official track listing. Also a very, very large percentage of albums I run through beets aren't in the MB database at all. I think I'm spoiled by how good Discogs is: these problems would mostly go away. Last.fm's data might also be an improvement, though it's not on par with Discogs. > it would be prudent to informally standardize a REST/JSON API for music collections This sounds cool. If you come up with a spec for this, I'd like to know too (email in profile).
  - samps 14y ago
    Yep, that's me! I'll send you email. :)

by graue 14y ago

clicks 14y ago

Heh, that makes the three of us. Though, I also was using Bootstrap in addition to HML5+Backbone+Flask. But I think I'll abandon my project (I was in the earlier steps either way), study you guys' efforts, and work on something else.

mikevm 14y ago

Wow, so many technologies. How do you people find out (and keep track) of these frameworks?

zanny 14y ago
Read a lot of HN, and as a general principle, whenever you are about to write a novel application, google for it, because someone already did it and its on github. Then read a lot of code and framework manuals.
zx2c4 14y ago
I asked Jack Groetzinger from Seatgeek.com, "what do web people use these days?" And he said, "Flask and Backbone, use Flask and Backbone," so that I did.

monus21 14y ago

cool.I made one that streams from Google Drive on top of App Engine using Backbone. http://tunebanda.com http://tunebanda.com

graue 14y ago
Nice. Do you pay for Google Drive? My music collection is too large to store in the cloud affordably. But this looks cool, I'm uploading an album to my (previously unused) Drive to try it out. Edit: Hmm, seems glitchy. The music is playing but tags won't load and a random textbox is obscuring part of the UI. http://i.imgur.com/sJwd2.png http://i.imgur.com/sJwd2.png
- monus21 14y ago
  No I don't.I'm using the Drive API https://developers.google.com/drive/ https://developers.google.com/drive/ which is free.I'm still very much testing it out but there's a lag in retrieving tags.I'm curious though how it works for you now?

bocmaxima 14y ago

let us know when you finish your cover art version. I'd love to see one that let's you sort the albums by the color of the cover art.

zx2c4 14y ago

> How long have you been working on this? Initial frontend prototype took about 30 minutes, and backend about the same. Then I spent a few hours polishing. Was mostly done in between other tasks over the course of a couple days. It's a tiny simple-ish project. But there's a lot of work to be done and things that can be added. > I want a visually-oriented player with cover art very prominently featured I'd love to have this! Please feel welcome to submit any patches or improvements from your own project. It'd be nice to have some help on it.

samps 14y ago

Crazily, I have also built a (rudimentary) similar project out of Flask, Backbone, and HTML5 audio (and Mutagen, of course). It's a piece of a larger music-management puzzle: http://beets.readthedocs.org/en/1.0rc2/plugins/web.html http://beets.readthedocs.org/en/1.0rc2/plugins/web.html Anyway, zx2c4's project is obvious slicker than mine. It's somewhat crazy that all the people on this thread saying "hey, me too" are only now finding each other. I think there are some pretty clear opportunities for collaboration here. In particular, I think it would be prudent to informally standardize a REST/JSON API for music collections so these tools can interoperable. (I'll send you email about this, zx2c4.)

graue 14y ago
I've looked at this one, actually! Are you the author of beets itself? beets is a great music importer. A few months ago I wanted to write something like that — looking up releases in a central repository, automatically correcting tags and renaming. But I hadn't got very far, so I abandoned the project when I saw you had already done it way better. I would prefer if it pulled data from Discogs instead of MusicBrainz. Have you considered using the Discogs API? In my limited experience, MusicBrainz disappoints me by "correcting" tags to something wrong because there's a typo in the DB, or changing the typography ("and" -> "&", "... (Part One)" -> "..., Part 1") in a way that doesn't match the official track listing. Also a very, very large percentage of albums I run through beets aren't in the MB database at all. I think I'm spoiled by how good Discogs is: these problems would mostly go away. Last.fm's data might also be an improvement, though it's not on par with Discogs. > it would be prudent to informally standardize a REST/JSON API for music collections This sounds cool. If you come up with a spec for this, I'd like to know too (email in profile).
- samps 14y ago
  Yep, that's me! I'll send you email. :)