Kaindl-Hönig Fotostudio+Werbeteam GmbH Salzburg www.kaindl-hoenig.com

It appears that network changes in Mac OS 10.5.7 could adversely impact some hardware, specifically the Euphonix EuCon line of controllers. Here is information sent to customers today – thanks to reader Oliver Lucas for spotting this.

Please note that the new Mac OS update released yesterday, Version 10.5.7, breaks support for the feature in EuControl that automatically detects what control surfaces are attached to your network.

Euphonix is working on a fix – please DO NOT update your Mac OS until we release a software update that addresses the issue, as your MC Mix/MC Control will not be seen by your Mac.

For those users who have already updated to Version 10.5.7, you can roll back your Mac OS to the previous version if you are using Time Machine.

Update: this is now fixed.

There are no other apparent audio issues with 10.5.7 that I can see. (Visualists may be pleased about some NVIDIA driver improvements.)

My sense is this is most likely limited to the EuCon, which connects via Ethernet. It sounds specific enough that even other networked music hardware, like the Lemur, may be immune – I’m posting this partly in hopes, though, that Mac users can report back and let us know.

Here are the network changes:

    • Improves network performance when connected to certain Ethernet switches that have Flow Control enabled.
    • Improves stability for network home directories hosted by Mac OS X Server v10.4.
    • Improves Finder search results for network volumes that may not support Spotlight searching, such as Mac OS X Server v10.4, Time Capsule, and third-party AFP servers.
    • Includes several improvements to Directory Service and Client Management.

I’ve said it before, but I’ll say it again: I think this happens too often on Mac OS. It seems like Apple could do more to make it easier for customers to roll back an upgrade, and more to communicate to developers what changes may be.

That’s not simply a criticism. I think Apple excels at producing an exceptionally high-quality operating system, and the expectations users have for desktop reliability set a higher bar than the norm for Linux or Windows. They also run an aggressive release schedule, one that often gets improvements and fixes into user hands sooner. But then, music users are especially sensitive, and I think the situation would be even better if developer communication were improved and rollbacks were possible even without Time Machine.

Anyway, Apple (or Microsoft, or even to some extent Linux) you can’t control. What you can control with any upgrade is to make sure you have an image of your system prior to the upgrade and that you thoroughly test hardware on which you rely immediately so you can roll back. That’s always true on any OS, period. (Apple, to their credit, says just as much in their support document.)

More information is always appreciated.

  • There is an issue with external displays that are hooked up to the HDMI port:

  • MMI

    Seemed to break Live 8.0.2 as well. Ableton support was able to help me by having me remove my prefs file. Pain (had to rescan/re-auth some plugins) but it worked.

    Annoying given that there was really nothing I was actually interested in in the upgrade.

  • @MMI: Do you have the exact preferences file you had to remove? Any step-by-step details from Ableton support?

  • MMI

    BTW, before doing this, Live was blowing chunks on startup.

    Sure, simply remove:

    $HOME/Library/Preferences/Ableton/Live 8.0.2/Preferences.cfg

    After doing this, Live was back to stock. It doesn't even look in your plugins folders, you need to re-enable that stuff at which point your plugins may or may not ask for attention. Dunno what else I lost in the process, probably not much since I don't rely on a default set and I don't have bookmarks all over my library.

  • MMI

    PS. if the above didn't work, Ableton Support wanted:

    $HOME/Library/Preferences/Ableton/Live 8.0.2/Log.txt

  • As much as I agree with you Peter I think it's down to the individual user to start realize that jumping onto the latest OS bandwagon ain't a good thing. PT take a ridiculously long time to approve a new version but they do have a point. If ain't broke don't fix it!

  • jt

    hmm. ableton live 8.02 is all fine for me luckily, but i did get the euphonix warning email about an hour after i updated. doh! i'd rather wait for a fix than rolling back my system. that sounds like a disaster in the making.

  • @spinner: Well, yes, indeed. That's why I run screaming headlines trying to get people not to update. 😉

    I will say, though, this is something different on Linux, in which you really *can* get the operating system and applications and libraries in sync. There are still issues, and other challenges arise, of course, but to have people with their fingers in the code can make a big difference. Now, commercial tools *could* learn something from this, which is to get dependent changes in the hands of developers more aggressively.

  • Pingback: Create Digital Motion » Mac OS 10.5.7 Reports Wanted: Improved Performance, But Video Output Issues?()

  • daves561

    Wow, what an awesome coincidence. (And by "awesome" I mean "sucky") Today I upgraded to 10.5.7 (at some point in the back of my head I said "shouldn't I maybe wait to see what breaks first?") and *then* I ordered a EuCon. And *then* I read this blog post. All in that order.

    So the race is on: does my EuCon arrive in the mail first, or does Euphonix release a patch? My bets are on UPS. Nothin personal, Euphonix coders.

  • Oliver Lucas

    The patch has been released:


    Now that'swhat I call a fast reaction!

  • Pingback: Create Digital Music » Euphonix EuControl Software Patched, Fixes 10.5.7 Support and More()

  • I havent updated my OS in over a year. Never will probably. In fact, the number one piece of advice for someone running a mac: when its working, dont change a damn thing.

  • Well, let's not get too carried away. There are times when doing an update does in fact improve things, and if you're careful, you can avoid breaking something else in the process. I think it depends on the machine/situation.