Yate Release Notes

Version 6.12 (11260.112556)

      Running Actions from the Multi Field Editor and from Function Buttons

• We've supplied many simple text manipulation actions over the years which were essentially extensions to the Multi Field Editor. In the future, this type of action will be supplied to be run from the Multi Field Editor.
• The Multi Field Editor is now extensible via actions which can extract which fields are currently selected.
• There is a new Multi Field Editor panel named Actions which lists appropriate actions and allows you to run them.
• An action is denoted to be used in the Multi Field Editor by setting the Association (formerly Menu) column in the Action Manager to M.
• Fields which have function buttons with a Multi Field Editor... item will now have a Multi Field Editor Actions submenu. Selecting an action from the submenu is identical to running it from the Multi Field Editor with the associated field. To the action, it looks as if it was run from the Multi Field Editor. Note that the selected fields in the Multi Field Editor will not be modified and the Multi Field Editor will not be displayed if it is closed.
• The Test Run Context statement can now test if an action was started from the Multi Field Editor, or a function button.
• Named variable Run from Multi Field Editor will be set to 1 if the action was run from the Multi Field Editor or a function button.
• The set of effective fields selected in the Multi Field Editor can be extracted by an Extract Preference Set with a Supplied Fields Set function. Note that when an action is launched from a function button, the button's associated field will be extracted.
• The Multi Field Editor's Actions panel enables the following from its context menu.
  • A listed action's description, if any, can be displayed. Hitting the spacebar has the same effect.
  • A listed action's resource help, if any, can be displayed.
  • A listed action can be opened for editing.
  • You can open and position the Action Manager to a listed action.
• More information can be found by doing a Search Yate Help with a topic name of Running Actions from the Multi Field Editor.
• A set of sample extensions named Multi Field Editor Bundle 1 can be downloaded from the Actions section of the resources web page. If you display the new actions panel, you will be asked if you want to install the bundle.

      Action Manager

• New action and folder icons under a Functions sub menu. The menu includes icons for all wizards, importers and associations.
• The Menu column has been renamed Association.

      Debugging Actions

• The Debug statement's runtime configuration panel has been enhanced.
• You can now specify fields to be displayed at runtime.
• You can now specify UDTIs to be displayed at runtime.
• You can now specify that Action Runtime Settings should be displayed at runtime.
• Settings now persist forever.
• You can save settings which can later be restored.

      Loved/Disliked

• By popular demand the order of values when clicking on the Loved checkbox is now ... (not Set), Loved then Disliked.
• There is a new Preferences - File List setting named Disable Disliked in the Loved checkbox. When enabled, the checkbox will only cycle between ... (not Set) and Loved when clicked. If a track is marked as Disliked, it will still display correctly. The setting only controls what happens when you click on the control.

      Yate Transformations

• The Sort and Sort Excluding First transformations now remove duplicates.

      Markup Sequences

• There is now a Link markup sequence. Do a Help>Quick Reference>Prompt Markup Sequences for more information.

      Preferences

• Again ... by popular demand ... all tables display item counts.

      Rename Template Editor

• There is a new IfVariousArtists token. This token is used to test if the file's Album Artist field contains Various Artists (case insensitive). If the Album Artist field contains multiple items separated by the multi value delimiter, true will be returned as long as one of the items is Various Artists.

      Action Runtime Settings

• The default action runtime settings set was named Action Runtime Settings for historic reasons. The entire benefit of the current implementation is that separate sets can be maintained for each action. For this reason the default action runtime settings set is now named the name of the initially run action.

      Escape Sequences

• The \at escape sequence used to return the text specified on a Version statement. It now returns the descriptive text of the action. An action's description is the first non empty content in a Comment, Force Grouped, Tooltip or Version statement. A search for a description is terminated at the first enabled statement which is not one of the preceding statements or an Empty Line or Constrain Execution to a Single File statement.
• The \a2 escape sequence returns the descriptive text of the initial action. \at returns the descriptive text of the current action.
• The \a3 escape sequence returns the version number of the initial action. \av returns the version number of the current action.

      Action Statement Changes

• The Comment, Force Grouped, Tooltip and Version statement's text fields now support the inclusion of markup sequences from the context menu.
• The Copy Non Audio Files statement
  • The statement no longer returns an error if the source and destination folders are the same. This is to be consistent with the Move and Copy Files statements.
  • The statement now supports escape sequence handling in all text fields.
