Descriptions for Description
Name: Yate for Mac
Release Date: 02 Jul 2016
Mac Platform: Intel
OS version:OS X 10.6 or later
Processor type(s) & speed: 64-bit
Web Site: http://2manyrobots.com/yate/
Yate was developed for people who want complete control over their tagging experience. Supports audio in AIFF, DFF, DSF, FLAC, M4A, M4B, MP3, MP4, STEM.MP4 and WAV files. Supports video in M4V and MP4.
Yate has a long list of features; most importantly, an innovative scripting system called actions. Actions can be used to update all of an album's tags with a single operation. Yate also supports integration with AcouticBrainz, AcoustID, Beatport, Discogs, iTunes and MusicBrainz. All changes can be easily reverted and individual changes can be undone in any order. Whether you want to automatically or manually tag your files, Yate can do it all!
What's New in Version 3.13:
Action Test State Changes
・Previously every action had its own unique test state. This goes back to the early days of action processing in Yate when there were no flow control statements other than the Test statement. The current implementation makes it impossible to return a true or false value in the test state from a called action. The behaviour has been changed such that there is now a single test state for the entire action mechanism. The value of the test state always reflects the last time it was set. With one exception, the test state is only automatically set when action processing first starts from the UI or whenever a new folder is about to be processed by the Batch Processor. In these cases the test state is set to false.
・The exception is the Load and Run statement. After executing a Load and Run statement the test state reflects the success or failure of the track loading, as it always did. The test state from the executed action is not returned.
・There is a new option in Preferences-Actions where you can return to the earlier action test state mechanism. This may be removed at a later date.
・The Preferences statement now allows you to set the behaviour either way at runtime. This also, may be removed at a later date.
Stem File Support
・Stem file metadata can now be viewed
・In the Snapshot Editor
・By double clicking in an Audio Information panel
・Via Log>Raw Data
・There is now an Advanced Filter panel. Complex filters can be defined and saved.
・Relative date testing is possible.
・Saved filters may be directly accessed via the viewer window's context menu.
・Database rows in Album and Track databases can now be dragged outside the database. The associated files or folders will be treated the same as if dragged from the Finder. Dragging to the Finder will copy, dragging to Yate will open, dragging to iTunes will add to the destination (library and/or playlist).
・You can now select any combination of actions and folders when doing a Smart Export. Note that the folder structure is not preserved when doing a Smart Export.
Action Editor Windows
・You can now Show and Hide line numbers in Action Editor windows via the context menu. This is to facilitate the location of items described by line number in certain error messages.
Action Pending Window, Prompts, Batch Processor logged messages, Action Error Messages
・With few exceptions, wherever an executing statement and action is described ... the action name is now displayed in one of the following ways:
・When executing a non-inline action:action name (line number)
・when executing an inline action:action name (line number in containing action)
・All preferences associated with Action Editor windows now take effect immediately.
・You can elect to display a vertical grid line between line numbers and statements in Action Editor windows.
・You can now change the labels on the Ask statement's True and False buttons.
・You can choose the Action Test State mode.
・You can now export the Classification, Hi Def Video, Network Name, Show Description and Video Description fields.
・The importer now supports a "run after import" action.
・Yet another tweak to the Discogs track separator algorithm. Note that this is the algorithm used to detect tracks and discs in the metadata returned by the API, not the algorithm which matches files to the metadata. Sub tracks are now better recognized.
・Comment statements are now displayed as ' text to make better use of display space.
・The Run Context Test statement now supports the cancelling of action processing if the specified context is not supported.
・The Access Query Database Cell statement has been renamed Access Query Database as row and column access options have been added.
・The Create Album Database and Create Track Database statements have a new option to preserve the contents of an existing sidecar file. See the online help for more information.
・The Prompt for File or Folder statement now optionally supports the selection of multiple items and allows the selection of both files and folders.
・The Regular Expression statement can now be used to return matched patterns and matched locations as well as replacing text.
・The Preferences statement supports the run time changing of the Ask Statements True and False button labels. It also lets you choose the Action Test State Mode.
・The Set Action Test State from Variable statement is now called Set Action Test State. The statement now supports the explicit setting of the test state to True or False as well as to the contents of a variable or named variable.
・The Dump Variables statement can now display the call stack. This may assist in the debugging of complicated actions. Each line in the displayed call stack represents a statement calling an action which has not yet terminated.
・The List Item at Index statement will process each file individually, when run stepwise, if the source and destination are not named variables.
・The Set List Index statement will process each file individually, when run stepwise, if the list is not in a named variable.
・Reduced spurious redraws in the File Browser when displaying a large folder.
・The 'db' field in database files did not support (B) for Beatport.
・The Log statement was failing when a path was not specified and it was running in the Batch Processor.
・The Build List statement was needlessly disabling some field types from the 'source' field.
・Actions exported via Smart Export were not preserving the date/time modified information.
・The Preferences statement was being ignored when overriding the Unique Value Mode. Regression introduced in v3.12.
・It turns out that there were workarounds to allow inline actions to execute recursively.
・The Run External Script statement's Ignore errors option was being reset the next time the action was opened (not run).