King, the problem comes from tags written to the files themselves.
The db tagging for me at least is pretty good. Full credit for the speed of it to the whole team.
Rhino's way would speed it up a LOT more though for tags saved in the actual files when several changes are made.
So you think it's not the database but writing to the ID3 tags.
well the way it is now many times you need to go back and save the same file with a new change, the changes matt did before (not the speed of the database changes) he said was to keep the tags from being written. but the only thing i see is many pop ups asking me if i really want to do the save (reminds me of pop-up ads really), and then i have to make more changes after it saves.
all of this pop-up warnings could be avoided if each file had a way to undo the changes (but thats another subject).