1. This is the easiest way to get the first run done. The Batch Processor is extremely efficient, never opening more than one folder at a time. While creating the dbs does not require that the files are written, the generation of the Yate IDs will. So indeed this can take a long time to run.

2. This will work. You can generate the Yate IDs on the selected files via Actions>Database IDs setting the desired settings in the displayed panel. The IDs have to be generated before you do the File>Database Functions>Update Databases. This will work but is far more time consuming overall.

Which way you go is largely a matter of personal preference. At some point you will be doing updates when you change metadata in files as you won't want to rebuild completely every time you change something.

The most important thing is to think carefully about what data you require in the dbs. While you can always add or remove columns, they will not automatically get populated.

I have an album and track database which I try really hard to maintain when things change. I tend to rebuild them once or twice a year. With the filtering and advanced find mechanism they're the best way to view your entire collection in one place. I use them so often I have a droplet on my desktop which opens the dbs and Yate if necessary.

As you're new wiih this and your collection is very large why don't you just build a portion of your collection using the utility (folder A) and then try working with the db and updating incrementally. This way if you decide to change the columns you won't have to rerun everything. This will also give you a chance to play with the database before it is completely populated.

If you want I can send you a simple action which opens your dbs (if not already open); generates the Yate IDs if required (and saves them); and then updates the dbs. This will be better than doing each step manually. You can place the action on a toolbar button or use a keyboard shortcut.

Let me know if you want the action.

Download the action at: https://2manyrobots.com/actions/Update-Databases-from-Selected-Files.zip

The action is named Update Databases from Selected Files. As I'm not sure what your workflow will be I've made it as simplistic as possible. There are only four executable statements in the action and two are initially disabled.

The action works on all databases that are open when it is run. As the name suggests, the action works on selected files, not loaded files. If you want the action to process all loaded files ... open the Action Manager; select the action and check the All Files column. In my opinion this is a better workflow as it removes the possibility of only selecting partial albums.

The action as supplied does not save any modified files, nor does it save any modified databases. You can change these behaviours by editing the action:

1: Version 1.0 - Update open databases. Ensure the presence of Yate IDs
2:
3: ' Assign Yate IDs if missing.
4: Set Yate Album ID and Yate Track ID if missing
5:
6: ' Save the selected files if modified. From the context menu select Enable / Disable>Toggle Selected Statements to change the state
7: # Save selected files if modified
8:
9: ' Update all open databases
10: Update Database (all open databases)
11:
12: ' Save the database files if modified. From the context menu select Enable / Disable>Toggle Selected Statements to change the state
13: # Save Database (all open databases)

If you want to save modified files, enable the statement on line 7. Select line 7 and from the context menu do an Enable / Disable>Toggle Selected Statements.

If you want to commit database changes (ie. not have to manually save), select line 13 and from the context menu do an Enable / Disable>Toggle Selected Statements.

The action could potentially open the databases, create backups, etc. As I said I kept it simplistic.