I've been giving this some thought and I have a potential approach which would be a real pain. It would involve you running two batch scripts for any one artist. Yate basically works with files as units and given the current state of the action library this type of thing would be quite tedious.
However, as is quite often the case I tend to overthink some of these interesting requests. 🙂
Why not simply create a Track database in Yate. I personally maintain two databases for my personal collection. The first is an Album database of all the albums in my library. I carry this on my phone so that wherever I am I know what albums I own and what's recent, etc.. The second is a track database of every track I own.
Why not create a track database which contains the file path (mandatory), the title, artist, genre, track number and whatever other information that you desire. You can open the database in Yate, filter down to a particular artist and then easily see what genres are used. There is not currently any counting functionality except by filtering....but it should be pretty obvious what genre is prevalent. You can then select all the tracks with different genres and open them in the Yate main window from the context menu. Once open in the main window, you can select all the tracks and edit the genre field once for all of them. You can even apply the changes back to the database if you desire.
If this type of thing becomes more common, I can add functionality to the database code to do counting, etc.
To create a Track database you must first design the Export set to be used. You do this in Preferences>Export Sets. As I said the only mandator field is the file path but you can add any other columns that you'd like to see. (Obviously Artist and Genre are needed for what you want). You can drag and drop the items to change the order in the produced database.
Once you have your Export Set you have to write a simple one line action which is a 'Create Track Database'. Other than naming the database to be produced, I'd leave all the other options to their default values. (Other than auto open if you wish). If you'd like to see artwork in the database I suggest adding an 'Artwork to folder.jpg' function to the action. The database handler will display the images contained in the folder.jpg files.
To build your database start the batch processor from Actions>Batch Processor Wizard. Select the action you created and drag over the root folder of your collection. Once started the batch processor will run over your entire collection and create the database.
Once the database has been created you can open it at any time or simply drag it to the file area of the main window. When a database is open and has the focus you can see its help from Help>Help for Current Context.
Let me know if this works for you or if you need any assistance.
|