Advice for upgrading from vers 3 to vers 4
Hello,
Having just purchased version 3 and analyzed a large library, I thought I would ask about what should be reanalyzed for version 4.
My understanding is the beats per minute is more accurate, so probably that analysis should be rerun, replacing the calculated version 3 values.
Also, there are new key and color algorithms. Are these more accurate, and should new values be calculated for these as well?
Would you recommend replacing the tags associated with a song? How many tags should be attached to a song? I believe I initially grabbed about 10 tags, as it seemed four or five tags were too few.
The replay gain calculation probably will be the same for version 3 and four, am I correct? So that does not need to be recalculated?
Does Version 4 take power naps?
In general, you probably have many folks who will upgrade from version 3 to version 4, and some practical advice, maybe a faq would be useful.
Thanks.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Hendrik Schreib... on 20 Aug, 2014 03:07 PM
Hey,
let me try to address your questions.
The new OnsetPeak algorithm distinguishes much better between e.g. 60 and 120 BPM (double/halve error, also known as octave error). Unless you have manually determined values in your collection, re-analyzing for BPM will probably improve your metadata.
OnsetPeak is also faster than the previous algorithm.
The color scheme as a whole has changed. For color to work as expected, I recommend re-analyzing the whole library, replacing every value.
The new scheme differs from the old one in that it is not library-specific anymore and can be calculated more efficiently, especially in large collections. By comparison, the old scheme had rather poor scalability and was not well suited to collection with multiple ten thousand songs.
The key algorithm is now much better for electronic dance music (EDM). It also takes more audio content into account. If you have a lot of EDM, re-analyzing might be worth your time. However, because it takes more audio content into account, the algorithm got slower rather than faster.
The tags are still imported from Last.fm and haven't changed (I guess you used the plugin). So re-importing them will do you no good. However, if you are interested in inferring moods from your tags, you might want to check that task.
Track ReplayGain has not changed (other than that you can now set a target level).
However, Album ReplayGain has been added. Beware though: Calculating Album ReplayGain requires to work through all songs in an album to calculate the value. This is a calculation intensive task.
During analysis, beaTunes 4 informs OS X that it performs a user initiated task and therefore it should not nap. The same happens during playback.
Additionally, beaTunes 4 introduces a number of other new features. A new integrated music player, automatic segmentation, ... here's the list.
Note that segmentation is rather calculation intensive. Whole files have to be read and then there's a lot to calculate - in other words: segmentation takes a while, should you want to analyze your library.
Cheers,
-hendrik
2 Posted by beatunes on 21 Aug, 2014 12:36 PM
One more question: (of course)
What about java? I have been running vers 6, but it is getting time maybe for vers 7 (for non Beatune reasons).
What happens if I update to v 7? Does beatunes deal with that?
Does that cause problems if I go back to vers 6 java? back to beatunes v3?
Thanks,
Support Staff 3 Posted by Hendrik Schreib... on 21 Aug, 2014 12:42 PM
beaTunes 4 comes with its own bundled VM, so there should be no problem whatsoever. Currently that's version 8. The exact version number is displayed in the
Aboutdialog.Cheers,
-hendrik