JamGlue Launches "Remixing for the Masses"

Next Story

Daily Crunch: Boss Edition

JamGlue, one of the YCombinator companies, publicly launched today. JamGlue is an online community, similar to SpliceMusic, where you can listen to or mix music from a library of tracks and other mixes. JamGlue was originally in private beta with 2,500 members and a basic library of 1,500 tracks.

JamGlue, as their slogan suggests, is about providing “Remixing for the Masses” via their Flash-based mixing board. The board is a lot slicker than its Splicemusic counterpart. Key differences are that it expands to fill your browser window, allows you to add innumerable tracks to a mix which can be nested in groups, zooms in and out on tracks, and reacts to changes to the mix while still playing. JamGlue managed to do it all on their initial $18,000 budget and a bit of their own finances. Splicemusic, however, supports beatmatching and recording your own sounds within their sequencer.

Both sites allow you to remix other users’ mixes. JamGlue does this by generating an XML file representation of the mix that contains all of the edits to the original sound clips and tracks. When you’re finished, both JamGlue and SpliceMusic master the final mix and let you download your masterpiece as an mp3. JamGlue’s track nesting, however, makes it easier to manage additions to existing remixes or remixes made up of multiple remixes. Take a listen to some of my favorites from the site.

http://static.jamglue.com/flash/inline-mix-player.swf?1165951317 The Ballad of Haggity WagBag by fluffy

http://static.jamglue.com/flash/inline-mix-player.swf?1165951317 tiny avatar Help Me Somebody by tiny avatar bushofghostsremix

A community built around derivative works begs the big question: copyright? Close to Lawrence Lessig’s rip-mix-and-burn philosophy, both JamGlue and Splice use the Creative Commons license. JamGlue has it broken down into five different licenses that always allow remixing, but also control commercial use and modification of the original license. They also seek protection by respecting take-down requests under the DMCA “safe harbor” provision and user flagging.

For the launch, JamGlue is also holding a music mixing contest with the forward-thinking Nettwerk music label. The song “Peace and Hate” by the band Submarines will be put on the chopping block under the Creative Commons license for the community to mix and mash. The makers of the six most popular mixes will get prizes.

For more Creative Commons beats, check out ccMixter.org.


  • http://workingnotes2.wordpress.com/2009/11/10/links-for-2009-11-10/ links for 2009-11-10 « Working Notes 2.0

    […] The Top 10 Most Common API Pitfalls "many ISVs still treat their API as an afterthought or merely a “checkbox” on their project list rather than a core feature of their solution. As a result, APIs are not well designed or properly built and wind up costing both the vendor and its customers tens of thousands of dollars in ongoing maintenance due to infrastructure costs and the drain on engineering resources. After reviewing hundreds of actual SaaS APIs, many up to par and others distinctly subpar, it is clear that there are a number of common mistakes made when developing an API. Fortunately, each of them can be easily remedied by following best practices." (tags: howto web2.0 technology) […]

  • http://blog.wdcigroup.net/2009/11/10-most-common-api-pitfalls/ WDCi Blogs » Blog Archive » 10 most common API pitfalls

    […] blog on what to look out for when building/updating your API .  Article by Rick Nucci @ Boomi […]

  • http://blog.programmableweb.com/2010/01/06/how-to-avoid-api-slamming-and-the-api-treadmill/ How to Avoid “API Slamming” and the “API Treadmill”

    […] Nucci also noted the issue in his post The Top 10 Most Common API Pitfalls, with inadequate API versioning making it in at number 3: 3. Developing a single version of your […]

  • http://www.blogopensource.com/how-to-avoid-%e2%80%9capi-slamming%e2%80%9d-and-the-%e2%80%9capi-treadmill%e2%80%9d/ How to Avoid “API Slamming” and the “API Treadmill” | Open Source Blog

    […] Nucci also noted the issue in his post The Top 10 Most Common API Pitfalls, with inadequate API versioning making it in at number 3: 3. Developing a single version of your […]

  • http://boskabout.wordpress.com/2010/03/18/links-for-2010-03-18/ links for 2010-03-18 « Boskabout

    […] The Top 10 Most Common API Pitfalls A robust application programming interface (API) has become essential for today’s successful SaaS independent software vendors (ISVs). As a SaaS vendor, you should expect that a majority of your customers are going to require interoperability with other SaaS applications, web services, and legacy systems. As demonstrated by internet pioneers Google, Amazon, and Facebook, an open application strategy facilitates deeper customer usage and enables new revenue streams. Integration is critical for SaaS vendors, and developing a reliable API strategy is the first step toward achieving that goal. […]

  • http://www.apibook.com/blog/archives/95 API Design for C++
blog comments powered by Disqus