Thursday, 4 October 2018

macOS Mojave update

We can confirm that there is a minor problem with BitPerfect under macOS 10.14 (Mojave) which is preventing Integer Mode from being selectable. Interestingly enough, if you had previously been using Integer Mode on your selected DAC, BitPerfect was still playing using Integer Mode, even though the check box was unchecked and grayed out.

In any case, we have developed a fix for this issue. It is currently undergoing test, and will soon be released for Approval to Apple. You should be seeing it in due course as an update.

Saturday, 29 September 2018

macOS Mojave problem

We are seeing evidence of unusual behavior of BitPerfect under macOS 10.14 (Mojave). It seems that the Integer Mode checkbox appears to be greyed out and unchecked, and yet playback is still happening in Integer Mode.

It looks like something that will need to be addressed with an update to BitPerfect. As soon as we have any further information to report we will post it here.

Thursday, 27 September 2018

macOS 10.14 Mojave

I have just installed macOS 10.14 Mojave on one of my Macs and so far BitPerfect seems to be working just fine with it.  This is not yet a comprehensive approval, but at least I have not encountered an out-of-the-box catastrophe.  BitPerfect users who wish to upgrade to Mojave can do so if they need to for other reasons.

Monday, 12 March 2018

AirPlay with High Sierra

After my slightly encouraging reports on AirPlay under Sierra, the newer High Sierra (macOS 10.13) has proven to be a catastrophic step backwards.  AirPlay under BitPerfect failed completely.  You would go through all the hoops to get BitPerfect to select your preferred AirPlay device as its designated audio output device, but as soon as music started to play - and BitPerfect hogged the AirPlay device - macOS would observe that the device had suddenly disappeared, and would delete its Standard Audio Interface.  Since this is what BitPerfect was using for playback, it meant that playback instantly stopped, before it even got started.

Well, without any fanfare, it seems Apple have fixed this with the 10.13.3 update to High Sierra.  I am now getting it to work.  The approach is pretty much as described in the previous post (which I linked to above) except for one thing which has changed.

As before, you still need to go into iTunes and in its “Choose which speaker…” selector (the button with a ‘transmission beacon’ icon to the right of the iTunes volume slider).  But now you need to be sure to choose the AirPlay device that you actually want BitPerfect to play to and NOT "Computer".

I hope this is a sign that Apple are taking seriously the situation where third-party software (such as BitPerfect) "hogs" a device (in Apple-speak, puts it in "exclusive mode").

Wednesday, 15 November 2017

Announcing BitPerfect v3.1.2

Today we announce the release of v3.1.2 of BitPerfect.  This is primarily a maintenance release which addresses a specific problem where BitPerfect is unable to play to AirPlay devices under macOS High Sierra (i.e. OSX 10.13).  

This is a workaround rather than a proper solution.  The workaround means that BitPerfect plays without Hog Mode when playing through an AirPlay device.  This means that other extraneous noises and sounds will be audible even when BitPerfect is in control of playback.  However, this only happens if an AirPlay device is used, and if the Operating System is 10.13 (High Sierra) or higher.  Hog Mode will continue to be engaged under all other conditions.

This release requires OSX 10.8 or higher, as will all future updates of BitPerfect until further notice.
As usual, BitPerfect v3.1.2 is a free upgrade to all existing BitPerfect users.

Monday, 30 October 2017

Avoid High Sierra

Too many problems are now emerging with macOS High Sierra, and I must strongly recommend that BitPerfect Users do not make this update.  Sorry if this has come along to late ....  my bad.

In order of importance:
  • High Sierra has totally broken AirPlay under BitPerfect
  • High Sierra causes iTunes to crash unexpectedly 
  • High Sierra can cause BitPerfect to skip on some computers
I will post any updates in dues course

Tuesday, 10 October 2017

iTunes 12.7.0 crashing

I am getting several reports of iTunes 12.7.0 crashing.  This crash only seems to happen when BitPerfect is running, and also seems to be associated with the new macOS 10.13 (High Sierra).  Although the crash seems to happen only when BitPerfect is running, the reports seems to be consistent that it only happens after a listening session is over, and not while music is actually playing.  In my own case, when I see this problem it is usually when I look at the system first thing in the morning and find that it has crashed overnight.  Also, it is both infrequent and intermittent - my own system has not crashed in nearly a week.

The iTunes crash reports do not provide any indication (at least not to us) of how the interaction with BitPerfect is causing this crash.  BitPerfect's communications with iTunes has not changed across several generations of BitPerfect, and is performed consistently with Apple's meager documentation on the subject.  However, one this that has changed with macOS High Sierra is that a new message is now flooding the console log, but that seems to be an irrelevant warning rather than an error per se, so it is hard to see how that can be the culprit.  But is seems reasonably likely that it is probably a symptom of the same issue.

A related issue is that after a period of inactivity, BitPerfect seems to "lose its connection" with iTunes.  It is as though somewhere inside macOS and/or iTunes a "handle" to the communication channel between BitPerfect and iTunes has been reset, and nobody has seen fit to advise BitPerfect and/or iTunes.  When this happens, it is necessary to quit BitPerfect and then separately quit iTunes.  Sometimes iTunes refuses to quit completely (the 'dot' remains below its task bar icon), and it has to be "force quit" via Activity Monitor.

Any information BitPerfect users can provide that helps to shed light on this issue would be most welcome.  Please e-mail us at