So, Im new to YATE and like it very much. My main use is for tagging a large collection of live recordings. These recordings do not typically come with properly named files, or properly tagged. They do , however, usually come with a text file that contains the set list.

If there were a feature that would allow importing of filenames from a text file this would certainly make the tagging process tons easier. I have used software previously that had this capability. It would import titles, one line at a time, from a list (a text entry box that was temporarily saved). With a little cut/paste and editing, you could rename files in a flash. This would be a great help. Maybe, some kind of "import titles from selection could be used too.

Wow. Thanks so much. I will definitely give it a try. The new version sounds great, too. As a new user, I have yet to dig into rolling my own actions, but I guess there's no time like the present.

-a humble new YATE user

Very useful. (I used to do the same with A Better Finder Rename and then used Media Rage to process file names to tags.)

But it is limited to each line containing a title. How would you handle a text file that contained, for instance:

01. title1
02. title2

or :

01 title1
02 title2

these are common scenarios.

I wonder if and how the extract titles inline action could be more general. is there any way to past the text through a file to tag template, specifically?

However, the Scanner statement offers a larger degree of programmability so that you could easily write a single extraction to handle both the above scenarios.

Yes, it does, and you could. Perfect! Implementing that handles all three of the above scenarios: lines with only title, lines with "number title" ("number<space>title") and lines with "number. title" ("number<period><space>title"). Thanks again.

FYI I made two variants with this addition, one with the prompt for file at the top as you had it, and a second without the prompt for file, but just uses "read file" to load a text file at a static path, such as: /PATH/TO/fl-temp.txt. That way you skip the file dialog, and just copy and paste the title lines into that static text file as needed for each album you need to process this way.

(Super convenient… I'm well on my way to reducing the apps I use to manage audio files significantly, as Yate cuts out one outlying scenario that required fiddling in multiple apps after another… Now if there were a way to do the same with text on the clipboard, that could avoid loading files altogether… hmm… I'll be stunned if there isn't…)

damn, do neither of us ever sleep? 😉

puzzled by this response tho. the actions operate on a current file, meaning the audio file and it's metadata. but what about a text source? the import action you give says:

Read Text File "\v1" into named variable 'contents'

I changed this to:

Text from Clipboard to named variable 'contents' (all)

Seems to work just as expected. That saves a step, as typically the workflow for this would be to copy and paste the track info data from some kind info file to a temp file. Now I can just copy the data and run the action. No intermediate file needed.