search

jrmuizel / banshee-unofficial-plugins

Automatically exported from code.google.com/p/banshee-unofficial-plugins
0 stars 1 forks source link

Use 22.050 sampling rate to compute models #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Better similarity similarity models are computed when we compute the
features with a sampling rate of 22050Hz.

need to recompute mirage/res/*.filters

Original issue reported on code.google.com by dominik....@gmail.com on 10 Aug 2008 at 3:58

GoogleCodeExporter commented 9 years ago

Original comment by dominik....@gmail.com on 10 Aug 2008 at 4:04

GoogleCodeExporter commented 9 years ago

Original comment by dominik....@gmail.com on 10 Aug 2008 at 4:04

GoogleCodeExporter commented 9 years ago 
need to bump the version of mirage, since all similarity models will need to be
recomputed to work properly with the changes done in svn. But the new filters 
and the
octave code to write the filter files just landed in svn.

I guess there needs to be some kind of version field in the models database so 
we can
verify if the whole model-database needs to be recomputed or not.

Original comment by dominik....@gmail.com on 26 Aug 2008 at 10:00

GoogleCodeExporter commented 9 years ago 
Banshee has some code to automatically migrate the DB and refresh the data when
needed. I'll see if can "borrow" it.
I guess the version will have to go into mirage.db ?

Does the writefilters.m file you added need to be in the tarball ? I couldn't 
find
where/how it was used.

Original comment by bertrand.lorentz@gmail.com on 28 Aug 2008 at 7:21

GoogleCodeExporter commented 9 years ago 
Since everything has to be recomputed anyways I guess the simplest solution 
would be
to use "mirage-0.4.db" or "mirage-1.db" as new database name.

writefilters.m is used to compute the binary filters "dct.filter" and
"filterweights.filter" (which needed to be recomputed for 22050hz and 1024 
windowsize.

Original comment by dominik....@gmail.com on 28 Aug 2008 at 8:10

GoogleCodeExporter commented 9 years ago 
I committed the code that handles the versioning and migration of the mirage 
DB. The
migration to the current version resets the whole DB.
So I'm marking this as fixed.

Original comment by bertrand.lorentz@gmail.com on 19 Oct 2008 at 12:25