Hi all,
As part of the Google Summer of Code, I have been working on a branch to
facilitate the automated selection of follow-up tracks. Since the project
has reached the halfway point, I thought it would be good to get some
feedback on the direction I've taken and to find out how this feature could
be made more useful.
In short, I'm looking for some help in evaluating the interface and
similarity calculations, by folks using the branch with their real
libraries. A fuller explanation can be found on the project blog at <
http://gsoc2013-mixxxtracksuggestions.blogspot.com/2013/08/week-7-midterm-overview.html
>.
Comments on any aspect of this effort, including the user interface,
additional kinds of similarity to include, and the code itself, are all
welcome.
Thanks,
Chris
P.S. I'm sorry I don't have a binary build to offer. Is there some way to
add this branch to the build server?
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org
Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
