Version 6.14 (11441.11431)
- AIFF files consist of a sequence of chunks. It is perfectly valid to have a chunk size of zero. However the Music application seems to stop reading data from files when a zero length chunk is encountered. This can potentially lead to a file being tagged but the metadata will not appear in the Music application. The Preferences - Audio - Common - Remove zero length chunks (AIFF only) setting will remove these items whenever a file is written.
- If for any reason you have a workflow where you do not want to link files dragged into Yate from an Apple app, you can do so by setting the Preferences - Apple Apps - General - Do not link when dragging from an Apple app option. When the option is enabled, dragging from an Apple app is treated the same as when dragging from the Finder. Note that when the option is set, no auto importing will occur.
- Yate v6.13.2 introduced the ability to display a submenu when selecting an action from a menu. The submenu allows you to edit, locate or run the selected action. The submenu was displayed if the Option key was depressed. It seems as if this interfered with some users' keyboard shortcuts. Preferences - General - Advanced has a new setting which allows you to specify any modifier sequence to display the submenu.
- In the Discogs and MusicBrainz preference panels you can specify a track database. If you enable Use track database and leave the path empty, the default track database specified in Preferences - Database will be used.
- All settings which are related to the editing state have been moved to a new preference section named Editing State. If this was not done the settings would have been on three different panels.
- The File List Preserve the Editing state setting has been renamed to Update the Editing state when selecting files. This flips the previous value but retains the intent. New installs have the setting disabled as changing the editing state on selection changes, limits some reversion functionality.
- There is a new setting to automatically copy the initial state to the editing state immediately before a file is saved. This gives you a recoverable set of values. You can select to never do it; do it on the first save; or on all saves.
- The filename field in the M3U preference panel can now contain escape sequences to insert metadata. These sequences are available on the field's context menu. Note that the escape sequences are only evaluated once per folder.
- It can be difficult to determine if a filename or path component is too long for an underlying filesystem. The new Preferences - Rename - Settings - Automatically truncate path components setting attempts to remove some of the burden. When set, filenames and path components will be reduced to fit within 255 bytes based on the system's representation. Note that due to encodings, a truncated component may be less than 255 characters. Bytes were chosen as a unit as APFS is based on UTF8 characters, HFS+ is based on UTF16 characters, etc. The setting errs on the side of caution. It is possible that extra characters can be manually entered when editing a path component in the Finder. This setting is also used by the following action statements:
- Copy Files
- Create Symbolic Links
- Export Metadata
- Import Metadata
- Import Metadata from Audio File
- You can now include a Category token in a rename template which maps to the field of the same name.
- The IfLength and Truncate tokens now always work on a number of characters as opposed to UTF16 units. In order not to break existing templates, negative lengths will be negated. eg. a length of -5 will be treated as if it was 5.
The Editing State
- The editing state is now always preserved when saving or refreshing a file. This used to depend on the value of the now renamed Preferences - File List - Preserve Editing state setting.
Action Statement Changes
- The Preferences statement can override the new Automatically truncate path components setting.
- The Preferences statement can override the new Copy the Initial state to the Editing state when saving files setting.
- The Truncate statement now always works on a number of characters as opposed to UTF16 units. In order not to break existing actions, negative lengths will be negated. eg. a length of -5 will be treated as if it was 5.
- There is a new Exchange Initial and Editing States statement.
- There is a new Copy Initial State to Editing State statement.
- The runtime debug configuration panel has a new Auto display Debug statement setting. When enabled, an action editor window containing the calling Debug statement will be opened and the Debug statement will be selected, whenever the debug panel is opened.
- The following menus (and their possible main window context menu analogs) now support a modifier key sequence to open a function submenu.
- Actions>User Defined
- Actions>Actions by Icon
- Actions>Actions by Grouping
- Edit>File to Tag>Actions
- Artwork>Search for Artwork>Actions
- Artwork>Search for Artwork>User Defined
- Artwork>Search for Artwork>Default Search
- database context menu>Run Action
- The initial modifier sequence is the Option key which was used for the action submenus introduced in v6.13.2. The sequence can be configured via Preferences - General - Advanced - Modifiers to display function submenus.
- The function submenu can contain items to edit the item in a preference template editor or an action editor window; locate an item Preferences or in the Action Manager; set or clear a default artwork search template; apply a template or run an action.
- Any other previous modifier sequences to perform the same functions are no longer used.
Other Menu Changes
- The Edit menu has new Exchange Initial and Current States and Copy Initial State to Editing State menu items.
- The MusicBrainz Release Type data was constructed using a slash (/) as a delimiter to separate multiple types with the primary always being first. A comma (,) will now be used as the delimiter as there is at least one secondary type which contains a slash (/).
- The Discogs and MusicBrains option named Auto add files had a potential vulnerability. If insufficient files in an album were selected, the algorithm would automatically load files in the same album. However, depending on the order of events, additional files in the same folder could be loaded even if there were now sufficient files.
- The Create M3U action statement's filename field was only being unescaped once.
- The Copy Non Audio Files statement's inclusion field was not linked correctly causing values to be lost when an action was saved and reloaded.
- Fixed a potential crash when a remote host could not be contacted.
Earlier Version 6 Release Notes
Version 5 Release Notes
Version 4 Release Notes
Version 3 Release Notes
Version 2 Release Notes
Version 1 Release Notes