Torrents for Mac Apps, Games, Plugins

Yate 3.12

2016-05-23   Music

Name Yate 3.12
Size 12.29 MB
Created on 2016-05-20 00:02:06
Hash af52f1b0d90f050d31bd748cc768620dfafd83b8
Files Yate 3.12/Yate (11.05 MB)
Yate 3.12/Yate 3.x [SP].zip (1.24 MB)

Descriptions for Description

Name: Yate for Mac
Version: 3.12
Release Date: 18 May 2016
Mac Platform: Intel
OS version:OS X 10.6 or later 
Processor type(s) & speed: 64-bit

Includes: K
Courtesy of Special K

Web Site:

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.12:
・Named variables now always persist while batch processing. The non-persistant option was a holdback to the application's earlier days and now has potentially breaking issues with the various batch processing modes. 
・In the rare event that you created actions to be run through the Batch Processor, which assumed that named variables were empty whenever a new folder as processed, they will break!. It is a good practice to always initialize named variables to the desired initial value.

 Main Window
・New field on the URLs panel called Podcast URL. 
・Added support for specifying that a track is a podcast. Note that iTunes only recognizes the setting when a track is first added. Setting the Audio Panel's Media Type field to Podcast will set the appropriate low level metadata for ID3 and MPEG-4 based files. When adding podcasts in ID3 files, iTunes requires that the Podcast URL field contains a well formed URL or it will not be recognized as a podcast. If you do not supply the URL and Podcast is specified, a hidden dummy URL will be supplied. When reading a file, the Media Type field will be set to Podcast if the low level podcast metadata is present. 
・There are now five Action-n toolbar items, increased from three.

・We've switched the application to use the custom Discogs authentication method. There is no longer a need to authenticate the application at Discogs. The Force Discogs Authorization and Validate Discogs Access Token menu items have been removed. 
・Discogs has increased the number of requests which can be sent in a given amount of time. The application's throttling algorithm has been modified to reflect the changes. Thanks Discogs!

・Better retrying is now performed for 503 and 504 responses.

・New Action menu item called Batch Extract iTunes PIDs. If you want the PID values and you have little or no metadata in your files, this process eliminates the need of dragging the tracks from iTunes into Yate. The process will also identify tracks in iTunes which cannot be located. 
・Linking to iTunes by PID silently updates the iTunes location if the file has been moved.

 Custom Panels 
・Links to multi item editing panels can now be placed on custom panels.

・The Database Viewer's context menu filter items have been enhanced and hopefully been made a little clearer. 
・You can now hide selected or not selected rows. 
・When database values are being accumulated, numeric fields are normalized to avoid ??? displays for same but textually different numeric fields. This mostly affects Album databases.

・The Multi Field Editor's Re-Encode function, the Re-Encode action statement and the Yate Transformations - Re-Encode to sub-menu, all have new options which are somewhat different than the previous usage of re-encoding from an incorrect Latin-1 determination. They are:

Unicode UNFC
When chosen a field will have decomposed accent sequences changed to composed accent sequences. eg. É will count as one character as opposed to two when taking the length of the field.

Force Latin-1
The re-encoding provides a forced transformation to Latin-1, preserving as many characters as possible. This differs from the Encode As ISO-8859-1 (Latin 1) statement as it does a smart transformation as opposed to simply trying to change the encoding. It will ensure that decomposed characters are composed; it will do a transformation of those nasty Unicode quote characters, it will preserve accents wherever possible; it will remove accents from characters which cannot be converted; and will change characters which cannot be represented to underscores (_).

Remove Accents
The re-encoding will attempt to remove all accents from characters.

Fold Characters
This changes various characters to their similar Latin-1 equivalents. Currently this includes single and double quote equivalents as well as dash/hyphen equivalents.

