Netjuke and Jinzora Projects to Merge

Oh man.

This is bad bad bad news. I tried Jinzora about a year ago, and it was a huge mess. Totally unusable for collections more than a thousand or so tracks, and this odd mentality of “precompute everything before the user asks for it” just doesn’t work when you’ve got 10,000+ tracks in your collection.

I’ve been wishing that there was native MusicBrainz support in Netjuke, as well as support for a lot of other interesting features. Maybe now is the time to fork the Netjuke 1.x code base and start something interesting. I can see lots of things that need to be done:

  • Adding support for songs in more than one “genre” or “group”
  • Adding support for “collections” of music
  • Fixing the “two artists with the same name” and “two albums with the same name” problems
  • Fixing the interface with respect to recent artists & albums. (the problem now is that if I have one track from an album, and then I download the rest of the tracks, that it doesn’t show up in the ‘latest albums’ section
  • Better support for collections, soundtracks, various artists, etc.
  • Anyone interested?

    This entry was posted in Linux Stuff, Music, Web. Bookmark the permalink.

    3 Responses to Netjuke and Jinzora Projects to Merge

    1. Ross Carlson says:

      Slacy,

      Well I’m sorry you feel that way. If you haven’t tried us in over a year saying that were a “huge mess” is a bit unfair don’t you think? If you’d give 2.0 a go you’d see that we handle exceptionally large collections wonderfully (I have 60,000 tracks in my collection, quite a bit more than yours).

      I wish you’d also see that the goal here is to bring the best of both projects together. We plan on bringing all the concepts of both to our 3.0 version in the future, and our 2.0 product now is stable and powerful. Oh, and we have a Musicbrainz metaservice now that can pull artist and album data from Musicbrainz (however it’s the slowest of the 5 providers we use!)

      We also have plans to add each of the features you list above, and have plans to add many more than that.

      I hope you’ll reconsider your comments, give Jinzora 2.0 a chance (especially before you slam it) and understand what we’re trying to do with our merger…

      Thanks,

      Ross

    2. Ross Carlson says:

      Oh, BTW forgot to say I’m the new Project Lead for the combined Jinzora+Netjuke project and the founder of Jinzora…

    3. slacy says:

      Okay, I’ll give the current Jinzora a try and see how the install goes. Should I be pulling a nightly or daily (CVS) or just going with the released Jinz2.0?

      Do you guys have any thoughts about MusicBrainz integration? Thats another big thing that I was thinking would be fun to add — automatic TRM creation, and song identification and retagging. I find that ID3 tags are basically useless most of the time…

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    *

    You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>