Commentary

Serdar Yegulalp
 

Songbird 0.5rc1: Still Hatching

A while back I looked at an earlier release of the Mozilla-derived open-source music player Songbird, and while I liked what I saw it was still undeniably rough.  Now I've looked at the first release candidate of the new version 0.5 of the program, and while it's still promising, there's a few too many places where the promise just isn't completely fulfilled yet.  But hey, welcome to beta software.

A while back I looked at an earlier release of the Mozilla-derived open-source music player Songbird, and while I liked what I saw it was still undeniably rough.  Now I've looked at the first release candidate of the new version 0.5 of the program, and while it's still promising, there's a few too many places where the promise just isn't completely fulfilled yet.  But hey, welcome to beta software.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The first and biggest problem I've seen consistently with Songbird is that it doesn't do the greatest job of handling very large music libraries.  If you try to open or scan through a very large library, the program's interface seizes up and goes unresponsive for seconds at a time.  My music library has more than 15,000 tracks in it, and I know at least a couple of other people who have collections that dwarf mine.  Music lovers have big libraries, and if Songbird can't at least work elegantly with a large library then it's going to be a real barrier to adoption (and, in my case at least, even testing it casually).


Songbird 0.5rc1's interface still hesitates when dealing with large music libraries (on the order of thousands of tracks).  A small subset is visible here.
(click image for larger view)


Songbird 0.5rc1's interface still hesitates when dealing with large music libraries (on the order of thousands of tracks). A small subset is visible here.

Other omissions at this stage are minor but striking.  In version 0.4, the only way to get a Now Playing list -- something that's standard issue on most music players -- was to install a third-party plugin.  Not too much of a hassle, since the mechanism for installing plugins is integrated directly into the program a la Firefox itself.  In 0.5, this is still the only way to get a Now Playing list, and the plugin in question doesn't work with 0.5.  At least, not yet.

Some things that I knew I wanted to see are already here.  A third-party extension lets you access the eMusic DRM-free online service (a favorite of mine), and there's talk of adding support for Amazon's MP3 download service as well.  Both of these fit perfectly into the "social" aspect of the player, where finding music and connecting with other music lovers is as important as savoring what you have.  Those are all great, but I'm still hoping the core components of the player -- the library, the UI -- are what they need to be by the time there's a 1 to the left of the decimal point.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links