What is new in this release:
Today we released a small update to Yate. Not much changed other than working around a few Catalina issues. We also added new functionality to the UI to be able to identify, filter and re-encode progressive jpeg files.
What is new in version 4.3.0.2:
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.
What is new in version 3.7:
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.
What is new in version 3.6:
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.
What is new in version 3.54.0.1:
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.
What is new in version 3.4.0.1:
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.
What is new in version 3.2:
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.
What is new in version 3.1:
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.
Limitations:
There is a 14 day trial version with all the same features as the full release
Comments not found