The Add to iTunes functionality currently works only with loaded tracks. However, the ability to add a track specified at runtime is trivial to add. This would allow you to walk your database as opposed to your file structure. I'm assuming you have some indication in the DB as to whether the track is already in iTunes. Adding a track which is already in iTunes can be prone to duplicates.

That being said, I'm not sure you would run that much faster. All my tracks are on a NAS drive and the load time is negligible compared to the time that iTunes takes to actually add the track. My iTunes test library has about 45k tracks and adding a new album can take ten minutes. Sometimes it takes ten seconds. After all these years, I still have no concrete idea as to what they are doing.

If your DB has a flag indicating whether the track is already in iTunes, we can do it now with a net saving as not all files will have to be added and therefore not all files will have to be loaded. If all tracks are being added there will be no saving. If not all tracks have to be added, the action to do so is pretty easy. It involves opening your DB as a Query Database. For each line check if the file has to be added. If it does, do a Load and Run on the file path calling an action which does the add. If you need any help with this, just export the Export set used to define the DB and send it to me at support@2manyrobots.com. If not obvious, describe the column used to detect the need to add the track.

If all tracks have to be added I will look into adding the Add to iTune by path functionality. It'll have to wait until after the next release comes out as it's really close.

Thank you....running it right now, and it's working great. Guess i'll have to accept the speed of iTunes :-/