Blog

Yate v3.7 released!

Yate

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!

Yate

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!

Yate

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!

Yate

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!

Yate

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!

Yate

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.

Yate v3.1 released!

Yate

v3.1 is out in the wild!

A bunch of new action statements that were on the list for a while have been implemented.

We’re big users of the Musician Credits field so we’ve enabled the direct editing of it and the Involved People field. There’s also a new format option which is essentially a UI based implementation of the Format Credits action statement.

Almost every function button has a new menu item to open the Multi Field Editor with the appropriate field selected. It’s pretty convenient.

We’ve also fixed a few v3.0 regressions and the first batch of Yosemite oddities.

We’ve also stared work on a Sample Actions area on the site. Each action has pretty much step by step documentation and a download link for the action and any other required Yate components. There will be more samples as we move forward. Documenting them takes far longer than creating them 🙂 All the samples at this time have been with created with v3.1.

You can access the Sample Actions webpage easily from within Yate via the Help menu. You can also get at it from the forum.

Yate v3.0 released!

Yate

UI overhaul, File Browser, Custom Panels, and tons of other changes.  Remember you can always view the release notes from the Help menu.

We’d like to thank everyone who helped test the release and those of you who looked at the previews and sent off suggestions.

We still have a long list of interesting stuff to do post v3.0.  If there’s something you’d like to see in an upcoming release please feel free to pass on the request.  Email works fine but the forum is a better place to share your ideas.

By popular demand, over the next short while we’ll be working on a resource area on the web site to describe sample actions, provide additional help topics and to supply tips for new users.

Yate v2.7.7 released!

Yate

Just some bug fixes around UI regressions in Preferences-FLAC and Preferences-Tag Sets that occurred in v2.6.

We’ve also added support for files with a .mp4 extension. This does not include files which contain video.

Well after 300 builds v3.0 is looking good. We’d like to invite our registered users to take a sneak preview and pass on feedback if you’d like. There’s a new sticky topic in the forum called called ‘v3.0 Preview’. If you’d like a peak simply email us at support@2manyrobots.com and put ‘v3 preview’ in the subject.

One gotcha! Yate auto migrates its preferences and exported preference files but only one way…. to newer releases. As there are new action functions in v3.0 the preference file level has been bumped and will not load in versions prior to v3.0. If you want to play with the preview it might be a good idea to export your preferences first. You do this via Yate>Export Preferences.

We’re pretty exited about v3.0. As a matter of fact going back to v2.x releases for testing purposes has become quite painful for those of us that have been using v3.0 for quite a while now.

Changes to Discogs

Yate

On Aug 15th Discogs will start failing search API requests when the request is not secured with an OAuth access token.

This means that in order for Discogs searches to continue to operate in Yate, you will have to authorize the application to run.  We’ve written a wizard which will step you through the process automatically.  In theory this wizard should only have to be run once.

In order to authorize Yate you will have to be registered at Discogs.  If you have not already registered you will have to do so.  While you have to log in to authorize Yate you do not have to be logged in while accessing Discogs via Yate.

This functionality will be available in the upcoming v2.7.6 release.  This should be the last release before v3.0.

We understand that some people are against registering at web sites and we feel for you.  However, it is not our data and we have to play by their rules.  Discogs remains an amazing resource and we’re happy to be allowed to continue to provide access to it.