Exaile as Counterpart of Helium-Music-Manager?

> it has mysql support for big music-collections
not applicable to Exaile, we ditched sqlite in the 0.3.x series because it was giving us issues, and making the new system run on any sql-based system would be very difficult. speed or memory use improvements to the new system would be very welcome, however.

> the collection/the folders could be organized in categories
not sure what you mean by this, explain?

> a very good tag-editor with auto-tag functions that work very well
exaile trunk has a new tag editor with a fair number of features, expansion on that would certainly be welcome.
see also bug 280319, bug 280323, bug 304258, and bug 472373

> a very useful auto-rename function, which renames and moves the files with data from tags and own schemes
there's a standing request for this, bug 11222. infrastructure for it needs to be implemented for the mass storage plugin and cd plugin anyway, so will probably end up happening at some point.

> a music browser which displays the content of the database in an html/xml style
building such an exporter would be easy enough, but i'm not sure that it'd be of much use, given that nothing other than exaile would support it. unless i'm missing what you're going for?

At any rate, if you have _specific_ requests for things that could improve Exaile, please file a new bug report (one per request!) to suggest that it be implemented. Saying we should be "like" another player is silly - we aren't trying to be like other players, we're trying to be better.

here is a screenshot of the tag-editor(advanced) in standard view, it's fully customizable:
http://www.helium-music-manager.com/assets/Uploads/hmm7-tageditor-advanced.jpg
the clou, i think, is that it takes contents for tags from filename with a scheme that could be freely defined.

auto-rename: The File Rename Wizard helps you to rename your files using templates so that you can quickly and easily rename them into a format you want. You can create additional folder structures using the included templates or by creating your own. The File Rename Wizard uses information contained in your tags to create new

here's a screenshot of the music browser which does the following: The Music Browser is where you can browse your music collection, find relationships between artists and download information for your music collection; like biographies, discographies and relations for artists both in and not currently in your collection.
http://www.helium-music-manager.com/assets/Images/Screenshots/musicbrowser.png
it's a very good way to browse all music not in folders but graphically...

i don't think saying a program should be "like" another program is silly, i take that example to make it easier show which features i mean, because you could see the other program and immediately see what i mean, so then we can speak about certain features and how to implement them in Exaile.
why don't take the best out of different programs and unite them in one "new" program, i don't think that this is silly!

more screenshots of some "features" are here:
http://www.helium-music-manager.com/screenshots/

Because applications are built upon different design decisions, they can't
just take features from others and apply them blindly – sometimes it's not
technically feasible, most of the time it's a bad idea.

Also, for instance, Helium's tag manager doesn't allow multiple tags per
track – something that has always been supported in Exaile.

what are multiple tags per track?

i don't understand why it should be a bad idea to take good features from an existing program that definetely HAS great and "unique" features as encouragement to implement it in another program to make it even better. i think that's evolution - not only in software development - no one has to reinvent the wheel.
not only in my opinion the music-management and playing programs for Linux aren't as good and complete as i.e. Helium-Music-Manager. why just don't have a look at that program before saying it is a bad idea to take features from it or saying it's silly to implement features from another software.
if you want to be better as other "players" (it's about Music-Management!) i think one HAS to look what features other "players" have and THEN make it better!

keep up your good work.

best regards!

The problem isn't that its a bad idea, it's tha tyou're going about it the wrong way. If you have SPECIFIC features you want that are in helium music manager, then by all means, file a request for them on our bugtracker. Vague suggestions of "you should be like X" will be ignored, because we probably have no experience with X, nor any inclination to try it out. It's your job as the feature requester to try it out and find SPECIFIC features that you think Exaile would benefit from, and file requests. If that's too much to ask of you, then shut up.

> what are multiple tags per track?
Allowing one track of have multiple instances of a tag. For example, if you have one song that has two artists in it, instead of having to merge them in one tag ("Cool guy and His Friend"), you can have one instance of the tag for each artist ("Cool guy", "His Friend"). This is a much more accurate way to organize music and allows the media player to search for those artists more flexibly, and is supported by most modern tag formats.

ok, i will do that, my intention for this request was that if some projectmember test the software and recognize the features "live" it's eventually much more efficient because a developer or an involved member should know directly what and how to implement!?
but it's ok, i will do the requests.

multiple tags: that feature is included in Helium since 2 years or so.

best regards.

> if some projectmember test the software and recognize the features "live"
> it's eventually much more efficient because a developer or an involved
> member should know directly what and how to implement!?

perhaps true, but if spent all our time looking at media player, we wouldn't have time to implement the features we saw. additionally, there's no guarantee that we'll see the same things you do in helium. It's much more efficient overall for you to do the initial work, and then if the developer needs firsthand experience while implementing the feature, _then_ they can go and install it.

thanks for understanding.