03-30-2020, 04:22 AM
(03-30-2020, 04:14 AM)KHS Wrote:Additionally, upon Import of a .CHO file, the editable fields are first shown, but what is NOT shown is how they'd be populated from the metadata in the .CHO file. Is there a good reason why that data is not shown in a situation where user input is invited without the user being aware of what will be inputted automatically?(03-30-2020, 03:58 AM)Zubersoft Wrote: It all seems to work for me. I just imported this:Many thanks to you and to Johan! Is it possible that you could offer the user a choice upon "file swap" or re-import (at least with .CHO files) to have the library metadata edited thereby? At least the metadata that's accepted from .CHO files? That would make the process of fine-tuning .CHO files a lot less frustrating.
Code:{title: Test}
{year: 1985}
{year: 2003}
{meta customgroup test1}
{meta customgroup test2}
The new song had multiple years listed and multiple custom group entries. This does only get picked up when you first import though - I don't make changes to the library metadata if you edit the file and it gets parsed again.
As Johan specified, CSV uses the plural form because it accepts multiple values in the column, but the .cho only supports one value per meta directive.
Mike