NOW if the developers want to give users the OPTIONS of removing items during the installation this will help a lot in giving people a streamlined player without all the BS!

Damn, that would be like thinking mig is sarcastic or something.

Anyhow, your comments about functionality and memory are exactly my point.

Because we are on top of mozilla, we’re the mozilla plugin system, not yet-another-custom-C/C++ plugin system. One writes plugins for Songbird in the same scripting language that web programmers use, not yet-another-custom-scripting-language.

We’re inheriting a skilled developer community of thousands of thousands of eager programmers, so I have absolute and unquestioning faith that such functionality you request will eventually get implemented by somebody. Even if it might not be us.

That’s why we believe, eventually, we will stomp every other media player. That’s why we chose Mozilla and XUL.

And, to be honest, that’s why we put up with the fact that it wants to eat so much RAM.

We can tune the RAM usage. That’s way easier than trying to train up 10,000 skilled developers from scratch.

You have to really “have the vision” to see it, right now, because there’s only 4 or 5 extensions out there so far, and there’s nothing on the website set to present this to the users.

But we have the vision. We have the religion.

We’re on the way.

Therein I see an opening for you.

Here are the most important features from foobar which you ought to implement

1. gapless via LAME tags.
2. diskwriter support. the best feature of foobar is the diskwriter plugin which allows you to convert from one format to another, even using command lines for encoders like LAME (ex: v2-q2-vbr new). It also allows you to specify how you want directories created, getting information from the metatags. Extremely powerful, you should implement this in some form.
3. Masstagger, which allows me to change up the tags for multiple files quickly and efficiently.
4. freedb. This plugin allows me to select a number of tracks and lookup info regarding them on the freedb (say if they’re all part of an album)

Now, I have a few other ideas.

1. visual cd burning support. What I mean by this is to have each song that is put in the burn list be represented by a bar, that can be made to overlap with otherbars, and you can choose to either have them overlap or have one cut off the other.
2. EAC-like cd ripping functionality.

and on the memory thing, I think that you can afford to be less than frugal, due to the huge amounts of RAM in modern systems, but still keep watch. 7mb is nothing when you have 1gb, and I personally wouldn’t really care if memory usage went up to 50-70 mb. That said, don’t go above 100mb.

Anyways, I like the player so far, it has great potential, keep it up!!

If Peter wants to port his internal core to be a Mozilla plugin and release it under GPL, sure.

Anybody wanna take bets on his likelihood of doing that?