Torrents for Mac Apps, Games, Plugins

Yate 3.6

2015-05-10   Music

Name Yate 3.6
Size 10.36 MB
Created on 2015-04-29 12:44:00
Hash 50daa084536b3f03aa51ab069bad040314629044
Files Yate 3.6/Yate 3.x [SP].zip (1.22 MB)
Yate 3.6/Yate.dmg (9.15 MB)

Descriptions for Description

Name: Yate
Version: 3.6 (3999)
Mac Platform: Intel
Includes: K

OS version: OS X 10.6 or later

Yosemite Compatible Patcher

Courtesy of Special [K]

Version 3.6 (3999)
If you have written actions directly manipulating User Defined Text Information items (UDTIs) please read the section on UDTIs and Mappings.

Direct support for Notification Center has been added. You can now issue notifications through Growl or Notification Center. You can choose which classes of notifications you would like to receive. If you previously had notifications enabled they will still be issued via Growl unless you change the setting in Preferences - General. Note that if you are running OS X 10.6 or 10.7, a setting of Notification Center will automatically be treated as Growl. Notification Center support was introduced in 10.8.

Main Window

If you are running on OS X 10.10 (Yosemite) you can now Hide/Show the main window's tile bar via the Window menu.

UDTIs and Mappings

An earlier version of Yate moved the display of the MusicBrainz Recording Id to the Unique File Identifier (UFID) panel. This is where the value is stored in ID3 files and it seemed like a good idea at the time. In practice, however, not having the information in the same place as other MusicBrainz metadata (on the UD Text panel), was not a terribly good idea. The Recording Id is now displayed as a UDTI. Yate takes care of making sure it is loaded from and stored to the correct place in ID3 based files.
In the past, Yate normalized some FLAC metadata to use the same field names as those used in ID3 and m4a files. This was done for UDTIs which Yate directly manipulated (mostly various Discogs and MusicBrainz metadata items). FLAC metadata item names are only stored in upper case alphabetic characters and the normalization process ensured that there was a common name which could be referenced.

Starting with this version, Yate is far more aggressive with the normalization process and normalizes FLAC, ID3 and m4a UDTI metadata in order to produce a list of more meaningful names representing the function as opposed to the low level frame/atom/comment name which might have been chosen for arbitrary reasons years ago.

If you have written actions to manipulate UDTIs, they may break as the names may have changed. The Frame Mapping Table available from the main Help page describes the current values in the Field column and the older values (where appropriate) in the ID3 Frame column.

If you do not have the time to modify your actions, you can revert to the earlier behaviour by means of the Do not normalize UDTIs option in Preferences-Audio. We feel the new names displayed by the normalization process make much more sense and you should only remove the functionality if you really think it is necessary.

FLAC UDTI Mappings

In the past, if you were adding your own metadata items as UDTIs and you wanted common names to be displayed for FLAC, mp3 and m4a files, you had to use uppercase names. FLAC mappings to User Defined Text Info items are now used as alias names. If you want to add a metadata item called My Metadata, mapping it as a User Defined Text Info item will preserve the alphabetic case. This is a fully optional step for aesthetic reasons only and in no way affects what is stored in the audio files.

Custom Mappings

When assigning custom mappings you can now choose from a list of commonly used mappings to set their associated values. Note that as was always the case, Custom Mappings are based on the actual metadata frame/atom/comment names stored in the audio files.

Custom Panels

User Defined Text Information (UDTI) items can now be mapped to custom panels. This is the only component type which can appear more than once on a single custom panel.
There are now ten custom panels.
Custom panels can now have components which resize vertically which are not anchored to the bottom of the panel. You must now mark components as vertically resizable. Components anchored to the bottom of a panel are no longer automatically resizable. Custom panels built before this release will have been modified to have the same render behaviour as before. Components marked as vertically resizable will be resized when rendered unless they are adjacent to another resizable component which does not have the same first grid row or has a different number of initial grid rows.

Edit Panel Picker

If you've been using the Edit Panel Picker, you will have to rearrange the button order as seven new edit panels have been added (Custom 4 through 10).
The drawer based Edit Picker, was intentionally designed to be a single column display so that the drawer hugged the window as much as possible. With the introduction of the new Custom panels, it is now possible that not all the panel buttons can be displayed as a drawer cannot be larger than its parent window. If your main window does not have sufficient height to display all the buttons, buttons for which there is no room will not be displayed. A ... indicator will be displayed at the bottom of the drawer to indicate this fact. If you want to move buttons around, you may have to resize the main window in order to see them all. Note that the window based Edit Panel Picker is not affected.


You can now crop non square artwork items from any full artwork control's large image well via the Crop Artwork... context menu item.

Batch Processing

You can now optionally run an inline action before any files/folders are processed and after all file/folders have been processed. The special inline actions are named Batch Start and Batch End. The actions are always run stepwise even if the main action starts with a Force Grouped statement. Remember that information can only be retained in system variables between executions of the main action on individual folders.


New action statement called Normalize Artwork which ensures that every track in an album has the same artwork items.
New action statement called CSV Data to List. The function will convert one or more lines of CSV data to a list of lists representing the content.
New action statement called List to CSV Data. The function is used to format list data for CSV files.
New action statement called Stop Batch Processing.
The Remove Artwork statement now has an option to remove duplicates.
The Compare Text statement now supports the relational operators: . A fuzzy compare has also been added.
The following statements can now be executed when batch processing: Copy to Clipboard, Text from Clipboard, Ask, Prompt for File or Folder and Prompt for Text. The intent is to use the statements in the Batch Start and Batch End inline actions.
The Prompt statement by default gets written to the batch log file when executed while batch processing. There is a new UI option which will direct the prompt to be issued to the UI. The intent is to use the statement in the Batch Start and Batch End inline actions.
If you wish to create a CSV file which does not contain the minimum field requirements to be an Album or Track database you can now do so. Use the new standalone option in the Create Album Database and Create Track Database statements.

Bug Fixes

The Content Advisory and AAC Kind fields were editable.
Selecting an empty Content Advisory did not work if tracks were selected with multiple values.
When importing from Discogs, Part of a Compilation values of 0 were incorrectly identified as being different from a Yate value of empty.
The Set Variable to Action Test State was broken in the last release.
The Set Named Variable had some UI issues since the last release.
The Set System Variable had some UI issues since the last release.
The Prompt for File/Folder statement sometimes incorrectly hid the New File option.

Full Release Notes:

More Info:

Yate was developed for people who are serious about tagging and organizing their audio files. The application was designed from the ground up for Mac users. It is a 100% Cocoa written application and uses its own tagging library. Yate will tag mp3, m4a, AIFF, wav, dsf and FLAC files.
Yate has a long list of features, including an innovative scripting system called actions. The app also supports integration with Discogs, MusicBrainz, AcoustID and iTunes.

-Music    By