Version 8.2.4 (12409.12371)
Multi Field Editor Credits Functions
- The credit functions can be targetted to specific tracks.
- By default, the credit functions work on all selected files. When manually specifying credits it can be tedious to change the file selection so that only the appropriate files are modified. The new Track list field can be used to specify a list of tracks to be modified. When the field is empty, all selected files will be processed.
- The field can contain a list of files with track numbers and/or ranges of track numbers to be modified. eg: 5,6,10-13 means modifiy any selected files with a track number of 5, 6 or 10 through 13.
- You can also explicitly associate tracks with disc numbers. eg. 1:1,3-5,3:4,5 means modify any selected files on disc 1 with a track number of 1,3,4,5 and on disc 3 with a track number of 4 or 5. Disc associations persist until the next #: sequence is encountered.
- Note that all or no tracks must be specified with a disc number. ie. 3,2:5 is invalid.
- There is a new function named Resolve Non Standard Mappings. Any item which has the same role as a known credit (in the Combined Credits Editor's database), will be mapped to the field associated with the known credit. eg. a credit of Guitar in Involved people will be moved to Musician Credits. Note that after this function executes, both of Involved People and Musician Credits will be sorted.
Action Statement Changes
- The Involved People/Musician Credits Functions statement can specify the same disc/track list as in the Multi Field Editor's Credits panel. The functionality is enabled by setting the new Runtime track list option. The list is extracted from the IPMC Track Override named variable.
- The statement always returns an action test state of true, unless an error occurred when parsing IPMC Track Override.
FLAC/OGG Mappings
- A few new read only mappings have been added. If you want these changes, do a Yate>Import Built in Items>Import FLAC/OGG Mappings.
- MOVEMENT_TOTAL is a readonly mapping for Movement Count.
- MOVEMENTNUMBER and MOVEMENT_NO are readonly mappings for Movement Number.
- PARTOFACOMPILATION is a readonly mapping for Part of a Compilation.
Tahoe Beta
- Minor changes for Tahoe compatibility.
- All the previous icon machinations have been removed. The current icon is not drawn with a border by the Tahoe beta.
Bug Fixes
- The All Tags panel's Revert All to Menu, submenu items were not working.
- The Duplicate Artwork statement was not duplicating artwork within a track. ie. only one to many worked.
- In FLAC/OGG mappings, Involved People List Item MIXER=Mixer was not predefined as documented.
- The Multi Field Editor's Credits panel may not have been displaying the correct fields when the function was one of Move Credits, Move People or Sort Only.
Version 8.2.3 (12399.12371)
Regular Expression Extensions
- You can now specify that when inserting capture groups, all alphabetic characters should be converted to lower or upper case.
- A bookmark named Yate Regular Expression Extensions has been created in the Help>Search Yate Help panel.
Original Release Time and MPEG-4 Files
- Plex requires that Original Release Time in MPEG-4 files is encoded into a UDTI named originaldate. Further it may expect the year portion of the field encoded into a UDTI named originalyear.
- There is a new Settings - Audio - MPEG-4 option named Enable additional mappings for Original Release Time. When the setting is enabled, every time an MPEG-4 file is saved, the two UDTIs will be written or removed based on the Original Release Time field. Note that the default mapping or Roon's mapping is still written.
The Action Manager
- When searching the Grouping column, the search is now a contained search as opposed to an equality search. This makes more sense now that mutiple groupings are supported.
Bug Fix
- Creating a regular expression action on the Multi Field Editor's Replace display did not work if the replace template had a \1 sequence.
Version 8.2.2 (12388.12371)
The Discogs and MusicBrainz Wizards
- If a release has retained import settings, these settings will always be loaded when the wizard is started. While many users employ this mechanism to have retained per release settings, it may be problematic for those users who may inadvertantly import the settings.
- Both wizards already have the abilty to create and maintain named import setting configurations. Starting with this update if there is a retained import setting set named Autoload (case insensitive), it will be loaded whenever the wizard starts. ie. it will override any retained settings in the tracks.
Tahoe Beta Support
- The application icon will now be repaired whenever Yate starts. The previous method did not set the icon when the OS was updated and Yate was not.
- Droplets will now be created with Tahoe style icons. Note that previously created droplets will not be modified.
Version 8.2.1 (12383.12371)
The Multi Field Editor
- The Sort Form panel's Set Last Name, First Name function now allows you to selectively disable use of the following replacement sets: Sort Form Name Prefix, Sort Form Ignore Suffix.
Tahoe Beta 1
- Whenever Yate is started on a Tahoe beta and Yate's build number has changed, the application icon will automatically be changed to a Tahoe icon. The build number test ensures that the icon will be set again on a Yate update.
- Note, that the dock icon more than likely will not automatically update. Remove the application from the dock and add it again.
- The resource document Getting a Tahoe Style Icon for Yate has been updated.
Bug Fixes
- File to Tag processing was changing a Season or Episode of 0 to 1.
- The Episode ID field's Synthesize function was not working unless the file contained a video stream. It is possible to enable the use of Video fields even when no video stream is present.
- The Season and Episode fields did not differentiate between empty and 0.
- View>Credits Invalid for Roon did not always find all invalid credits. The error was formatting dependent.
- Renaming Credits via View>Credits Invalid for Roon or the Multi Field Editor could cause a crash depending on the credit/format composition.
Version 8.2 (12379.12371)
Binary Data Handling
- Binary data items can be present in plist files. In the past there was no means of manipulating the data in these items.
- There is a new Binary Data action statement which allows you to manipulate the data in Container Data items. This incldes the insertion/extraction of data items, strings in multiple encodings and integers and decimal numbers in a variety of widths and endian encodings.
- The same statement can read and write binary files in a non linear manner.
- Files can remain open until manually closed or automatically closed when an action or the Batch Processor terminates.
- The container statements Add Item to Container Array and Set Item in Container can now create empty data items.
- The Extract Data from Container statement can now return a data item's length.
Yate Album IDs
- Generated Yate Album IDs are now folder based as opposed to album based. This makes no difference for most people. It does however ensure that IDs are unique when generating an Album Database which contains multi disc albums separated into disc folders. Album Databases, which have one folder per row, have individual rows for disc folders.
The Database Viewer
- The context menu has a new Duplicate Row item.
- The context menu has a UID setting... item. Databases can be assigned a unique ID class which can be used to limit which actions can be displayed on the Actions menu. More information can be found in the viewer's online help.
Roon
- The repair functionality associated with the View Credits Invalid for Roon function, now repairs missing or redundant plurals.
The Action Manager
- An action can now be associated with multiple groupings. The context menu can now display an edit panel where multiple groupings can be entered. Groupings are separated by commas.
The Container Viewer
- When View Value is specified on a row containing a Data item it will be displayed as a hex dump in the Log Viewer (if it's < 10k).
Flac/Ogg mappings
- ENCODER SETTINGS has been added as a read only alias for Encoder Settings. This is an out of the box setting. If you want to import the mapping, do a Yate>Import Built in Items>Import FLAC/OGG Mappings.
Action Statement Changes
- The container statements Add Item to Container Array, Set Item in Container and Extract Data from Container now accept date as a source/destination.
- The container statements Add Item to Container Array and Set Item in Container can now create empty data items.
- The Add Item to Query Database statement can now specify an insert row as opposed to always appending.
- There is a new Binary Data statement.
- The Close/Save Query Database statement can now specify rows to be selected.
- There is a new statement named Compare Container which is used to test for equality or inequality between two container items.
- The Create Album Database and Create Track Database statements can now specify a UID to be associated with the database. UIDs can be used to establish a class which can be used to limit which actions can be displayed on the Database viewer's Actions menu. More information can be found in the viewer's online help.
- The Date Functions statement has a new Duration from ms.zzz function. The ms from Duration extraction function will now parse .zzz in all accepted soure modes.
- The Debug statement now displays ␦ for control and invalid characters. It now displays \- for tab characters when compressing the display display. Large data items are truncated after 5000 characters.
- The Extract Data from Container statement now returns a data item's length. When extracting a date, Yate's date format is returned.
- The Format Numeric statement has new hex(2), hex(4), hex(8), hex(16), decimal(1), decimal(2), decimal(3) and decimal(4) functions. The statement's menu has been divided into submenus for easier access.
- The Indexed Artwork statement has a new Compare Artwork function.
- The Is Action Defined statement can now test for the existence of inline actions.
- The Open Database for Querying statement now sets named variable db prefix-UID.
- The Preview statement can now be passed any valid path and not just a path to an audio file.
- The Prompt statement's Popup Window mode can now specify that the popup is centered on the display or displayed relative to the mouse pointer.
- The Remove Item in Query Database has been renamed to Remove Items in Query Database. The statement can now take a list of rows to be removed.
- The Rename Files statement can now override the settings encapsulated in the specified rename template. You can specify the name of an alternate template in named variable Rename Template Settings Override. The alternate template is used for the settings while the specified rename template provides the tokens.
- The Prompt from Container statement has a new boolean key named placeholderDisplayOnly. When set to true, the associated placeholder does not represent a default value ... only display text.
- The Stop Action and Post Process statement can now specify #Edit Panel as a token. A single edit panel can be specified, which will become current.
- The Substring statement's function menu has been rearranged for easier access.
- The Trim statement now includes a space character in the ASCII and Latin-1 sets.
Resource Actions
- Using the new Binary Data functionality, a Core Audio Suite has been implemented. The suite can analyze Core Audio Files and display their contained tags in a database. A workflow is supplied allowing you to apply the modified database back to the source files. Basically you can tag your Core Audio files.
- The Apple Music suite has been updated.
- The Sync Files suite has been updated.
- The Multi Field Editor Copy Extensions bundle has been updated.
- Rename templates for Plex have been supplied (in the Templates section).
macOS 26 (Tahoe) Support
- This release will run fine on beta 1 of macOS 26. Previous releases crashed on startup.
- For those of you running on the Tahoe beta (you're very brave), there is a process to change Yate's icon to look like a native Tahoe icon. On the web resources page there is a document describing the process.
- The document is also available in the Web Resources page's Documentation section.
- You can also create a link to the document by opening the Help>Search Yate Help panel; right click in the sidebar and select Create Resource Bookmarks.
Bug Fixes
- Actions>Yate Database IDs had a bad help link.
- The Action Importer was not disabled when actions were open.
- The Get Info statement had various UI display issues.
- Found an API where re-encoding from Cyrillic to ASCII could crash. These conversions are now protected.
- The Discogs Join override sequence was being accessed when Combine multiple value items into a single item was disabled. The Join override sequence is never used in conjunction with Involved People or Musician Credits.
- Popup help panels no longer display the mouse cursor in the center of the popup.
- While database columns could be set to use monospace fonts, resetting to proportional was not working.
- Previous releases would not run on the Tahoe beta.
- Prompt Popup Window's were immediately released.
Version 8.1.1 (12302.12298)
Album Databases and Yate Album IDs
- There have been ongoing issues with the updating of Album databases when separate disc folders are maintained. Largely this is due to the fact that the database when produced by the Create Database Utility resource action creates a database row for each disc folder.
- Attempts to rectify this issue in v8.1 did not go far enough.
- Starting with this release, Yate Album IDs are grouped on the containing folder as opposed to the Album field. This and other internal changes seems to fix the issues.
- The change of Yate Album ID generation will not affect users who do not maintain separate Disc subfolders and use an Album database. Further, if you used the Create Database Utility to create the database you will be fine unless you updated the database from loaded files in the UI.
- If at any time you manually created Yate Album IDs via Actions>Yate Database IDs for a single album spanning multiple folders, you will have to recreate the IDs.
- For affected users, it is strongly recommended that the Create Database Utility be used to recreate the album database and your track database if it contains Yate Album IDs. Make sure you update to v2.7 of the utility first.
- When running the Create Database Utility utility, ensure that Create Yate Album IDs is set to If Missing. This will validate the IDs across the entire database.
- An updated bookmark to the Updating Album Databases topic has been placed in Yate>Search Yate Help.
Menu Changes
- The File>Database Functions menu hase been merged into the File>Database menu.
Action Statement Changes
- The Prompt from Container statement has a new key named placeholderDisplayOnly. The key is used to imply that a row's placeholder always represents an empty value and should not be retained when placeholders are saved to named variables.
- The Rename Files statement now has the ability to override the settings (as opposed to the tokens) in the supplied rename template. This is largely so that actions can be written to enforce certain settings. This avoids having to document required settings for rename template to be used with supplied actions. More than likely this feature will not be used other than possibly in actions we distribute.
Resource Actions
- There is a new Generic Text Exporter action which exports metadata for individual files based on a rename template.
- The Create Database Utility has been updated to v2.7. This version validates IDs when testing for missing IDs.
Version 8.1 (12290.12280)
Settings
- Both of the Discogs and MusicBrainz General panels have a new Copy Mood to Genre setting. The following three settings, if enabled, on each of the panels are applied in the following order:
- Merge genres into mood
- Copy mood to genre
- Ignore all but the first genre
- To avoid confusion the Discogs, MusicBrainz and AcoustID settings now disable the Join sequence if Combine multiple value items into a single value is not enabled.
Debugging Actions
- The Actions menu has a new submenu named Debug.
- Pause Running Action, (formerly Debug), stops an executing action and displays a Debug panel.
- Typically breakpoints in an action are only enabled when an action is run from an editor window or when Pause Running Action is selected. There may be other times when you want breakpoints to be initially enabled. For example when debugging an action running in the Batch Processor. Enabling Always Enable Breakpoints will cause breakpoints to be initially enabled whenever an action is run.
Application menus
- Menu items which toggle no longer display green or red icons. They now display a ✓ or x or the title changes to indicate the function to be performed.
- The File Properties topic has been added to the Help>Quick Reference menu.
The Main Window's Default Sort
- The default sort is the sort applied when loading files and the Open Mode is Album. This is initially
- Album ascending
- Disk ascending
- Track ascending
- Path ascending
- The above sort is now called the Standard Sort.
- You can set alternate default sorts via the Sort submenu on the main window's column header. This includes named sorts that you may have created.
- A topic named Main Window Sorting will have ben created in the Search Yate Help panel's bookmarks.
Credits Database
- The Credits database was updated to the latest Discogs, MusicBrainz and Roon published information.
The Container Viewer
- There is a new disclosure button to the right of the search bar which displays a menu allowing you to constrain where searches are to occur.
- All, names or values is displayed to indicate the set search location.
The Action Manager
- You can now sort folders based on the grouping or icon.
- The Log Action & Debug Usage context menu item has been removed.
- You can accumulate and display usage information by selecting any number of folders and actions and then selecting the Log Usage Information or Display Usage Information context menu items. Information will be displayed in the Log Viewer or the Container Viewer. Note that the displayed information will not reflect possible changes in actions currently being edited. The following information will be displayed:
- For each selected action:
- A list of actions which are called by the action
- A list of actions calling the action
- Display Usage Information only
- A list of named variables referenced by the action
- A list of track variables referenced by the action
- A List of containers referenced by the action
- An entry indicating that the action contains a Debug statement or any statement marked as being a debug statement.
- For every named variable a list of actions which references it.
- For every track variable, a list of actions which references it.
- For every container, a list of actions which references it.
- A list of all actions which contain a Debug statement or any statement marked as being a debug statement.
Action Editor Windows
- The ability to open every action contained in a folder at once has been removed.
- The Display Named Variable Usage context menu item has been removed. Use the Log Usage Information or Display Usage Information function in the Action Manager.
Action Statement Changes
- The Duplicate Artwork statement can now copy an image from any loaded file to any other file.
- Many resource actions use discardable databases. This means that any changes made to the window size will not be retained as the associated plist (sidecar) file is removed when the database is discarded. A workaround has been implemented and is documented in the Open Database statement.
- The SoundCheck statement has a new option which specifes that all options are taken from Settings-ReplayGain.
Resource Action Updates
- A number of resource actions have been updated including major changes to the Apple Music Suite. It has new actions to search for individual tracks by searching and extracting. The suite's profile manager now supports the duplication of an existing profile.
Bug Fixes
- The Involved People / Musician Credits action statement had a few display issues.
- The Combined Credits Functions action statement was only displaying its name in an action editor.
- The Prompt from Container statement was not immediately clearing a state field when a row was disabled by a different row.
- View>Validation Errors was displaying some irrelevant information for multi item fields.
- The false label in Settings - Actions was misplaced.
- The Is Database Open and Preview statements were showing a bogus control
- The Open Database statement not properly initializing the Disable Close in UI control when displaying.
- The Open Database statement was not automatically unescaping named variables when inserted into the alternate help source field.
- If a Prompt from Container statement was terminated by a Cancel button with an Exit mode, the panel's settings could still be saved.
- The Test Run Context statement flipped messages for Not Started Action and Started Action File. Only the text was incorrect. The function was performed correctly.
- v8.0 messed up the use of keyboard shortcuts with the Actions>Copy Metadata submenu. Any shortcuts to this menu will have to be respecified.
- The Update Database functionality was not propertly handling the situation of: Album Database, separate disc folders and Yate Album IDs present. A topic named Updating Album Databases will have ben created in the Search Yate Help panel's bookmarks.
- The Get Info statement's List of Action Runtime Settings Sets function would not always include a set created while the action was running.
- The Save Variables and Restore Variables statements were not logging their track variable usage.
Version 8.0.1.1 (12254.12246)
Bug Fix
- The Add/Replace button in the Open Mode toolbar item, (using Yate Classic icons on Sequoia and Sonoma), was not changing to the appropriate icon when clicked.
Version 8.0.1 (12253.12246)
Application Icons
- There is a new application icon more in line with current OS versions.
The View Menu
- The View menu has a new Auto Attempt Repair item which allows you to configure the Credits Invalid for Roon menu item's method of attempting to automatically repair invalid credits. The values are Never, Prompt and Always.
Action Changes
- The Get Info statement has new Actions by Grouping to Container and Actions by Icon to Container functions.
- The Log statement has a new Credits Invalid for Roon function.
Automatic Column Sizing
- v8.0 flipped the default for File List - Auto size column widths after loading files to enabled. Unfortunately this enabled the setting for everyone.
- The default for the setting has been restored to disabled. This will not revert an existing setting of enabled.
- This release will prompt once if you have the setting enabled. The prompt will let you disable the setting if desired. You can always change the setting manually in Settings - File List.
Bug Fixes
- Stepping while debugging an action run in the Batch Processor might beep.
- The Copy Metadata Between Files statement with a mode of Fields in Default UI Settings, could crash if run through the Batch Processor.
- ⌘Q with confirmation on macOS 10.10 sometimes failed to quit.
Version 8.0 (12242.12200)
Toolbar Icons
- A new set of monochromatic minimalistic toolbar icons has been implemented.
- There is a new option in Settings-File List which allows you select the following.
- Mac Monochrome
- A set of minimalistic monochrome icons. This value is initially selected.
- [ Mac Monochrome ]
- Same as Mac Monochrome but displays a border when you hover over an active toolbar icon. This only works on macOS Catalina (10.15) or later. On other versions of the OS, the border is not displayed. Note that the border causes additional spacing to be present between icons. Further, it may change the size of the icons.
- Yate Classic
- A set of coloured icons...the original Yate classic set
- On older versions of macOS, the new icons look better when Use Small Size is selected.
Toolbar Icon Text
- The text (potentially) displayed on a toolbar icon could be limited in the past by enclosing a portion of the action's name in [ ].
- This can be problematic with resource based actions as the name change could mess up the Action Updater.
- Starting with this release when you do a Set as Toolbar Action from the Action Manager's context menu, you will select an action icon number as before. Immediately after selecting the icon number, a panel will be displayed which allows you specify the icon text as follows:
- Default
- The text will be Run action #.
- Action name
- The text will be the name of the action.
- Specified
- The text will be whatever you specify.
- You can still use the [ ] method but it is now deprecated.
- On the same panel you can specify a tooltip which overrides a Tooltip statement, if present, in the action.
- You can also supply an alternate icon for the item. This is done as in Settings-File List-Toolbar Action Icons but only a single icon can be changed.
- Note that post configuring the above properties, they may be edited via the Edit Toolbar Icon Attributes context menu item.
Search Yate Help
- You can now select and delete multiple bookmarks at a time.
- You can use the bookmarks context menu to create bookmarks to the web resources page document items. Note that bookmarks will only be created for those items which are not built in to the application.
- Selected or all bookmarks can be exported via the bookmarks context menu.
- Bookmarks can be imported via the bookmarks context menu.
- The search panel now has an 🅘 button which displays the Help>Quick Reference menu.
- There is a new main window toolbar item to display the window.
- When bookmarks are added by an application update, they will be prefixed with the version number. These version numbers will automatically be removed from the bookmark names on the next update. The bookmarks will remain ... only the version prefix is removed.
Invalid Text Identification
- Main window fields which contain invalid characters are displayed with blue text. However, this is not sufficient if a field only contains non displaying invalid characters. Starting with this version, the label associated with a field will displayed in red text if the field contains invalid characters.
- The built in Lyrics field does not have a label in order to maximize the display area. If this field contains invalid characters, a red exclamation mark indicator will appear beneath the field's associated function button.
- The field's context menu Why is the text Blue and Label Red? item, will now display the text with invalid characters marked by a question mark in a blue diamond character.
- The field's context menu item Yate Transformations>Remove Invalid Characters can be used to remove the invalid characters.
- View>Validation Errors identifies all fields which contain invalid characters.
The Batch Processor
- Yate treats all disk access as transparent. A disk being internal, attached or network based make no difference.
- When using network based storage and the connection is lost, the Batch Processor would still process every folder already identified and return an error.
- Starting with this release whenever an error is detected which might be due to a disconnect, an alert will be displayed in the UI. You can choose to Continue, Cancel or Ignore for All.
- If you want to always ignore the reporting in the UI, you can set the new Settings-Actions>General - Do not report potential drive/network errors in the UI when batch processing option.
The Chapter Editor
- The Chapter Editor has been modified to always display the value to be written as opposed to empty if a chapter name has not been modified. This makes it easier to modify existing values.
- A green/red change indicator column is now displayed.
- You can now set a chapter name completely to empty.
- Various clearing and revert functions are now available on the table's context menu.
- The context menu can now be used to rename chapters using a configurable template.
- The Revert to button has been removed as it is now redundant and has been replaced by a Cancel button.
- The identifier column can now be a compressed path where common leading path components are not displayed.
- There is a new import/export menu which contains various means of importing and exporting chapters to text files.
Disabling Chapters in MPEG-4 Files
- Chapters can be disabled, not removed, in MPEG-4 files. The chapter names will no longer appear in players. The function is performed via File>Save Selected Files>Save if Has Chapters Disabling Them. Any selected file which contains chapters will have them disabled.
- The function can also be performed by the Save action statement.
The Custom Panel Editor
- The insertion context menu has been reorganized to make it easier to access various components and to group all similar named items dynamically into submenus (based on availability).
- Horizontal separator lines can be inserted spanning a single column or two columns.
- All custom panels can be exported at once, via the Export All item on the Import/Export menu.
- When clicking on an Unused grid item to display the selector menu, the item will be displayed as green until the menu is dismissed.
- Entirely empty grid rows (ie two empty columns) can be dragged above or below locations in the grid. When the Shift key is pressed, you are moving below otherwise above. When dragging, both of the Unused items on the row will be displayed as green. The destination of the drop is chosen as follows:
- Terminate the drop anywhere in a used grid item
- You are moving above or below the selected item.
- Terminate the drop on an empty grid item adjacent to an occupied grid item
- You are effectively choosing the adjacent item as the destination.
- Terminate the drop on an entirely empty row
- You are moving above or below the empty row.
- The [ ] method of cropping an action's name on an action button is now deprecated. You can use the Display Name field which is a better more powerful solution.
- The Import menu has a new submenu to install custom fields and an edit panel for Audirvana and Roon. The content is automatically downloaded from the web resources page.
Involved People, Musician Credits and Custom Fields
- Involved People and Musican Credits are used to store credits which do not map to standard fields such as Producer, etc.
- You can now elect to move credits to custom fields which are defined to be a credit when the credit name in Involved People or Musican Credits is the same as the name of the custom field (case insensitive). For example if you have a custom field named Engineer, you can have all credits of the same name automatically moved to the custom field.
- This can be done when importing from Discogs or Musicbrainz and manually from either field's function button or the Multi Field Editor's Credits panel.
- The same functionality can be performed by the Involved People/Musician Credits Functions action statement.
The Custom Field Editor
- The Choose commonly used mappings popup menu in the Custom Field Editor, now groups all common credits on a Credits submenu.
MusicBrainz Settings
- There is a new Settings - MusicBrainz - General setting named: Percentage of tracks which must be classical for identification. Previously this was always 50%. You can now set other percentages and Unlimited.
Discogs / MusicBrainz Settings
- Discogs and MusicBrainz General settings have a new item named Prefer custom fields to Involved People and Musician Credits. The setting enables the automatic moving of imported credits to custom fields defined as a credit, where possible. Note that while the setting appears on both setting panels, it is a single setting.
- The Auto Add files setting now only adds files. It will not remove files from the initial selection.
Discogs / MusicBrainz Wizards
- When mapping files, a popup window displaying Mapping ... may be displayed if the process may take a more than a few seconds. The mapping process for large box sets can take a while. Simply wait it out.
- When files previously run through the wizards have had the appropriated IDs imported, mapping is exponentially faster.
Actions>Copy Metadata
- The submenu and configuration panel has been changed to allow the saving and use of named configuration sets. A bookmark named v8.0 Copy Metadata has been created in the Search Yate Help panel.
- The configuration panel's UDTI exclusion list can now handle exclusions and inclusions for Comments, UDTIs and UD URLs. The formatting has changed considerably and is backwards compatible. A bookmark named v8.0 Multi Item Transfer Rules has been created in the Search Yate Help panel.
The Multi Field Editor
- The Replace function supports \1 sequences in the replace with pattern.
- The Credits panel has a new function to move credits to named variables defined as a credit.
The Artwork Viewer
- If you drag in a folder with the Shift key down, the folder's icon will be displayed.
- You can now use the File>Save and File>Save As menu items to save the image. Previously this could only be done from the context menu.
The Database Viewer
- The output of the query process now lists the number of unique items.
- A database viewer's help button can be configured to display alternate help when the database is opened by an Open Database statement. When a database is automatically opened by the Batch Processor (after a Create Album Database or Create Track Database statement), no Open Database statement is used. For this reason, whenever a database is opened directly or indirectly by an action, and alternate help has not been provided, named variable Database Help-dbname is examined. If the variable is not empty it will be used as the alternate help. dbname is the database's last path component without the filename extension.
Export Sets
- When creating a new Export Set, there is a new preset for a minimum set for the track database Look for Duplicates functionality.
The View Menu
- The Validation Errors functionality has been completely rewritten to perform far better error identification.
- Previously the Credits Invalid for Roon function returned valid Roon items which had Roon aliases. From this point on no valid items are returned. The format of the produced results has been updated.
FLAC Mappings
- The Catalog Number field has a new alternate r/o mapping CATALOG NUMBER.
- The File Type field has a new alternate mapping FILE TYPE.
- These new mappings can be imported by Yate>Import Built in Items>Import FLAC/OGG Mappings.
The Video Definition Field
- 4K is now supported.
- If the video definition information is not explicitly set in the file, the Settings - Video - Auto set Video Definition field setting will set the field based on the video's xy dimensions.
The Droplet Creation Panel
- You can now manually enter the name of an action.
- You can now select an action from a flat list of names or the Action Manager's current display (as in previous versions).
Settings - Audio Application Presets
- When Audirvana or Roon is selected, you are given the option of downloading and installing custom fields and an appropriate edit panel.
Player Interfaces
- You can now download and unzip the player interfaces to your Downloads folder via the File>Open Track Playing In>Download Player Interfaces menu item.
Importing from Archives
- When doing a File>Import/Export>Import from Archives>Specified Archive, it can now be exponentially faster if there are a lot of filename matches.
Action Statement Changes
Insert Sequential Numbers
- The \1 escape sequence can be redirected to a track variable as opposed to the Integer to Insert named variable.
- This is done by setting the Integer to Insert named variable to =# where number is 0-15 representing a track variable.
- This expanded mechanism allows you to insert integers on a per file basis making use of the parallelism of stepwise mode.
The Roon Edit Panel
- In case you didn't notice, The Roon+ edit panel was recently updated with the addition of a boolean Live field.
- The previously available panels have been coalesced into a single panel named Roon.
- The panel can be installed over an existing Roon+ panel directly from the Import menu in the Custom Panel Editor.
Resource Actions
- There is a new action named Repair Credits Invalid for Roon.
- The Apple Music suite has new actions to search for individual tracks.
- The Open Opus dataset was previously distributed as a database. As the content is updated from time to time, it is now distributed as an action which generates the database form the remote content.
- The following actions/suites have also been updated: Artist Reference Database, Classical Metadata from Title, m3u Suite, Renumber Chapters, Yate and the P Word.
Resource Documentation
- The Yate and the P Word document has been updated.
- There is a new document named Configuring Yate's Appearance.
Detached Edit Panels
- There were many bugs in the detached edit panels implementation released in v7.0
- Most functions which cause a sheet to be displayed in the main window will now be displayed on the detached edit panels window if it has the focus.
- When either the main window or the detached edit panels window has a displayed sheet, the other window will be completely disabled.
Bug Fixes
- The Decompose Title into Classical Metadata statement was displaying a meaningless unused control.
- Various bugs related to a detached edit panel window.
- The multi line JSON editor panel's insertion menu was missing an item for the Configuration icon.
- The Custom Panel Editor was not always re-instating associated items when an item was deleted. This may not have been evident as all was fine the next time a panel was displayed.
- The Apple App association in the Action Manager was being set as an Artwork association. In order to make it easier to identify, the Apple App Association is now displayed as ⌘.
- Dragging to the main window, Batch Processor, an artwork viewer and File>Open Path in Clipboard now handles any combination of symlinks and aliases.
- At least one audio file converter is mangling the Involved People field when converting from FLAC to M4A. This could result in long load times and possibly even a hang when loading the files. When this is detected, the issue is repaired.
- The Suppress opening the main window setting when a droplet is created was only working if Yate was already running.
- When simple field items were deleted from the All Tags editing panel, changes to other edit panels were not made until the file selection changed.
- Search Yate Help bookmarks were not being exported as expected.
- The File Path Manipulation statement was not logging all variable usage.
- Stepping was not reliable when debugging an action running through the Batch Processor.
- The Build Component List statement was not properly handling the multi line edit control.
Latest Release Notes