Archive for the ‘Blog’ Category

Yate v3.10 released!


First and most import…Happy New Year!

Yate v3.10 has been released. Far too much to list here. Check out the release notes.

Once again thanks to everyone who tested the previews.

Yate v3.9 released!


v3.9 is out. Lot’s of feature request implementations in this one.

The release was supposed to be primarily about the importing of changes from CSV/TSV files. Somehow a pile of AcoustID, Discogs and MusicBrainz enhancements made the cut…..and last but not least there’s support for downloading artwork from

Thanks to everyone who took the time to test the previews.

Yate v3.8 released!


v3.8 is officially released. Lot’s of exciting things in this release. Far too many items to discuss here. Check out the release notes.

Sometimes it’s the simple things that catch you. Personally, we like the new full grid display mode.

We’re also releasing a new application called Audio File Health Check. The application walks your collection’s folder structure looking for errors in audio files. While intended to be a companion application to Yate, (which can fix all the serious errors), it is available to everyone for free.

We’d like to thank everyone out there who went above and beyond what we expected when testing the v3.8 preview builds. Your help and feedback is much appreciated.

v3.8 Preview


v3.8 is now available for preview.  The release has support for video, the reintroduction of the auto-downloading of Discogs images, a new snapshot mode and the introduction of Beatport support.


If you’d like to take a look at it send an email to with Preview in the subject line.   Registered users only please.

Yate v3.7 released!


3.7 is finally released!

We’ve finally found time to redo the Multi Field Editor. We hope you like the new look.

We’ve spent a lot of time working on the AcoustID, Discogs and MusicBrainz action statements. With a little bit of luck you should be able to use AcoustID and MusicBrainz to find and match files without any tagging information.

We were an early supporter of DSF files, even going as far as to provide a free converter from DFF. We’re excited to now support the new conventions used to directly tag DFF files. If you use dff2dsf there’s a new release which will preserve tags in the source file.

Of course there’s lots of other stuff and as usual the full list can be found in the release notes.

To close off there’s one more item to discuss. We’ve finally got around to dropping 32 bit support. We polled you over a year ago asking for your opinion on the the matter and not one person responded that they wanted us to maintain support for 32 bit only Macs. You can’t accuse us of acting too swiftly on the matter 🙂

Yate v3.6 released!


3.6 is out. A somewhat mixed feature set in this release.

We’ve tried … once again … to make sense of the various UDTIs used in conjunction with Discogs and MusicBrainz. We’ve opted to go with meaningful names as opposed to names directly associated with the low level audio frames/atoms/comments. This potentially can break existing actions if you are directly manipulating the UDTI names so we’ve built in a “dont’t do it” option. If you can’t do so now, you should eventually move to the default naming conventions as soon as possible as the option may be removed in the future.

We write a lot of actions! We significantly expanded the capabilities of the batch processing mode by supporting the running of an inline action before any folders are processed and another inline action after all folders have been processed. A number of prompt type action statements are now supported while batch processing so that you can interact with the UI. This was primarily enabled to use in the new Batch Start and Batch End inline actions. If you design new interactive actions for batch processing, remember that you can only use system variables to retain information between the per folder executions of the action.

As usual there are a slew of feature requests implemented. There are now ten custom edit panels and we’ve relaxed the conditions as to when components can be vertically resized.

…and last but not least, there are some bug fixes as well.

The full release notes are always available from the Help menu.

Yate v3.5 released!


Well we finally got a Mac which has a Retina Display. v3.5 fixes the issues which some of you were partially getting around by dividing your desired artwork scale sizes by two. Thanks for your patience. As is often the case, the required changes were fairly trivial.

A mixed bag of changes this time around. UI, artwork, actions and more. As usual there were a number of feature requests implemented and little annoyances fixed that we found while using the product.

The action set continues to to grow in power and flexibility. The sample action ‘Extract Producer from Involved People’ is down to a single statement.

Stay tuned….more to come.

Yate v3.4 released!


Well, the intent was for there to be a relatively fast turnaround after v3.0 shipped for the next release. Then v3.3.1 kept getting larger and larger and larger and now here we are at v3.4.

This time there is a rather eclectic mix of new features, all user driven.

People have been asking on and off for more comprehensive filtering of the main file list. We finally bit the bullet and jumped onto the implementation. Hopefully you like the new file list filtering.

We’ve provided the first round of AcousticBrainz integration for the extraction of low level audio properties. Currently you can import BPM and key values. They seem to have two different key determination algorithms which can produce different results. We’ve allowed to you import both results.

The number of custom fields has been expanded to ten and we’ve supplied a more comprehensive means of mapping the custom fields to low level audio frames, atoms, comments. The custom fields are now synchronized across the Yate feature set. As an example, if you run the MusicBrainz wizard and extract release ids which have been mapped to custom fields, they will will be properly synchronized to the low level components.

We write a lot of actions, so there are always action changes in each release. There are about six new functions and about another six or so have been enhanced. One significant change is that you can now directly embed a field value in any text field which supports escape sequences. \[Album] will insert the value of Album field. The properly escaped field names can be pulled from a context menu.

In the action editor we’re now keeping the date/time an action was last modified. and enhanced the sorting capabilities. You can specify the date representation and separate the display into ‘today’ and ‘not today’ values. If you want the actions you’re working on to really pop out at you, use the following date format:
‘★’ HH:mm:ss|yyyy-MM-dd HH:mm:ss

There’s lots more and as usual the full set of release notes can be viewed at any time from the Help menu.

Thanks once again to everyone who helped test this release.

Yate v3.3 released!


Another year done. Another release of Yate. v3.3 is now available. There was going to be a v3.2.1 but as often is the case with Yate a simple release gets to the point where it is no longer a simple release. Just one more feature, and just one more feature and well, you get the idea.

Here’s wishing all of you the very best for the new year.

Yate v3.2 released!


Lot’s of feature requests implemented, bugs fixed, new and enhanced action statements and a few Yosemite work arounds. It looks like v3.2 is officially released.

We’ve been having a lot of fun playing with the new Duplicate Identification and enhanced Query capabilities. It looks like I have 32 distinct versions of “House of the Rising Sun” under 4 different title variants. I guess I tend to like different covers of the same tracks. 18,044 of my 40,803 tracks are identified as duplicates when looking for similar named tracks.

Once again, thanks to everyone who helped us test this release.