I am still having difficulty posting a screen shot. So, I will try to offer additional details in lieu of a screen shot. My 23000 plus music files are stored in a database created within a program called MusiCHI. Each record contains a number of different fields, including a field entitled "Composition".
I have created and deleted a number of Libraries in MusicBee. Each time I have created a new MusicBee Library, the process has successfully accessed my MusiCHI database and pulled over all fields which match the named "standard" (Tag 1) fields in MusicBee.
So, I have a very usable MusicBee library - except for the fact that many of my MusiCHI entries do not contain the Composition name in the Title field. Example: A Beethoven symphony with 4 movements contains only the movement names in the Title field. The symphony name is contained in the Composition field. Therefore, when this data is pulled into the MusicBee Library, the movement names come over into the Title field. But, the symphony name information is not captured because there is no Composition field in the MusicBee Tag 1 set of fields.
Now, in Patch 3.1, there is a new field called Work, but it is not useful in my case because I cannot rename the MusiCHI Composition field to Work and I cannot rename the MusicBee Work field to Composition.
Bottom line: I can rename one of the MusicBee custom fields to Composition and I have done so before creating a new library. However, MusicBee will not populate this custom field during the library creation process.
So, my simple question is: How do I "auto-populate" a MusicBee custom field? If it is not possible to "auto-populate" a MusicBee custom field during the Library creation process, then please just tell me that it cannot be done and I'll move on.
Thanks,
Art