Yep. As the title suggests, I've ripped a 4-disc set that is unrecognised by the ripping software & therefore has no track names.

Roon does, however, seem to recognise it, so I've taken screen-shots from Roon, converted them to text using an online OCR & have made a text file of the track list.

Now all I need to do is get the text file into Yate.

It's probably very straightforward, but I've had a look around & can't see what I need to do.

Perfect, thanks!

The action need not be modified to support any fixed pattern text input. There is no code to specifically assign Title or any other combination of fields.

The action only has one input option ... a File to Tag template. The template visually describes the layout of the text to be read from a file or the clipboard.

File to Tag templates are defined in Preferences - File to Tag. Typically they are used to extract metadata from a filename. They have been expanded to allow for \n (newline) and \- (tab) escape sequences so that multi line input can be processed.

The bottom line is that you have to define the template which describes the formatting of your text. The action reads the template and uses it assign the text components to the appropriate fields.

While the action typically associates one text record linearly against files it can also extract a file path and use to make the associations. This is done by using a (Variable 0) token in the template to define the location of the file path. If you want to assign data linearly to the selected files, you never have to use the construct.

Here's a sample template which is multiline:

❨Title❩\n❨Artist❩\n❨Genre❩·--·❨Year❩

It specifies a three line record. Line 1 is the Title; line 2 the Artist; line 3 the Genre separated from the Year by a 'space dash dash space' sequence.

You can read about how the action works by right clicking on it in the Action Manager and clicking on Resource Documentation.

File to Tag templates have online help available within the token editor.

I cleaned up the action twice yesterday so you might want to do a Yate>Check for Action Updates. You should also install Yate v6.10.2.1 which was released yesterday. Do a Yate>Check for Application Updates.

Oops .. entirely my fault. At the last minute I decided to rename a few named variables to something that made sense and I messed up the change. 😥

Do a Yate>Check for Action Updates and you'll get v4.1 of the action.

Sorry.

Yes, you have two because I got myself into a scenario where the action wouldn't update correctly because all of the actions from the pre v4.0 action no longer exist in the download. I create the dummy action, labelled with (Main) to get around the issue. The (main) action simply calls the non (Main) action. Once everyone updates to the latest version I can get around the issue and automatically delete (Main).

Yate cannot run an action without having selected files. You can specify that an action can run without selected files in which case Yate will automatically supply a single dummy file so that the interpreter can execute.

The error message says it all. You have to select the files that you want Yate to manipulate with the action. You can automatically have the action select all loaded files by going to the Action Manager, highlighting the action and check the checkbox in the All Files column. If you do that all loaded files will be selected when the action starts.