Hi,

I can't seem to find the IMPORTDATE tag which can be used in Roon
my goal is to get the Finder creation date of the album folder and copy it to importdate tag and for future albums have this done automatically.

Thanks
Christian

I've created an action which will copy a track's containing folder's creation date to the Import Date tag.

Download and install the action at: https://2manyrobots.com/actions/ContainingFolderCreationDatetoImportDate.zip

The action works on all selected files. The selected files do not have to be in the same folder.

I tested it with a album located in the downloads folder and works perfect,
but this is not where my music is stored it's on a Mac mini external drive located in another room and that don't seem to work would that be possible you think, if not no problem I'll move the hdd to this Yate Mac and all future albums will be processed in the downloads folder and then moved.

If you mount the drive you can load the files. At that point everything should just work. You will first have to configure the Mac Mini to share the drive.

This Importdate tag will it work on other players supporting this tag or is it only a custom Roon tag I ask because maybe it can be build in as an option next to the Tagging Time in the more info tab, if not

As far as I know IMPORTDATE is only read by Roon. You can't change the built in editing panels. However on the resources web page in the Templates section there is a download for the built in panels as custom panels. You can import the copy of the More Info panel into the Custom Panel editor and then modify it to add the Import Tag field. From that point on, simply use the modified More Info panel as opposed to the original. In the same template section you will find an Extended Info Editing Panel download where Info was modified to add a field.

I like to have this done automatically but I already have and action run after import from MB anyway around this?

Actions can call other actions. Create an action which calls the current action you're running and then the new one. Each statement is a Run statement. If you want to run two actions, you'll need two Run statements. Once your action is created, select the new container action to be run after importing.

Thank you.

🙂

This error message is only displayed when a Version statement has invalid data in its version field. You do not have to force quit. Simple fix or delete the offending statement in the action editor window. The offending statement will typically be highlighted and with contain:

***** error description

This is the way it works for all actions. You can't save an action with errors.

Have you modified the Version statement which is the first in the action? I've just downloaded the action to a 'clean' Mac running version 6.10.3 and I can edit it and close the window without any errors?

Ignoring the background colour, the action should be as in the screenshot. If the action looks corrupted, delete it and install it again.