hendrik on 11 Feb, 2011 08:37 AM
beaTunes updates files
when you commit inspections
when you analyze files
when you use the Get Info dialog
Some of these updates may be executed asynchronously, i.e. while
it appears that the task is finished, beaTunes may still be writing
information to files in the background. However, beaTunes does not
write to files randomly.
Note, that analyzing colors may lead to changes not only in the
analyzed file, but also other files. Also, if you are using the
embedding option in the general prefs, I strongly
recommend to update to 2.1.18, if you haven't done that
hendrik on 11 Feb, 2011 10:29 AM
beaTunes calculates a multi dimensional frequency based profile
for each song.
It then reduces the multi-dim values to 3 dims (think red, green,
blue), taking all existing values into account.
This changes some of the already computed 3 dimensional values,
which then have to be updated.
This also means, that the colors you see for your library are
different from the colors other people see for their library.
What happened in at least 2.1.17 and perhaps other versions
since 2.1.14, is that when embedding data into files, beaTunes
might have deleted other id3 TXXX frames. If you have valuable
stuff in TXXX frames, you might want to consider restoring.
However, the audio portion of the files was not modified.
The color analysis updates explains why analysing just a few
newly added songs changes sometimes many songs all over the place!
(Out of curiosity do you have any pointers to research literature,
etc, to explain the coloring algorithm in more detail?)
Lost tags: I probably had some replay gain and Musicbrainz tags
in TXXX but can regenerate former and live without latter, intact
audio is most critical.
Aha! I just looked in the Beatunes log file and see this:
2011-02-11 21:37:24,494 
com.tagtraum.beatunes.library.HibernateMusicLibrary: Songs still in
queue for color update: 11549
so indeed there is a lot of background activity left running and
updating my file tags even though the UI seems to give no
indication that this is still going on. It's many hours since I ran
any analysis and beaTunes has been stopped/started meanwhile. Very
nice that the queue is persisted in that way but it comes as a
surprise when there is no indication in the interface of what it's