From d527421da3b03477a14f379e92e3c9110f45d24a Mon Sep 17 00:00:00 2001 From: Sevag Hanssian Date: Thu, 19 Aug 2021 09:50:16 -0400 Subject: [PATCH] Remove unnecessary fork description in README --- README.md | 7 ------- 1 file changed, 7 deletions(-) diff --git a/README.md b/README.md index 439d4de..6f47ca8 100644 --- a/README.md +++ b/README.md @@ -6,13 +6,6 @@ A python package to evaluate source separation results using the [MUSDB18](https://sigsep.github.io/musdb) dataset. This package was part of the [MUS task](https://sisec.inria.fr/home/2018-professionally-produced-music-recordings/) of the [Signal Separation Evaluation Campaign (SISEC)](https://sisec.inria.fr/). -### Note on the sevagh fork - -My fork adds considerable speedups by using cupy for offloading the fft, ifft, and linalg executions of BSSv4 to the user's NVIDIA GPU. However, this has several downsides: -* Switching to using GPU arithmetic and float32 changes output values due to numerical precision differences -* Managing memory is not straightforward, often requiring the user to disable and re-enable the cupy fft cache between runs -* Installing GPU libraries is a burden on end users, so it's a bigger conversation to merge such a requirement upstream - ### BSSEval v4 The BSSEval metrics, as implemented in the [MATLAB toolboxes](http://bass-db.gforge.inria.fr/bss_eval/) and their re-implementation in [mir_eval](http://craffel.github.io/mir_eval/#module-mir_eval.separation) are widely used in the audio separation literature. One particularity of BSSEval is to compute the metrics after optimally matching the estimates to the true sources through linear distortion filters. This allows the criteria to be robust to some linear mismatches. Apart from the optional evaluation for all possible permutations of the sources, this matching is the reason for most of the computation cost of BSSEval, especially considering it is done for each evaluation window when the metrics are computed on a framewise basis.