Thanks, I backed up and (gingerly) tested it. Works well, but
many of the BPM calculations are either double or half speed. I
can't see any way to improve on the outcomes. I'm using the
suggested, Rayshoot, 70-140, Use Online resources, with Quality
ranging from Fast to Accurate. May not be possible to get better
than what I'm getting, but it does mean the only way to find out is
to check EACH outcome. Any pointers?
hendrik on 16 Jan, 2011 04:29 PM
@jon: Not using Online Resources may lead to better results.
@lien: the size of your library in songs is actually irrelevant,
only the number of songs matter. If you are running in the
issue described by the screenshot repeatedly, you might need to
increase the amount of memory granted to the app or run fewer
analysis tasks in parallel (option in Analysis preference
Hi, I tried that, doesn't improve the results. But I thought an
online resource might already have had human intervention and be
more accurate than a machine.
Don't get me wrong, I like the software and am still exploring
it, but I guess it's difficult to get the BPM to match what a
person might consider it to be when lots of instruments are
involved and filling in various parts of the beat.
I think your software gets me a lot further than I'd be on my
own, and I can intervene in those instances where I know (or guess)
the BPM has been doubled. For example, it's obvious "Gloomy Sunday"
shouldn't really be 140BPM. Funny though.