・Rename templates now have a Force Latin-1 option. This is equivalent to performing the Force Latin-1 re-encoding described above. One possible use of this is to ensure that files can be placed into m3u as opposed to m3u8 files while renaming. 
・Some users produce CSV files on other platforms and then create the associated sidecar (plist) file via Preferences-Export Sets, if required. When CSV files are produced on non Mac platforms it is possible that the OS cannot automatically determine the file's encoding if accented characters are present. In the past the encoding setting which can be specified for a CSV database was only used for writing purposes. If a CSV file cannot be opened letting the OS automatically determine the encoding, an attempt is now made to open it with the explicit encoding specified in the sidecar file. 
・The Read Text File and Write Text File action statements now support the explicit specification of an encoding. You can always do a read and then write of any text based file to process files produced on other systems. 
・The list of available encodings for database file creation and the Read Text File and Write Text File action statements now include twelve different possible encodings.

・Preferences-Audio-MPEG-4 now lets you set the rating mapping. Previously it was hard coded to be iTunes (0-100). 
・The Preferences-Audio rating mappings now support a new mapping called Direct*2 (0-10). This mapping is used by JRiver Media Center when writing MPEG-4 ratings. 
・There are now presets in Preferences-Audio and Preferences-Audio-Configure Full Rating Mapping for JRiver Media Center settings. 
・When Yate starts it automatically creates a backup of the application preferences. In Preferences-General You can now configure how many backup files will be retained. 
・File to Tag, Rename and Search templates can now be marked as Hidden. When Hidden, a template will not appear on any associated menu. This is useful when a template is used by an action and is not intended to be directly run. 
・Replacement set to fields can now be edited in a larger text view. They can still be edited inline.

Title Case 
・The v3.11 Title Case algorithm properly handles multiple sentences being processed. Abbreviations are problematic as they are terminated with periods. You can somewhat get around the issue by making general exceptions which cause the abbreviations to be set to lower case. However, the Title Case algorithm can do much better if it knows that the items are abbreviations. For this reason, Preferences-Exceptions has a new case mode called Abbreviation. This mode is only meaningful in the Title Case word list. In all other lists it is treated as No case change. The mode tells the Title Case algorithm to treat the word as an abbreviation when it is followed by a period. It is a good idea to use this new mode on words such as v, vs and ft.

Action Manager
・You can now specify that an action should appear on the File to Tag, Rename or Search for Artwork menu as well as the User Defined Actions menu. You do so from the context menu Add to Menu item. 
・In the past all actions which effectively started with a File to Tag statement, were automatically added to the File to Tag menu. This mechanism is no longer supported. However, all such actions will automatically be migrated to have the include on the File to Tag indicator.

Action Editor Windows
・There is now a button in the help panel which will load the displayed help page in the default browser. 
・You can now add if-endif and else sequences directly. Previously you could only add if-else-endif sequences.

New Action Statements
・AcoustID Metadata for ID. The statement can be used to manually extract metadata from downloaded AcoustID data. See the online help for more information. 
・Set User Defined Text Item. While UDTIs can be set by the User Defined Fields statement, this new statement is not limited to having the source in a variable. 
・Stop Action and Filter Files. The statement allows you to Close, Hide and Select Files, either Matching or Not Matching a chosen filter. The main window's filter functionality now supports the specifying of Variables in filters so that complex non destructive filters can be formulated. 
・Restart Batch Processor can only be specified while processing the Batch End inline action. The statement causes the folder traversal to restart. This can be used to create multi-pass actions. 
・Open File by the OS. eg. opening a file with a .txt extension will typically open the file via TextEdit. 
・Enumerate Tag Set. Useful when you want to write an action based on a variable set of fields. 
・Metadata for MusicBrainz Release Id. This statement is used to fetch the metadata for a specified MusicBrainz Release Id saving it to a key value list in a named variable. 
・Constrain Execution to a Single File. If you write an action which does not actually use the current file selection, it can be a pain to ignore meaningless action executions in grouped mode if more than one file is selected. This statement causes the action to operate as if a single file was selected.