• The Enumerate Fields and Extensions statement
  • The statement has been renamed Enumerate Fields, Roles and Extensions.
  • There is an additional enumeration named Formatted Fields.
  • There is an additional enumeration named Plain Text Fields.
  • There is a new function which allows you to display a filtered list of credit roles as displayed in the Combined Credits Manager.
  • There is a new function which displays all fields mapped to preference lists.
• The Extract Preference Set statement has a new function named Supplied Fields Set which returns the effective set of fields supportd by the action. See the online help for more infoemation.
• The Fill Lists statement can now specify the source fields in a named variable.
• The Is Query Database Open statement now sets named variable Query Database Modified to indicate if the query database has been modified.
• The Map Action Runtime Settings statement now implies the name of the initial action if no set is specified.
• The Move statement supports the ability to change the move to a copy at runtime. If the Allow runtime override setting is enabled and named variable Override Move to Copy is true, the override will occur.
• The Move Non Audio statement
  • The statement supports the ability to change the move to a copy at runtime. If the Allow runtime override setting is enabled and named variable Override Move to Copy is true, the override will occur.
  • The statement can now specify the same track variable for the source and destination. This is to make it easier to rename non audio files.
  • The statement now supports escape sequence handling in all text fields.
• All Prompt statements other than Prompt from Container will now display the resource help if the Option key is pressed when clicking on a help button.
• The Prompt statement now has a Popup Window mode. It displays the specified prompt in a popup window. The action is resumed as soon as the window is dismissed by clicking outside the window or by hitting the escape key.
• The Prompt for Fields statement can now specify that exactly one field be selected.
• New Prompt for Text statements no longer create a Multi Line Editor button by default.
• Query Database statements now force all keys to be Unicode UNFC to avoid issues when copying files and updating databases between drives using a different name encoding.
• The Re-Encode statement can now re-encode to Unicode UNFD.
• The Scanner statement has new functions:
  • Scan Unsigned Integer
  • Scan Unsigned Integer or Hexadecimal.
• New statement named Sort Container Array. The statement sorts an array component by string items or at a supplied item in an object.
• The Sort Form statement has two new convenience functions.
  • Sort Multiple Items treats the source as a list delimited by the multi value delimiter. Leading and trailing spaces, empty items and duplicates are removed and the list is sorted in ascending order.
  • Sort Multiple Items Excluding First is the same except that the first list item remains first.
• The Standardize on List Items statement can now specify the source fields in a named variable.
• New statement named Supported Fields. This statement provides some guidance to the Multi Field Editor to determine if the specified fields are appropriate for an action, or function button. The statement is optional. If not specified, the Multi Field Editor assumes valid for all fields.
• The Test Run Context statement can now test if an action was started from the Multi Field Editor, or a function button.

      Other Multi Field Editor Changes

• The Sort Form function supports the new modes added to the Sort Form action statement.

      Bug Fixes

• If you had an old Mac (and required the OM version) and were running a patched version of macOS >= 10.13, the v6.11 update process looped.
• The Append to Values menu item on the function button to the left of the Involved People and Musician Credits fields, displayed a text field which accepted rich text. This could look a little weird when pasting text from a browser.
• The Is Database Open statement's documentation did not describe how named variable Database Status was set.
• The main window's db column was erroneously showing some files as having Beatport track IDs. The column's display logic no longer looks for IDs in filenames, only in the well defined places. The Beatport Importer will still attempt to extract the IDs from filenames if they cannot be found in a well defined location. ie. only the display has changed.
• After inserting a regular expression sequence [^set] from the context menu, ^se was selected as opposed to set.
• Doing a Find in an action editor window did not always provide access to all warnings.
• The Enumerate Fields and Extensions statements Numeric Fields function was not returning Playlist Delay or Rating.
• The Enumerate Fields and Extensions statements URL fields function was not returning Commercial Information Webpage or Official Artist/Performer Webpage.
• The Test Run Context statement's Started Action modes were not always working correctly.
• The Prompt statement's Flush User Log and Ignore if Batch settings were incorrectly entwined. If you are using any of these modes, you should open the action, check the value and resave it.
• The Set User Defined Text Item statement was not displaying 'only if empty' if the value was zero. Only the statement's display was incorrect.
• The Set User Defined Text Item statement was trimming leading and trailing spaces in the name at runtime. While this is more than likely benign, it is not correct.
• You could not delete a Rating on the All Tags editing panel.
• The Container Viewer's Copy Name/Index context menu item was using the selected as opposed to the clicked row.
• When an action finished, the last mapped Action Runtime Setting set was not unmapped.