Re: library file across SMB?

Yup, CDJ deals with writing libraries in a very inefficient but robust manner. This is one of my primary motivations to switch over to a real database engine. CDJ does the following for *each* entry it writes out:

1) Searches the lib to see if the entry exists
2) Writes out the entire lib file with the new entry to a temp file
3) Copies the temp file over your library

This way there is always one good copy of you library in existence. It's also slow as hell. Give me a little time and I'll have it running on an Access DB which works a lot more efficiently.