Modified Action Statements
・The Replace action statement has new options called Leading and Trailing. They are similar to At Start and At End, with the exception that all leading or trailing sequences are replaced by a single replace with string. As an example, the Trailing option can be used to remove all trailing semi-colons in a field. 
・The Stop Action and Open Files statement can now specify multiple paths separated by newline characters. 
・The online help for the Move statement now describes the sequence to do duplicate handling. 
・When Batch Processing, if you are performing lengthy operations in the Batch Start or Batch End sub-actions, there may not be any progress updates for a while. The Prompt action statement now has a Batch Status mode allowing you to output a prompt message to the Current Folder field in the Batch Processor's progress panel. Doing this too often may slow things down quite a bit. 
・Re-Encode modified as described in the above Encoding section. 
・The Open Database for Querying statement now sets a prefix-Path named variable. It is the unescaped expanded path used to open the file. The variable can be passed as a parameter to any query database statement to identify the file. 
・The Column Value List From Query Database statement now has an ignore empty values option. 
・The Create Album/Track Database statements now create the path to the file if it does not exist. 
・When sorting the results of a Build List statement and Case Insensitive is specified, the sort will be an as in the Finder sort. 
・The Compare Date, Compare Numeric and Compare Text statements now all have an Any option. The default behaviour for stepwise execution is and has been for all files. The Any option, allows you to do a test which will succeed if true for any file. 
・The Load and Run statement can now be used when running in the UI. 
・The Move Non Audio Files statement no longer displays an error if the source and destination folders are the same. The statement simply does nothing. 
・The Add to List statement has new options to disallow adding empty items and/or items already in the list. You can also control how may files get enumerated when adding to a named variable and executing stepwise. 
・The Translate Rating statement supports the new Direct*2 (0-10) mapping. 
・The Ask, Prompt and Prompt for Text statements have a new Hide Info option. Thise option will hide the action name, associated file and reason text. This can result in a somewhat prettier display. 
・The Read Text File and Write Text File statements have been enhanced as described in the above Encodings section. After successfully reading a file the named variable Read Text File Encoding will be set to a textual description of the encoding used. If a file cannot be read due to the encoding, the Read Text File Encoding will be set to Indeterminate. 
・The Write Text File statement also now supports lossy and lossless writes. It also allows the testing of content to determine if it can losslessly be converted to a specific encoding. 
・The Repeat With, List to CSV and Build List statements allow an empty delimiter so there is no concept of a default delimiter. As this is typically not the case, the statements now pre-initialize to having a delimiter of ~ (the default delimiter's escape sequence). If you want an empty delimiter, you can delete the text. 
・The Access Query Database Cell statement has a new convenience function to set a cell to a named variable. This avoids the need to escape a named variable when setting a value. 
・All Query Database statements can now identify the desired database by specifying the named variable prefix supplied on the Open Database for Querying statement.

The Batch Processor
・The Batch Processor now automatically creates a named variable called Batch Phase. 0 implies Batch Start is executing. 1 implies that folder processing is occurring. 2 implies that Batch End is executing.

The Multi-Field Editor 
・The Replace panel has the new Leading and Trailing options.

MPEG-4 Files
・iTunes may use two atoms to identify the seller of a track. 'sfID' (the iTunes store) and 'xid ' (a vendor ID field). These contents of these atoms are now both displayed in the Seller field. Previously 'sfID' was stored in Seller, while 'xid ' was stored in a UDTI named iTunes Vendor xID. You can read more about the display format of the Seller field on the help page for the Privacy panel. 

Bug Fixes 
・The List Contains Test statement was not allowing an empty pattern for 'Equals' tests. 
・The Encode As statement did not handle Latin-1 properly. At times, ASCII could be substituted. 
・The Multi-Field Editor's Replace function had an extraneous Words checkbox. 
・The main window's status bar was not always displaying the longest common path. 
・The Access Query Database Cell statement was not accepting an absolute row index of 0. 
・The Column Value List From Query Database statement was ignoring the case insensitive option. 
・The following Database statements were not properly handling empty paths:Close Database, Update Database, Remove Items from Database, Save Database and Close Query Database. 
・Fixed a timing issue which could cause a crash when closing the Beatport Importer window. 
・The single export of a Tag Set from within Preferences-Tag Sets was broken. 
・Values were not being retained after doing a Set All or Clear All in Preferences-Tag Sets. 
・When an action was duplicated, the new action did not inherit the initial action's icon. 
・The Rename template IfExists and IfExists+ sequences were not working when a Variable was being tested. 




-Music  -  By