I would be interested in knowing how Tagalicious 1.0 "messed up your
database" if you have to personally approve all the changes that
Tagalicious suggests. None of it is automatic. Are you tagging
tracks and then just immediately choosing to update all your tracks?
The "msng" bug was limited to the 1.1 betas, so I have trouble seeing
how you complain about that when you didn't report it. I know of no
trouble transferring tags to iTunes in the 1.0.x releases. (By the
way, the "msng" bug is fixed in the latest 1.1 beta.)
Regardless, you're right that there are crashers and problems with the
current release version. That's why we opened this Google group,
because there were problems that we didn't catch before releasing 1.0
and 1.0.1. But many of our users have also had little trouble with
the release version.
I'm testing Tagalicious on my own database (5000 songs large), and one
developer at our office has a library roughly matching your 40000 song
database. We have identified and corrected certain problems on our
own but we can't find all of them. If beta testers don't report
problems and crash reports, we can't fix their problems.
Additionally, crash reports are automatically sorted when we receive
them so we can look at the frequency and see which problems are
occurring the most. If you can't be bothered to send in your crash
reports, I won't know that you're having problems.
There are many more users on this group that have made responses that
are far more helpful than your first post to this list (despite your
contention that you've tried all the betas). Some people have
reported crashers that are too constant to make the current beta
usable. We're working on resolving these before the 1.1 release. It
would have been nice to hear about your thoughts and problems earlier,
when you first encountered them.
If you'd like to continue this conversation focused on your specific
problems, I'm happy to do so.
-- Simone