Implement more separation metrics

Although bss_eval is pretty standard, there are more: http://bass-db.gforge.inria.fr/peass/ http://labrosa.ee.columbia.edu/projects/snreval/

[bmcfee]

My $2e-2: i think it makes sense to have a self-contained bsseval package and either deprecate the implementation in mir_eval, or refactor it to depend on the bsseval implementation. A few arguments for this:

1. Google-ability, as mentioned above.
2. It’s the only functionality in mir_eval that depends on audio signal processing (not counting sonification), and has always been a bit of an odd one out.
3. Potentially wider adoption / more maintainers. The bss eval metrics in mir_eval are somewhat baroque (to maintain compatibility with the matlab package), and AFAIK we don’t really have a dedicated maintainer for that at this point. I’ve spent enough time in the guts of this module to know what a pain it is to get right (BLAS dependencies, anyone?), so anything we can do to increase participation / maintainership is a good thing IMO.

[faroit]

Thanks for your feedback. I think wrapping around bsseval makes sense. The current museval is actually quite close to the eval pipeline of mir_eval with respect to the metric artifacts. We then would include a mir_eval api compatibility layer so that using bsseval could be a drop-in replacement for mir_eval.separation.evaluate.

Now we need to work on bssevalto match the rigor of mir_eval with respect to testing and code coverage – especially regression tests. I will get back to you here when we are done.