beaTunes News

Saturday, November 18, 2017

Pssssst!

We're having a sale over at MacUpdate.

Labels: ,

Tuesday, November 7, 2017

Still using beaTunes 4? You might like this!

beaTunes4 logo

beaTunes 5 has been released a couple of months ago and of course I recommend you buy an upgrade license for your copy of beaTunes 4 (if you haven't done so already). There are certainly a bunch of good reasons for upgrading. But if you're still on beaTunes 4 and don't want to jump to version 5 just yet, you might want to update to version 4.6.18.

Most of the changes in 4.6.18 are back-ports of changes originally made for beaTunes 5. There's just one exception: The Chordify integration hasn't been fixed in beaTunes 5 yet (this will happen in the next update).

Please note that you can only get this update from the old downloads section of the website.

Changes in 4.6.18

  • Improved artwork lookup via Discogs.
  • Improved handling of MIK key data.
  • Fixed Open in Chordify.
  • Fixed ignore Amazon album version solution.
  • Fixed inline BPM editor for tempi without relative salience.
  • Updated Amazon integration for Spain and Italy.
  • Updated built-in Discogs database.

Labels: , , ,

Wednesday, November 1, 2017

High Sierra menu bar bug fixed in 10.13.1?

As of macOS 10.13.1, I cannot reproduce the infamous menu bar bug anymore. It appears as if Apple has listened to our pleas and fixed the issue.

Is this fixed on your system as well after you've updated to macOS 10.13.1? Please leave a comment (in the web version of this post). Thanks.

Labels:

Friday, October 27, 2017

Let Apple know that High Sierra bugs bug you

In theory, this blog post should be about how great beaTunes works on High Sierra, Apple's latest version of macOS. Unfortunately, Apple still hasn't fixed an embarrassing bug, which is why beaTunes users have problems using their software on High Sierra: Unless you start beaTunes with English as your system language, the menu bar may not work properly. The obvious workaround: change your system language to English and then start beaTunes. But really—who wants to do that just to start an application?

It seems to me that Apple never ran a Java application under a non-English language before they shipped High Sierra. One might argue that a billion dollar company should have better quality control...

I'm also under the impression that Apple classified the bug that prevents beaTunes to work properly as a low priority bug. The simplest way to change that is to tell Apple it's not. How do you do that?

By filing a (duplicate) bug report.

Simply go to https://bugreport.apple.com/, log in with your Apple Id and describe the problem like this:

Summary:

In a Java app, when the System property "apple.laf.useScreenMenuBar" is set to "true", the JMenuBar instance set on the displayed frame should appear in the macOS screen menu bar. This is not the case under macOS High Sierra 10.13.0 when the application is run from an .app bundle with a non-English system language.

Steps to Reproduce:

See https://bugs.openjdk.java.net/browse/JDK-8188085

Expected Results:

The menu bar should contain a "File" item that's clickable.
The application menu item should contain the usual suspects, incl. "Quit".

Actual Results:

The file menu item is missing.
The application menu item is empty.
For more details see the screen capture https://bugs.openjdk.java.net/secure/attachment/72794/menubar_bug.mov

Version/Build:

OpenJDK Java 8_144
macOS 10.13.0

FYI: This bug report is a duplicate of 34117157.

By the way, beaTunes is not the only software that suffers. Pretty much all of JetBrains' products are broken, too. Hopefully, if enough people file the same report, Apple wakes up and fixes the issue quickly.

That all aside, beaTunes 5.0.5 is out! As always, you can download the new version from the download section of the website.

Changes in 5.0.5

  • Improved "Open in..." file extension support for Windows.
  • Improved statusbar to show data about selected songs.
  • Improved handling of MIK key data.
  • Improved support for APFS (High Sierra).
  • Improved artwork lookup via Discogs.
  • Added write progress dialog to multi get info pane.
  • Changed grouping/work behaviour.
  • Fixed odd NPE on Windows when MyDocuments is root folder.
  • Fixed gamma issue with application icons (High Sierra).
  • Fixed multiple showing of identical notifications.
  • Fixed key matching with SYNC button enabled for small sources.

Labels: ,

Wednesday, October 11, 2017

High Sierra Woes

Good news! Apple has indirectly acknowledged that the non-English UI High Sierra issue for Java apps is indeed a High Sierra bug. Apple engineers are working on a fix.

Let's hope said fix is going to be released with macOS 10.13.1—it does not seem to be included in the current beta version.

Labels:

Friday, September 29, 2017

Don't update to High Sierra just yet

Apple users: I just want to re-emphasize—don't update to High Sierra just yet. It's still a dot-zero version, i.e. there are kinks that need to be fixed. Apple and third party vendors are on it.

For those of you who can't resist new, shiny, and not quite working things—here are some tricks to get beaTunes to run on High Sierra.

Labels:

Monday, September 11, 2017

beaTunes on High Sierra

macOS 10.13, also known as High Sierra, is going to be released very soon, which means it's time to talk about compatibility with beaTunes. An issue some beta users reported is a missing menu bar. In essence, just the application name, but none of the usual menu items are visible, which makes it impossible to work with beaTunes.

Should you encounter this issue, please try the following solution see note below.

  • Go it https://support.apple.com/kb/DL1572 and install the latest Java version distributed by Apple.
  • The package will install two items: An antique Java Virtual Machine (JVM) and the JavaVM.framework.
  • Unless you still use an application that uses Java 6 (beaTunes does not), you should remove the Java 6 VM right away, because of security issues.
  • But for beaTunes to work properly, you must keep the JavaVM.framework, which has no known security issues.

Please let me know, should you encounter any other High Sierra-related issues.

Thanks.

Update

The issue seems to have been resolved in the final version of macOS 10.13.

Update 2

Unfortunately, the issue still persists on systems with non-English locale. To get beaTunes to run properly

  1. Please switch your system's UI language to English (via System Preferences)
  2. Start beaTunes
  3. Switch back to whatever your regular UI language is
I apologize for this inconvenience and hope it's properly fixed soon.

Update 3

Apple has indirectly acknowledged it's an operating system bug. They are working on a fix.

Labels: , ,