beaTunes News

Sunday, October 7, 2018

beaTunes on Mojave and Windows 10: Dark Mode and the AEpocalypse

Recently Apple has released Mojave, version 10.14 of its desktop operating system macOS. With respect to beaTunes this had three effects:

  1. The much touted dark mode was not automatically supported.
  2. Mojave asked for user permission, before it let beaTunes talk to iTunes.
  3. Due to a bug in Mojave, oftentimes beaTunes was unable to display the remaining time in its player.

With today's update, all three issues were addressed to various degrees.

Automatic Dark Mode

beaTunes 5 has supported a dark theme for a long time now. With v5.1.10, it will automatically honor the system setting at startup time (switching to or from dark mode while beaTunes is running is still not possible). This applies to both macOS 10.14 and Windows 10. Note that this implies, that you cannot select the theme from within beaTunes anymore. Instead you have to use the operating system's dialogs.
To enable the dark mode under Mojave, open the System Preferences under , then select General and then Dark. If beaTunes was already running, please restart it, so it can pick up the changed setting.

To enable the dark mode under Windows 10, open the system Settings (the cog wheel in the Windows menu), then select Personalization and Colors. Scroll down to Choose your default app mode and select Dark. More detailed guides can be found all over the web, e.g. here. Again, you might want to restart beaTunes after the change.

AEpocalypse :: Averted

With Mojave Apple introduced AppleScript Sandboxing. In essence that is a mechanism that prompts the user for permission before one application can control another, i.e. can send Apple Events to it. Let me be clear about this: It's a good thing. But, as pointed out before, Apple could have made more of an effort to ship a quality implementation earlier. That said, the final result does not seem to be all that bad. I have made an effort to provide decent explanatory messages in case something goes wrong. The important thing to remember is that you can turn automation (AppleEvent) permissions on and off in your System Preferences under Security & Privacy.

And should nothing work anymore, you can reset the authorization mechanism for all apps using the following line from the Terminal command line:

tccutil reset AppleEvents

For more info, please see Daniel Jalkut's blog post.

Player Issues Workaround

A couple of words about the beaTunes audio player. Because Apple broke one of their APIs, the player did not correctly show the remaining time, a playhead or segments. Luckily, I've found a workaround, so this is fixed in v5.1.10.

What else?

Additionally to the mentioned changes forced by external events, I have found some time to change/fix some other things. Fans of classical music will probably like that if a tonal key can be found in a track title, it will be used instead of content-based estimates. And I'm sure macOS users will appreciate that the playing-track system notification now shows album art.

As always, you can download the new version from the download section of the website.

Changes in 5.1.10

  • Fixed non-committing genre changes in info panel.
  • Fixed possible application hang during recovery.
  • Added automatic support for Mojave and Windows 10 dark modes.
  • Added workaround for Mojave AVPlayer bug (remaining time).
  • Added support for album art in macOS system notifications.
  • Enabled compression when communicating with AcousticBrainz.
  • Improved key import from textual metadata for classical music.
  • Improved export of m3u playlists with non-ISO-8859-1 chars.

Labels: , , , , ,

1 Comments:

Blogger Koen De Jaeger said...

I only wish traktor and beatunes to be dark though, not the whole windows 10 OS.

October 15, 2018 at 3:02:00 PM EST  

Post a Comment

<< Home