Fixed love/dislike propagation to iTunes (macOS only).ĭue to a mistake, v5.2.0 requires macOS 10.12 or later.Dropped support for old macOS versions, because of notarization.Changed keyboard shortcut for zero rating (Windows only). ![]() Added ability to force synchronization.Added support for Beatport during metadata import.Added support for macOS 10.15 (Catalina) Music.app.Added ability to delete fingerprints from database (to reduce size).If you are using a Mac, you need at least OS X 10.12 to run beaTunes 5.2 (OS X 10.11 will be supported again in 5.2.1).Īs always, you can download the new version from the download section of the website. Important: Please note that due to Apple's notarization requirements I was forced to drop support for older versions of macOS. But there are some other changes, mostly small enhancements and bug fixes (see below). Undoubtedly, Music.app support is v5.2's most important feature. The good news is, owners of a beaTunes v5.x license can update to v5.2 for free and v5.2 does support Music.app. Because some essential things have changed, beaTunes 5.1 or earlier will not work with the Music.app. With the pending release of macOS 10.15 (Catalina), Apple will get rid of iTunes as we know it and replace it with the new Music.app. Depending on the size of your database, it might even be beneficial to restart beaTunes a couple of times. Note that for this to take full effect, you will need to restart beaTunes, as database compression always happens on shutdown. This will delete all fingerprints currently in your internal beaTunes database. So if beaTunes feels sluggish, you have a large library, and you don't need those fingerprints anymore-just get rid of them, by opening the Tools menu and choosing Delete Fingerprints. Why is this a good thing? The more the database grows, the more disk I/O may happen, and the slower everything becomes. It allows you to quickly delete all fingerprints from the database, which can substantially shrink the database file. That's why beaTunes 5.2.0 introduced a new feature that I believe is very handy, if you have a large library. However, when you've fixed all your metadata and are not hunting for duplicates, they take up a lot of space in beaTunes' internal database. As you can imagine, the process takes a little longer, so you might not want to do this all the time, but only every now and then.įor certain features like acoustic duplicate detection or lookup of metadata for files with no metadata whatsoever, audio fingerprints are a great feature. This makes sure that all your play counts, loved flags, etc. When you manually initiate synchronization via the File menu, and beaTunes 5.2 cannot detect any changes, you are given the option to force synchronization (see screenshot), i.e., to ignore any shortcuts, previous knowledge etc., and re-read all available data. And this is where forcing synchronization comes into play. However, those properties are available via AppleScript (Apple did a better job here). This means that just using the recommended Apple API certain changes cannot be detected. You simply won't find newer properties like loved, movement, or work. ![]() This is the Apple API that must be used to access the Music library. It has only one downside: Apple hasn't updated the ITLibrary framework for years. Therefore beaTunes uses a last-modification/hash-based approach, which works really well. ![]() If (osName.toLowerCase().Now, with macOS 10.15 and the new Music app, doing a diff is not an option anymore and checking the file system is inefficient. String osName = System.getProperty("os.name") If you're using JNA and it has this problem you can change the temp directory system property and JNA will create the file in a different directory. I've seen this happen with many different DLL files, like jna.dll. I read somewhere this can be caused by Microsoft Security Essentials but it doesn't look like this is installed on the computer that just experienced this problem. If you are the author of the code that put the DLL in the TEMP folder then I would recommend you change the code to put the DLL in a folder under this path instead as I have yet to see this problem there: %USERPROFILE%\AppData\Local\ I've found deleting the TEMP folder and letting it re-create it automatically usually solves the problem. Everything is fine one day and then suddenly you get an access denied exception when Java tries to access a DLL in the temp folder. This is a strange random error that sometimes manifests on Windows 7 and Windows 8.
0 Comments
Leave a Reply. |