Steinberg Installers Not Compatible With OS X Yosemite

Steinberg VST 3.5Steinberg has announced that its installers are not currently compatible with Mac OS X Yosemite, but that they have a workaround in place.

Here are the details:

If you are planning to update to Yosemite this fall or to take part in the Yosemite beta-testing program, please be aware that our software products as are cannot be installed on this operating system. Current Steinberg software installed before updating to OS X Yosemite is not affected.

The solution we offer is a small software tool currently available as downloadable pre-release version from our website which will enable a seamless installation of our existing software range on the OS X Yosemite operating system.

Check the Steinberg site for their latest information on compatibility.

14 thoughts on “Steinberg Installers Not Compatible With OS X Yosemite

      1. There aren’t such problems on OS X (fake viruses?): every major Mac OS X (or Windows) update can bring about incompatibilities with certain software. Yosemite has a lot of new features that often aren’t perceivable by users: it’s not only about changing the GUI.

  1. if they worked with mavericks then somethings changed, this yearly update in OS for apple is becoming a compatibility issue. only minor things arise per update, but across several years real problem are occurring. first apple then microsoft, every one is blinded by iOS

    its the new VHS : )

      1. VHS was chosen over Beta max for it commercial viability not its quality, am suggesting that iOS is inferior to OS X, and apple (and Microsoft) are going for the short term solution, in a market were competition is leading to side ways innovation to sell devices and computers. The pace of technology is two fold, the consumer product say a phone, repackaged with a new camera in, a faster chip, new OS ect goes from phone 49 to phone 50. this phone will be updated next year to phone 51 with similar specs increased ect. ect. But the other side of this is that the hardware and software hasn’t really advanced that much, the pace in most cases for hardware has slow down slightly, 10 years ago this kind of technology would have been released at more like 2-3 year periods.

        and the VHS analogy, VHS was the save bet technology a bit like mobile devices today in respect that the likes of apple are going all out for the iOS market, its save, people want it and their is a lot of demand for it but like video its really stagnating because of the compression in release cycles and the unwillingness to brake the mould. Just think of the last generation of VHS video recorders and how they evolved more useless features than god know what, DVD had been in the wings for years but no one jump ship at first.

        hope that clears it up, and by the way my day job is IT, I work with both apple and Microsoft software and hardware, and Yosemite like mavericks before has some significant changes to the OS. With Mavericks they did change coding to their audio drivers, not major but they did tinker, I haven’t beta tested Yosemite i haven’t got time but I hear more changes are a foot, only time will tell. If you going to up grade image/clone your drive first then you can go back after if issues arise (same goes for any OS upgrade).

    1. The compatibility problems are starting to get a little annoying considering how incremental the updates on the these OSes are.

  2. Honestly, I blame the majority of the compatibility problems on the developers, not apple. Apple developers get OS releases many months in advance for testing, tons of documentation, and solid support from Apple through various channels. It’s always the older software companies that have issues with their software… Autodesk, Adobe, Avid, Steinberg, etc…. places that have glacially slow update cycles themselves, often to a code base that is more than a decade old, and often charge phenomenally high prices compared to other comparable software options. Most software companies have their updates ready well in advance of an OS release (Mac or Windows), and don’t charge you for a point release which really only rolls in those changes.

    I’m not saying software development is easy, but the way a company is structured, the age of a code base, and the personalities involved all do WAY more to slow down the development process than Apple and it’s updates ever could.

    1. How is it the developpers fault if there aren’t any legacy support in OSX? Also how could Steinberg have known about it when Apple never tell people what they will retire in the next version of OSX? This is why a lot of software breaks with OSX updates as opposed to Windows where most software from 10 years ago still work without any need to be updated for the new version of the OS?

    2. Seems like a lot of companies stumbled over Sandboxing. I suppose it’s a good thing, but it meant that developers had to spend time rewriting sections of code that had not needed to change for years. The down side is that time spent accommodating changes to fit Apple’s rules and make it into the Mac App Store is time not spent moving products forward in other ways. To developers, it’s a cost — effort put in that is not visible to the customers.

  3. “They have a workaround in place.” Oh, I’ll just BET they do! Better to release a finished piece that doesn’t need one than to make the customer jump through update hoops. Its another small lesson in upgrading only after you’re sure that your key tools have gotten in line with the new OS. That’s substantially better than grinding through it by inches.

  4. It’s not even a released OS yet. One big purpose of beta software is to catch and fix stuff like this way in advance of release, which Steinberg is doing. It’s only a problem if the official upgrade causes problems as the dev company will have had time to test and correct.

    1. I agree. There’s a reason people incorrectly call every plugin “a VST” — Stienberg produces some really good software and paved the way for high quality, low latency, plugins. But the fact remains that an installer doesn’t do a whole heckuva lot. It basically just has to copy files to the right locations, maybe setup a system daemon, and potentially activate a kext or two. None of those APIs change very often, and certainly not drastically; even between OS versions. So I maintain my opinion that “they did it wrong.”

  5. I’ve just upgraded my entire DAW to Yosemite and all my applications and plugins work (of which there are dozens) except for Steinberg’s Padshop Pro. It just won’t work with Logic. Pretty unimpressed.

    The Padshop installer is now also asking me for my E-Licenser dongle – which I don’t have because I never needed one for Padshop before. I hope that’s a bug because I love this Synth (when it’s working) and I don’t want to get another bloody dongle just for that one plugin.

    Whinge over.

Leave a Reply