You know the drill. There’s a new operating system from Apple. It breaks some music software. If you don’t like things breaking, you should wait a bit. Then once you’ve verified the stuff you need is compatible, go for it – it’s probably better than the last OS once the wrinkles are ironed out.

This post occurs with each new OS, a bit like some sites do Holiday Shopping Guides, or April Fools’ jokes. I could almost turn it into a Mad Libs post. But here are the specifics.

The operating system: OS X 10.11 “El Capitan.”

What breaks: plug-ins, mainly. Some Audio Unit plug-ins don’t pass validation. We’ve heard that from Native Instruments and Arturia already. Arturia says they’ve seen issues with standalone software, too. Either way, we’re talking software qualification. And I suspect we’ll hear from more developers through the day, not just Arturia and NI (feel free to sound off in comments).

Check hardware, too. Here, we only have heard from NI, but it’s a huge issue – kernel panics with the MK1 editions of Traktor Kontrol S4, X1, Traktor Audio 2, and Maschine, plus the Audio 2/4/8 DJ and Guitar Rig 3 Rig Kontrol 3 hardware.

Meanwhile, Elektron say their Overbridge tech isn’t quite working with 10.11 yet, either. (Their hardware is fine, but not with all the integration features.)

The good news here – in NI’s case, at least, there are already beta drivers. I’m all set to use my VST versions of my plug-ins and Maschine in glorious monochromatic orange.

Back in my day, Apple never used to have OS upgrade quality issues. Why have they abandoned pros? Ah, too true. I remember the golden days, back in Yosemite, OS X East Bay, OS X Delayed BART train, 10.6, 10.5, 10.4.8, 10.3, Mac OS X Puma, Mac OS X Llama, Mac OS X Rabid Kitten Beta 3, System 8, System 7.5.3 revision 2, System 7.blergh, System 6, PowerBook 5300 On Fire, Apple III Drop It On A Table Until It Starts Working… no problems whatsoever. Everything “just worked,” back when Steve Jobs was with us and I used my Mac Classic at school which I went to and from uphill in the snow both ways even in September, until the sad day when Gibson bought Studio Vision Pro and killed Christmas forever and the End Times were nigh.

Okay, no, seriously:

Will this get fixed? Yes, and if past OS updates are any indication, reasonably quickly. Just sit tight.

Why Shatner? Kirk in Star Trek V climbs the mountain El Capitan, in Yosemite Park (each a namesake of an OS X update now). Also, spoiler alert: Kirk falls. So before you make “love to the mountain,” be aware of the risks, and make sure Spock catches you. I mean, uh, make sure you have a backup before you upgrade.

Backup first. I’m not preaching abstinence; I’m saying use protection. Make a backup first. That was tasteless, sorry – but I think I’ve written this story ten times in the history of CDM, so you can expect the quality to degrade as I age. 😉

Updated: when you are ready, here’s four hours of Shatner while you wait on your machine to backup and upgrade.

Updated: Add notation software and UI problems to this list. Via CDM comments – thanks, Wheat!

“we’ve discovered some new incompatibilities with Finale 2014d. Specifically, opening certain dialog boxes (involving expressions, articulations, and others) can cause Finale to crash.

…at this point we advise against upgrading to El Capitan immediately upon its release. If the solution is on our end we will address it with Finale 2014.5, which we plan to release by the end of November”

http://www.finalemusic.com/blog/finale-and-os-x-el-capitan/

  • Gunboat_Diplo

    The Final Frontier is criminally underrated in the Star Trek canon.
    And all those damn kids complaining about OS upgrades weren’t around in the days of trying to get MIDI interfaces to even speak with OS9.

    • Yes, though Final Frontier did keep the ‘odd number’ curse going. 😉 Speaking of which, have we worked out what the current rule is for OS X operating systems on that?

      • Gunboat_Diplo

        OSes are so stable now, I suppose its more like trying to pick your favorite season of the Simpsons: either you go with early seasons/updates that are consistent and stripped down or you go with later seasons/updates that occasionally have a great new characters/features but otherwise are just tinkering with the current formula.
        i’ll just never forget OSX made it immediately easier to get all my interfaces to work together. one day i’m struggling with drivers and the next day everything worked. it was a festivus miracle.

    • oh lord, those were the days. Trying to sync cubase midi with Tascam tapes… Madness

      • Remember upgrading Digidesign PCI cards in expansion bays, while we’re at it?

        Or SCSI problems?

        Or… I could go on. Memories… 🙂

        • I also remember the first day I came to the studio with the whole session on an usb key. Paradise

        • Oooh lawd we came from far away

    • wetterberg

      aw hell – just had army-style PTSD flashbacks to setting up opcode systems back in the previous century… It very nearly killed me.

  • Gunboat_Diplo

    The Final Frontier is criminally underrated in the Star Trek canon.
    And all those damn kids complaining about OS upgrades weren’t around in the days of trying to get MIDI interfaces to even speak with OS9.

    • Yes, though Final Frontier did keep the ‘odd number’ curse going. 😉 Speaking of which, have we worked out what the current rule is for OS X operating systems on that?

      • Gunboat_Diplo

        OSes are so stable now, I suppose its more like trying to pick your favorite season of the Simpsons: either you go with early seasons/updates that are consistent and stripped down or you go with later seasons/updates that occasionally have a great new characters/features but otherwise are just tinkering with the current formula.
        i’ll just never forget OSX made it immediately easier to get all my interfaces to work together. one day i’m struggling with drivers and the next day everything worked. it was a festivus miracle.

    • oh lord, those were the days. Trying to sync cubase midi with Tascam tapes… Madness

      • Remember upgrading Digidesign PCI cards in expansion bays, while we’re at it?

        Or SCSI problems?

        Or… I could go on. Memories… 🙂

        • I also remember the first day I came to the studio with the whole session on an usb key. Paradise

        • Oooh lawd we came from far away

    • wetterberg

      aw hell – just had army-style PTSD flashbacks to setting up opcode systems back in the previous century… It very nearly killed me.

  • Gunboat_Diplo

    The Final Frontier is criminally underrated in the Star Trek canon.
    And all those damn kids complaining about OS upgrades weren’t around in the days of trying to get MIDI interfaces to even speak with OS9.

    • Yes, though Final Frontier did keep the ‘odd number’ curse going. 😉 Speaking of which, have we worked out what the current rule is for OS X operating systems on that?

      • Gunboat_Diplo

        OSes are so stable now, I suppose its more like trying to pick your favorite season of the Simpsons: either you go with early seasons/updates that are consistent and stripped down or you go with later seasons/updates that occasionally have a great new characters/features but otherwise are just tinkering with the current formula.
        i’ll just never forget OSX made it immediately easier to get all my interfaces to work together. one day i’m struggling with drivers and the next day everything worked. it was a festivus miracle.

    • oh lord, those were the days. Trying to sync cubase midi with Tascam tapes… Madness

      • Remember upgrading Digidesign PCI cards in expansion bays, while we’re at it?

        Or SCSI problems?

        Or… I could go on. Memories… 🙂

        • I also remember the first day I came to the studio with the whole session on an usb key. Paradise

        • Oooh lawd we came from far away

    • wetterberg

      aw hell – just had army-style PTSD flashbacks to setting up opcode systems back in the previous century… It very nearly killed me.

  • experimentaldog

    The solution of an El Capitan fail is of course Mr. Spock in jet boots. I hope the Spock update comes soon… https://www.youtube.com/watch?v=7XDFEv74DCo

    • Thank you. *That’s* the video I wanted.

      • experimentaldog

        I deleted my original post because of redundancy since you posted it. But yes I’ll definitely need Spock in jet boots to save my plugins from crashing.

  • misksound

    pretty sure NI doesn’t start testing their software with OS X updates until they hit GM status!

    • Well, when it comes to qualification of updates, though, that’s true of everyone – because things do sometimes change right through GM. Now, some are indeed *compatible* earlier, or start making testing/compatibility changes earlier. It’s a tricky business. Start early, risk doing extra work. Start late, and fall out of sync with the update. I can’t really pretend to judge.

      • Americatown

        More likely, they start testing their software once it goes into beta, and keep testing their software through GM in the hope that Apple fixes whatever issue is holding the product back.

      • jef

        That makes sense. It is still frustrating considering NI is a huge part of Logic for many people. It seems like Apple could be communicating with NI about the components it is updating, though maybe NI’s Mac userbase is small enough that they aren’t too worried about it. NI plugins have been broken since the 10.11 betas started. My reverb plugins have been working fine though (Valhalla, PSP, Aegean).

      • I’ll judge. Developers have had 8 betas plus a GM to start testing but once again, people beat up on Apple when it’s really the developers who’ve been slacking off since June.

        Apple specifically pushes out prelease releases—8 of them in fact plus a GM— so developers aren’t blindsided when the final version is released. It’s funny when people say “Apple doesn’t listen” but those same developers never participate in the betas until it’s all firmed up.

        It’s really a missed opportunity to instill some confidence in your customers as well as riding the wave of “hey we’re ready to go on El Cap! We’re proactive!” Even Adobe, hated by many, has certified their apps to go for El Capitan. People slated Adobe on this years ago and they’ve finally listened.

        • Maintenance release – maybe yes. But it still has a lot of significant changes under the hood. The review over at Ars goes pretty deep into details about that (http://arstechnica.com/apple/2015/09/os-x-10-11-el-capitan-the-ars-technica-review/). Working in a software development team myself, I second Peter’s opinion about the difficulties of hitting the “right” timing.

          Still, as an end user, I fnd it annoying too that large commercial software vendors don’t get their products ready in time. But it might simply not be that easy.

          • Same song and dance every year; I think corporate culture has something to do with it. They’d rather be reactive than proactive. “Let’s wait to see how many complaints we get before we start digging into this…” Especially if you’re relatively close to a new release, “why spend time working on old code when you can sell new code to customers” says marketing.

            It used to be only the biggest developers could get access to prerelease seeds which was the biggest problem. You’d have to wait until a public beta to even start testing. Now anyone who spends $100 on a developer subscription gets access to every release of iOS and OS X.

            By the third or 4th beta, all the major changes or bugs in APIs are pretty well settled in. The betas are there to chase edge case bugs in the new APIs.

      • misksound

        agreed, and having installed a few betas of 10.11 on an external drive, you could see that most changes in 10.11 are ‘under the hood’—which means it’s not going to be as simple for a developer to just port existing software to the new OS. For the record though, been using reaktor since 2003, and it speaks highly of NI that they’d rather get it right, than rush anything.

  • misksound

    pretty sure NI doesn’t start testing their software with OS X updates until they hit GM status!

    • Well, when it comes to qualification of updates, though, that’s true of everyone – because things do sometimes change right through GM. Now, some are indeed *compatible* earlier, or start making testing/compatibility changes earlier. It’s a tricky business. Start early, risk doing extra work. Start late, and fall out of sync with the update. I can’t really pretend to judge.

      • Americatown

        More likely, they start testing their software once it goes into beta, and keep testing their software through GM in the hope that Apple fixes whatever issue is holding the product back.

      • jef

        That makes sense. It is still frustrating considering NI is a huge part of Logic for many people. It seems like Apple could be communicating with NI about the components it is updating, though maybe NI’s Mac userbase is small enough that they aren’t too worried about it. NI plugins have been broken since the 10.11 betas started. My reverb plugins have been working fine though (Valhalla, PSP, Aegean).

      • I’ll judge. Developers have had 8 betas plus a GM to start testing but once again, people beat up on Apple when it’s really the developers who’ve been slacking off since June.

        Apple specifically pushes out prelease releases so developers aren’t blindsided when the final version is released. It’s funny when people say “Apple doesn’t listen” but those same developers probably never participate in the betas until it’s close to firmed up.

        It’s really a missed opportunity to instill some confidence in your customers as well as riding the wave of “hey we’re ready to go on El Cap! We’re proactive!” Even Adobe, hated by many, has certified their apps to go for El Capitan. People slated Adobe on this years ago and they’ve finally listened.

        Especially considering Apple is billing this as more of a refined, maintenance release without that many features, users are going to expect that it’s going to be a safer upgrade and go ahead with it.

        • Maintenance release – maybe yes. But it still has a lot of significant changes under the hood. The review over at Ars goes pretty deep into details about that (http://arstechnica.com/apple/2015/09/os-x-10-11-el-capitan-the-ars-technica-review/). Working in a software development team myself, I second Peter’s opinion about the difficulties of hitting the “right” timing.

          Still, as an end user, I fnd it annoying too that large commercial software vendors don’t get their products ready in time. But it might simply not be that easy.

          • Same song and dance every year; I think corporate culture has something to do with it. They’d rather be reactive than proactive. “Let’s wait to see how many complaints we get before we start digging into this…” Especially if you’re relatively close to a new release, “why spend time working on old code when you can sell new code to customers” says marketing.

            It used to be only the biggest developers could get access to prerelease seeds which was the biggest problem. You’d have to wait until a public beta to even start testing. Now anyone who spends $100 on a developer subscription gets access to every release of iOS and OS X.

            By the third or 4th beta, all the major changes or bugs in APIs are pretty well settled in. The betas are there to chase edge case bugs in the new APIs.

      • misksound

        agreed, and having installed a few betas of 10.11 on an external drive, you could see that most changes in 10.11 are ‘under the hood’—which means it’s not going to be as simple for a developer to just port existing software to the new OS. For the record though, been using reaktor since 2003, and it speaks highly of NI that they’d rather get it right, than rush anything.

  • misksound

    pretty sure NI doesn’t start testing their software with OS X updates until they hit GM status!

    • Well, when it comes to qualification of updates, though, that’s true of everyone – because things do sometimes change right through GM. Now, some are indeed *compatible* earlier, or start making testing/compatibility changes earlier. It’s a tricky business. Start early, risk doing extra work. Start late, and fall out of sync with the update. I can’t really pretend to judge.

      • Americatown

        More likely, they start testing their software once it goes into beta, and keep testing their software through GM in the hope that Apple fixes whatever issue is holding the product back.

      • jef

        That makes sense. It is still frustrating considering NI is a huge part of Logic for many people. It seems like Apple could be communicating with NI about the components it is updating, though maybe NI’s Mac userbase is small enough that they aren’t too worried about it. NI plugins have been broken since the 10.11 betas started. My reverb plugins have been working fine though (Valhalla, PSP, Aegean).

      • I’ll judge. Developers have had 8 betas plus a GM to start testing but once again, people beat up on Apple when it’s really the developers who’ve been slacking off since June.

        Apple specifically pushes out prelease releases so developers aren’t blindsided when the final version is released. It’s funny when people say “Apple doesn’t listen” but those same developers probably never participate in the betas until it’s close to firmed up.

        It’s really a missed opportunity to instill some confidence in your customers as well as riding the wave of “hey we’re ready to go on El Cap! We’re proactive!” Even Adobe, hated by many, has certified their apps to go for El Capitan. People slated Adobe on this years ago and they’ve finally listened.

        Especially considering Apple is billing this as more of a refined, maintenance release without that many features, users are going to expect that it’s going to be a safer upgrade and go ahead with it.

        • Maintenance release – maybe yes. But it still has a lot of significant changes under the hood. The review over at Ars goes pretty deep into details about that (http://arstechnica.com/apple/2015/09/os-x-10-11-el-capitan-the-ars-technica-review/). Working in a software development team myself, I second Peter’s opinion about the difficulties of hitting the “right” timing.

          Still, as an end user, I fnd it annoying too that large commercial software vendors don’t get their products ready in time. But it might simply not be that easy.

          • Same song and dance every year; I think corporate culture has something to do with it. They’d rather be reactive than proactive. “Let’s wait to see how many complaints we get before we start digging into this…” Especially if you’re relatively close to a new release, “why spend time working on old code when you can sell new code to customers” says marketing.

            It used to be only the biggest developers could get access to prerelease seeds which was the biggest problem. You’d have to wait until a public beta to even start testing. Now anyone who spends $100 on a developer subscription gets access to every release of iOS and OS X.

            By the third or 4th beta, all the major changes or bugs in APIs are pretty well settled in. The betas are there to chase edge case bugs in the new APIs.

      • misksound

        agreed, and having installed a few betas of 10.11 on an external drive, you could see that most changes in 10.11 are ‘under the hood’—which means it’s not going to be as simple for a developer to just port existing software to the new OS. For the record though, been using reaktor since 2003, and it speaks highly of NI that they’d rather get it right, than rush anything.

  • Aaron Levitz

    Thank you for posting this!

    One of my favorite Audio Units (Magical8bitPlug) broke nearly every iteration of my Ableton performance set and all of its backups last week. I’ve been racking my brain trying to figure out what changed. There it is.

    • Gunboat_Diplo

      Magical8bitPlug is awesome. and free.

      • Aaron Levitz

        It is. And it is. But I had to delete it for the time being because none of my files which reference it will open otherwise. I have three shows this weekend, so not discovering the problem sooner could have been bad.

        • Stephan Vankov

          Probably not a good idea to update your OS the week before you have to play 3 shows! I finally updated to 10.10…. from 10.6. If it aint broke, don’t fix it!

          • Aaron Levitz

            I’m now told that El Capitan hasn’t launched yet, which would explain why I don’t remember installing it — I didn’t. (only beta testers currently have access) I’m guessing this broke with a simple patch release. I’ve never had reason to question those before.

            (and it was really two weeks before the show. everything collapsed at rehearsal last Monday.)

        • trash80

          It could be a Ableton 9.2 issue, 9.2 has broke nearly all of my old “classic” plugins that are out of date, basically it crashes Ableton instantly and makes me shoot lasers from my eyes.

          • Aaron Levitz

            We’ve played a show or two since the 9.2 upgrade. It’s hard to pinpoint which component became incompatible with the others, but I’m pretty sure there wasn’t a change in my Ableton software.

  • Aaron Levitz

    Thank you for posting this!

    One of my favorite Audio Units (Magical8bitPlug) broke nearly every iteration of my Ableton performance set and all of its backups last week. I’ve been racking my brain trying to figure out what changed. There it is.

    • Gunboat_Diplo

      Magical8bitPlug is awesome. and free.

      • Aaron Levitz

        It is. And it is. But I had to delete it for the time being because none of my files which reference it will open otherwise. I have three shows this weekend, so not discovering the problem sooner could have been bad.

        • Stephan Vankov

          Probably not a good idea to update your OS the week before you have to play 3 shows! I finally updated to 10.10…. from 10.6. If it aint broke, don’t fix it!

          • Aaron Levitz

            I’m now told that El Capitan hasn’t launched yet, which would explain why I don’t remember installing it — I didn’t. (only beta testers currently have access) I’m guessing this broke with a simple patch release. I’ve never had reason to question those before.

            (and it was really two weeks before the show. everything collapsed at rehearsal last Monday.)

        • trash80

          It could be a Ableton 9.2 issue, 9.2 has broke nearly all of my old “classic” plugins that are out of date, basically it crashes Ableton instantly and makes me shoot lasers from my eyes.

          • Aaron Levitz

            We’ve played a show or two since the 9.2 upgrade. It’s hard to pinpoint which component became incompatible with the others, but I’m pretty sure there wasn’t a change in my Ableton software.

  • Aaron Levitz

    Thank you for posting this!

    One of my favorite Audio Units (Magical8bitPlug) broke nearly every iteration of my Ableton performance set and all of its backups last week. I’ve been racking my brain trying to figure out what changed. There it is.

    • Gunboat_Diplo

      Magical8bitPlug is awesome. and free.

      • Aaron Levitz

        It is. And it is. But I had to delete it for the time being because none of my files which reference it will open otherwise. I have three shows this weekend, so not discovering the problem sooner could have been bad.

        • Stephan Vankov

          Probably not a good idea to update your OS the week before you have to play 3 shows! I finally updated to 10.10…. from 10.6. If it aint broke, don’t fix it!

          • Aaron Levitz

            I’m now told that El Capitan hasn’t launched yet, which would explain why I don’t remember installing it — I didn’t. (only beta testers currently have access) I’m guessing this broke with a simple patch release. I’ve never had reason to question those before.

            (and it was really two weeks before the show. everything collapsed at rehearsal last Monday.)

        • trash80

          It could be a Ableton 9.2 issue, 9.2 has broke nearly all of my old “classic” plugins that are out of date, basically it crashes Ableton instantly and makes me shoot lasers from my eyes.

          • Aaron Levitz

            We’ve played a show or two since the 9.2 upgrade. It’s hard to pinpoint which component became incompatible with the others, but I’m pretty sure there wasn’t a change in my Ableton software.

  • Peter, why don’t you just paste the same OS upgrade article again next time? Just to see if anyone notices?

    Err… Ok, just kidding. But regarding the Shatner thing: Here’s something that fits too, in a way. Track 13… https://itun.es/dk/F-3M6

  • Peter, why don’t you just paste the same OS upgrade article again next time? Just to see if anyone notices?

    Err… Ok, just kidding. But regarding the Shatner thing: Here’s something that fits too, in a way. https://youtube.com/watch?v=-YA5J88ik64

  • Peter, why don’t you just paste the same OS upgrade article again next time? Just to see if anyone notices?

    Err… Ok, just kidding. But regarding the Shatner thing: Here’s something that fits too, in a way. https://youtube.com/watch?v=-YA5J88ik64

  • Will

    Only one post tagged “shatner”? http://createdigitalmusic.com/tag/shatner/ How is that even possible?

  • Will

    Only one post tagged “shatner”? http://createdigitalmusic.com/tag/shatner/ How is that even possible?

  • Will

    Only one post tagged “shatner”? http://createdigitalmusic.com/tag/shatner/ How is that even possible?

  • botsauce

    I found that the problem is the AU authorizer. Here’s a fix that worked for me:
    https://www.native-instruments.com/forum/threads/how-to-fix-el-capitan-beta-problems-crashing-logic-au-scan.261838/
    (This doesn’t fix hardware problems though.)

  • botsauce

    I found that the problem is the AU authorizer. Here’s a fix that worked for me:
    https://www.native-instruments.com/forum/threads/how-to-fix-el-capitan-beta-problems-crashing-logic-au-scan.261838/
    (This doesn’t fix hardware problems though.)

  • botsauce

    I found that the problem is the AU authorizer. Here’s a fix that worked for me:
    https://www.native-instruments.com/forum/threads/how-to-fix-el-capitan-beta-problems-crashing-logic-au-scan.261838/
    (This doesn’t fix hardware problems though.)

  • RangerJay

    Don’t get me started on Gibson and Studio Vision!

  • RangerJay

    Don’t get me started on Gibson and Studio Vision!

  • RangerJay

    Don’t get me started on Gibson and Studio Vision!

  • Freeks

    Why upgrade in the first place?

    Does El Capitan bring something new for music applications?

    I’m running 10.10.3. If i remember correctly some of the earlier versions were in .8 or something before new version came.

    El Capitan indeed works a bit different. Colleague of mine upgraded and now he can’t access all system folders even tough he is Admin. We were joking that now you need to call Apple every time you want to make system changes. After some googling that might even be so 😀

    • milo

      Yes, the AU standard has been updated. Some new functionality and things like running the plugin code external to the app so a plugin crash doesn’t crash Logic or Cubase. And overall better system performance and stability, this is basically another Snow Leopard to tighten up the last couple OS X versions.

  • Freeks

    Why upgrade in the first place?

    Does El Capitan bring something new for music applications?

    I’m running 10.10.3. If i remember correctly some of the earlier versions were in .8 or something before new version came.

    El Capitan indeed works a bit different. Colleague of mine upgraded and now he can’t access all system folders even tough he is Admin. We were joking that now you need to call Apple every time you want to make system changes. After some googling that might even be so 😀

    • milo

      Yes, the AU standard has been updated. Some new functionality and things like running the plugin code external to the app so a plugin crash doesn’t crash Logic or Cubase. And overall better system performance and stability, this is basically another Snow Leopard to tighten up the last couple OS X versions.

  • Freeks

    Why upgrade in the first place?

    Does El Capitan bring something new for music applications?

    I’m running 10.10.3. If i remember correctly some of the earlier versions were in .8 or something before new version came.

    El Capitan indeed works a bit different. Colleague of mine upgraded and now he can’t access all system folders even tough he is Admin. We were joking that now you need to call Apple every time you want to make system changes. After some googling that might even be so 😀

    • milo

      Yes, the AU standard has been updated. Some new functionality and things like running the plugin code external to the app so a plugin crash doesn’t crash Logic or Cubase. And overall better system performance and stability, this is basically another Snow Leopard to tighten up the last couple OS X versions.

  • All jokes about Apple / OSX aside, the Windows 10 upgrade is bringing all the same concerns with compatibility but according to Pete Brown at Microsoft, the upgrade has been designed to involve as few problems as possible.

    https://www.youtube.com/watch?v=LHaz3p_H8iM

  • All jokes about Apple / OSX aside, the Windows 10 upgrade is bringing all the same concerns with compatibility but according to Pete Brown at Microsoft, the upgrade has been designed to involve as few problems as possible.

    https://www.youtube.com/watch?v=LHaz3p_H8iM

  • All jokes about Apple / OSX aside, the Windows 10 upgrade is bringing all the same concerns with compatibility but according to Pete Brown at Microsoft, the upgrade has been designed to involve as few problems as possible.

    https://www.youtube.com/watch?v=LHaz3p_H8iM

  • Finale has advised users not to upgrade to El Capitan at the moment.

    “we’ve discovered some new incompatibilities with Finale 2014d. Specifically, opening certain dialog boxes (involving expressions, articulations, and others) can cause Finale to crash.

    …at this point we advise against upgrading to El Capitan immediately upon its release. If the solution is on our end we will address it with Finale 2014.5, which we plan to release by the end of November”

    2015.http://www.finalemusic.com/blog/finale-and-os-x-el-capitan/

  • Finale has advised users not to upgrade to El Capitan at the moment.

    “we’ve discovered some new incompatibilities with Finale 2014d. Specifically, opening certain dialog boxes (involving expressions, articulations, and others) can cause Finale to crash.

    …at this point we advise against upgrading to El Capitan immediately upon its release. If the solution is on our end we will address it with Finale 2014.5, which we plan to release by the end of November”

    2015.http://www.finalemusic.com/blog/finale-and-os-x-el-capitan/

  • Finale has advised users not to upgrade to El Capitan at the moment.

    “we’ve discovered some new incompatibilities with Finale 2014d. Specifically, opening certain dialog boxes (involving expressions, articulations, and others) can cause Finale to crash.

    …at this point we advise against upgrading to El Capitan immediately upon its release. If the solution is on our end we will address it with Finale 2014.5, which we plan to release by the end of November”

    2015.http://www.finalemusic.com/blog/finale-and-os-x-el-capitan/

  • The “back in the day” bit is too funny. Longtime users like me (and I’m sure you, too) know differently. Pre-OS X updates would break extensions all the time. OS 9 caused a global panic when it was released and broke Adobe fonts. And how about the “some things will work but not others” nightmare of trying to run legacy OS 9 apps in early OS X’s virtual “Classic” environment? This is SOP and nothing new.

    • just_parsley

      oh geez I remember that — what a nightmare. It was like throwing a rock into a still lake… you’d just stand there and watch the ripple effect…

      Nowadays I just wait a month or so before updating. I figure that’s enough time for them to fix issues (the app companies AND Apple) or enough time for me to learn what the problems will be if I update.

    • Tribeless

      To hell with Mac OS updates breaking extensions. Back in the day, it was invariably extensions that broke Mac OS.

      Wasn’t there a utility for testing Extensions compatibility?

      • C&G’s Conflict Catcher was what I used back in OS 9.

    • Jonnie Fuckin Rockit

      yeah k, just about ever iteration of OSX and even before it with OS 9 and previous… every SINGLE UPDATE had it’s own brand of suicide inducing issues… He must have been thinking about WINDOWS because as long as I can remember Windows NEVER killed the NIC card of its host computer, but then again you had to PAY FOR a windblows update.

  • The “back in the day” bit is too funny. Longtime users like me (and I’m sure you, too) know differently. Pre-OS X updates would break extensions all the time. OS 9 caused a global panic when it was released and broke Adobe fonts. And how about the “some things will work but not others” nightmare of trying to run legacy OS 9 apps in early OS X’s virtual “Classic” environment? This is SOP and nothing new.

    • just_parsley

      oh geez I remember that — what a nightmare. It was like throwing a rock into a still lake… you’d just stand there and watch the ripple effect…

      Nowadays I just wait a month or so before updating. I figure that’s enough time for them to fix issues (the app companies AND Apple) or enough time for me to learn what the problems will be if I update.

    • Tribeless

      To hell with Mac OS updates breaking extensions. Back in the day, it was invariably extensions that broke Mac OS.

      Wasn’t there a utility for testing Extensions compatibility?

      • C&G’s Conflict Catcher was what I used back in OS 9.

    • Jonnie Fuckin Rockit

      yeah k, just about ever iteration of OSX and even before it with OS 9 and previous… every SINGLE UPDATE had it’s own brand of suicide inducing issues… He must have been thinking about WINDOWS because as long as I can remember Windows NEVER killed the NIC card of its host computer, but then again you had to PAY FOR a windblows update.

  • The “back in the day” bit is too funny. Longtime users like me (and I’m sure you, too) know differently. Pre-OS X updates would break extensions all the time. OS 9 caused a global panic when it was released and broke Adobe fonts. And how about the “some things will work but not others” nightmare of trying to run legacy OS 9 apps in early OS X’s virtual “Classic” environment? This is SOP and nothing new.

    • just_parsley

      oh geez I remember that — what a nightmare. It was like throwing a rock into a still lake… you’d just stand there and watch the ripple effect…

      Nowadays I just wait a month or so before updating. I figure that’s enough time for them to fix issues (the app companies AND Apple) or enough time for me to learn what the problems will be if I update.

    • Tribeless

      To hell with Mac OS updates breaking extensions. Back in the day, it was invariably extensions that broke Mac OS.

      Wasn’t there a utility for testing Extensions compatibility?

      • C&G’s Conflict Catcher was what I used back in OS 9.

    • Jonnie Fuckin Rockit

      yeah k, just about ever iteration of OSX and even before it with OS 9 and previous… every SINGLE UPDATE had it’s own brand of suicide inducing issues… He must have been thinking about WINDOWS because as long as I can remember Windows NEVER killed the NIC card of its host computer, but then again you had to PAY FOR a windblows update.

  • JetBelly Music

    IZotope Ozone 6 broke on my test system (But oddly, 5 is fine)

  • JetBelly Music

    IZotope Ozone 6 broke on my test system (But oddly, 5 is fine)

  • JetBelly Music

    IZotope Ozone 6 broke on my test system (But oddly, 5 is fine)

  • Daniel

    Damn you, El Capitan.

    A warning to all: this has broken Logic Pro for me.

    I’m now experiencing crackling with my NI Audio Kontrol 1 (no surprises there, it’s an annual affair with a new OS) but worse, frequent crashes of Logic.

    Apparently as soon as I try to open third party instruments – particularly Izotope’s iDrum – it freaks everything out. Then that project file is rendered totally unusable and I have to choose a backup.

    I KNOW I KNOW don’t upgrade. But I was tempted by the claims of better graphical performance, which has been dogging my Logic Pro sessions for a while.

    Damnation. I have no recourse. For now.

    • Matt

      Bad news from NI Support:

      “Given that the AK1 is a discontinued product, it would not be highest on the priority list of drivers which need updating for Apple´s new OS. Apologies for the inconvenience.”

      • Daniel

        Thanks Matt!

        Yeah I figured as much. It’s a great shame because I love the AK1. But that’s not how capitalism works…

        How about a new system where a company makes a ROCK SOLID FOR LIFE product, and I pay a subscription. Sort of a lease-lend agreement. Then I don’t need to keep spending money for “free” upgrades.

        iDrum is discontinued as well, but there’s no decent modern alternative in my view.

        I’ve actually reinstalled Yosemite as El Capitan just wasn’t doing it for me

  • Daniel

    Damn you, El Capitan.

    A warning to all: this has broken Logic Pro for me.

    I’m now experiencing crackling with my NI Audio Kontrol 1 (no surprises there, it’s an annual affair with a new OS) but worse, frequent crashes of Logic.

    Apparently as soon as I try to open third party instruments – particularly Izotope’s iDrum – it freaks everything out. Then that project file is rendered totally unusable and I have to choose a backup.

    I KNOW I KNOW don’t upgrade. But I was tempted by the claims of better graphical performance, which has been dogging my Logic Pro sessions for a while.

    Damnation. I have no recourse. For now.

    • Matt

      Bad news from NI Support:

      “Given that the AK1 is a discontinued product, it would not be highest on the priority list of drivers which need updating for Apple´s new OS. Apologies for the inconvenience.”

      • Daniel

        Thanks Matt!

        Yeah I figured as much. It’s a great shame because I love the AK1. But that’s not how capitalism works…

        How about a new system where a company makes a ROCK SOLID FOR LIFE product, and I pay a subscription. Sort of a lease-lend agreement. Then I don’t need to keep spending money for “free” upgrades.

        iDrum is discontinued as well, but there’s no decent modern alternative in my view.

        I’ve actually reinstalled Yosemite as El Capitan just wasn’t doing it for me

  • Cameron Stephens

    Damn you, El Capitan.

    A warning to all: this has broken Logic Pro for me.

    I’m now experiencing crackling with my NI Audio Kontrol 1 (no surprises there, it’s an annual affair with a new OS) but worse, frequent crashes of Logic.

    Apparently as soon as I try to open third party instruments – particularly Izotope’s iDrum – it freaks everything out. Then that project file is rendered totally unusable and I have to choose a backup.

    I KNOW I KNOW don’t upgrade. But I was tempted by the claims of better graphical performance, which has been dogging my Logic Pro sessions for a while.

    Damnation. I have no recourse. For now.

    • Matt

      Bad news from NI Support:

      “Given that the AK1 is a discontinued product, it would not be highest on the priority list of drivers which need updating for Apple´s new OS. Apologies for the inconvenience.”

      • Cameron Stephens

        Thanks Matt!

        Yeah I figured as much. It’s a great shame because I love the AK1. But that’s not how capitalism works…

        How about a new system where a company makes a ROCK SOLID FOR LIFE product, and I pay a subscription. Sort of a lease-lend agreement. Then I don’t need to keep spending money for “free” upgrades.

        iDrum is discontinued as well, but there’s no decent modern alternative in my view.

        I’ve actually reinstalled Yosemite as El Capitan just wasn’t doing it for me

  • Mikhail Myasoedov

    Have anyone tried old firewire Apogee Ensemble with El Capitan? Apogee says that they don’t plan to update drivers for ensemble, but maybe it is still working?

  • Mikhail Myasoedov

    Have anyone tried old firewire Apogee Ensemble with El Capitan? Apogee says that they don’t plan to update drivers for ensemble, but maybe it is still working?

  • Mikhail Myasoedov

    Have anyone tried old firewire Apogee Ensemble with El Capitan? Apogee says that they don’t plan to update drivers for ensemble, but maybe it is still working?

  • Talon Patience

    From what I can tell, El Capitan has broken my Tascam UH-7000. There is now no audio functionality at all using the unit. I have emailed Tascam (TEAC) to see if they have any information. I was thoughtless with this upgrade, clearly.

    • Talon Patience

      Tascam emailed and said the following:

      “As the official version of El Capitan was recently released, we are in the process of testing the compatibility of various models. Once we have the final results (hopefully by the end of the month), they will be posted in the NEWS section of the website.”

      • Talon Patience

        On October 22nd, they said:

        “TASCAM has just posted El Capitan drivers for the US-2×2 and US-4×4, download those on our site. We have also posted a BETA driver for the US-1800. This US-1800 driver is for El Capitan only.

        The current US-2×2, US-4×4, US-16×08, and US-20×20 drivers are compatible with Windows 10 and OSX 10.11 El Capitan. Work on other interfaces continues and we hope to have another update soon.”

  • Talon Patience

    From what I can tell, El Capitan has broken the interface functionality for my Tascam UH-7000. There is now no audio interface functionality at all using the unit (though it still works in stand-alone mode). I have emailed Tascam (TEAC) to see if they have any information. I was thoughtless with this upgrade, clearly.

    • Talon Patience

      Tascam emailed and said the following:

      “As the official version of El Capitan was recently released, we are in the process of testing the compatibility of various models. Once we have the final results (hopefully by the end of the month), they will be posted in the NEWS section of the website.”

      • Talon Patience

        On October 22nd, they said:

        “TASCAM has just posted El Capitan drivers for the US-2×2 and US-4×4, download those on our site. We have also posted a BETA driver for the US-1800. This US-1800 driver is for El Capitan only.

        The current US-2×2, US-4×4, US-16×08, and US-20×20 drivers are compatible with Windows 10 and OSX 10.11 El Capitan. Work on other interfaces continues and we hope to have another update soon.”

  • Talon Patience

    From what I can tell, El Capitan has broken the interface functionality for my Tascam UH-7000. There is now no audio interface functionality at all using the unit (though it still works in stand-alone mode). I have emailed Tascam (TEAC) to see if they have any information. I was thoughtless with this upgrade, clearly.

    • Talon Patience

      Tascam emailed and said the following:

      “As the official version of El Capitan was recently released, we are in the process of testing the compatibility of various models. Once we have the final results (hopefully by the end of the month), they will be posted in the NEWS section of the website.”

      • Talon Patience

        On October 22nd, they said:

        “TASCAM has just posted El Capitan drivers for the US-2×2 and US-4×4, download those on our site. We have also posted a BETA driver for the US-1800. This US-1800 driver is for El Capitan only.

        The current US-2×2, US-4×4, US-16×08, and US-20×20 drivers are compatible with Windows 10 and OSX 10.11 El Capitan. Work on other interfaces continues and we hope to have another update soon.”

  • yikesboy

    For Cubase/Nuendo folks, wait. Steinberg has also advised that El Capitan is not compatible.

  • yikesboy

    For Cubase/Nuendo folks, wait. Steinberg has also advised that El Capitan is not compatible.

  • yikesboy

    For Cubase/Nuendo folks, wait. Steinberg has also advised that El Capitan is not compatible.

  • John Geaney

    Guitar Rig Session IO is busted as well – seems to work ok so long as nothing else that needs audio is running – bummer.

    • Andreas Kosch

      If only I had read that BEFORE updating…Sigh. Have you found a solution for the session to work under 10.11?

      • John

        No Fix so far. I contacted Native Instruments and they replied that they could not indicate when – or even if – a fix would be forthcoming. Needless to say NI are now at the bottom of my list the considering any new audio apps or devices!

        • Andreas Kosch

          It is a mess. I asked them, if there is a way to install the 2.8 drivers for the session but i doubt that they even WANT that…I am obviously supposed to throw away a perfectly working and nicely built interface in favour of their audio 6…now, that won’t happen, i will rather try to downgrade via Timemachine.

          • Andreas Kosch

            Took my TM Backup and went back to 10.10….no big deal but lot of time wasted due to the information policy of NI. Why can’t they clearly state on their website that the session I/O and other older, dicontinued and therefore totally ignored ex-products are NOT working with the newest software…I wouldn’t blame them.

          • John

            So, I junked the Session IO – just installed a Focusrite Scarlett 2i4 – works fine. Thanks NI, thanks Apple.

  • John Geaney

    Guitar Rig Session IO is busted as well – seems to work ok so long as nothing else that needs audio is running – bummer.

    • Andreas Kosch

      If only I had read that BEFORE updating…Sigh. Have you found a solution for the session to work under 10.11?

      • John

        No Fix so far. I contacted Native Instruments and they replied that they could not indicate when – or even if – a fix would be forthcoming. Needless to say NI are now at the bottom of my list the considering any new audio apps or devices!

        • Andreas Kosch

          It is a mess. I asked them, if there is a way to install the 2.8 drivers for the session but i doubt that they even WANT that…I am obviously supposed to throw away a perfectly working and nicely built interface in favour of their audio 6…now, that won’t happen, i will rather try to downgrade via Timemachine.

          • Andreas Kosch

            Took my TM Backup and went back to 10.10….no big deal but lot of time wasted due to the information policy of NI. Why can’t they clearly state on their website that the session I/O and other older, dicontinued and therefore totally ignored ex-products are NOT working with the newest software…I wouldn’t blame them.

          • John

            So, I junked the Session IO – just installed a Focusrite Scarlett 2i4 – works fine. Thanks NI, thanks Apple.

          • $pitInk

            straight up man, thats bullshit im in the same boat it can happen with any mic or audio plug in it looks like i have 2 mics and an audio board all effected by this bullshit

  • John Geaney

    Guitar Rig Session IO is busted as well – seems to work ok so long as nothing else that needs audio is running – bummer.

    • Andreas Kosch

      If only I had read that BEFORE updating…Sigh. Have you found a solution for the session to work under 10.11?

      • John

        No Fix so far. I contacted Native Instruments and they replied that they could not indicate when – or even if – a fix would be forthcoming. Needless to say NI are now at the bottom of my list the considering any new audio apps or devices!

        • Andreas Kosch

          It is a mess. I asked them, if there is a way to install the 2.8 drivers for the session but i doubt that they even WANT that…I am obviously supposed to throw away a perfectly working and nicely built interface in favour of their audio 6…now, that won’t happen, i will rather try to downgrade via Timemachine.

          • Andreas Kosch

            Took my TM Backup and went back to 10.10….no big deal but lot of time wasted due to the information policy of NI. Why can’t they clearly state on their website that the session I/O and other older, dicontinued and therefore totally ignored ex-products are NOT working with the newest software…I wouldn’t blame them.

          • John

            So, I junked the Session IO – just installed a Focusrite Scarlett 2i4 – works fine. Thanks NI, thanks Apple.

          • $pitInk

            straight up man, thats bullshit im in the same boat it can happen with any mic or audio plug in it looks like i have 2 mics and an audio board all effected by this bullshit

  • L e s l i e

    Happy to report that Apogee Duet FireWire although no longer supported, works just fine 🙂

  • L e s l i e

    Happy to report that Apogee Duet FireWire although no longer supported, works just fine 🙂

  • L e s l i e

    Happy to report that Apogee Duet FireWire although no longer supported, works just fine 🙂

  • Damien356

    i discovered that in el capitan all my virtual audio devices such as soundflower or wavetab wont work anymore… they aren’t even listed in the system preferences audio menu. reinstalling them always gives me an error during the installation routine. i used these virtual devices a lot to patch sound between applications. any ideas how to get it running again?

    greetz from germany

  • Damien356

    i discovered that in el capitan all my virtual audio devices such as soundflower or wavetab wont work anymore… they aren’t even listed in the system preferences audio menu. reinstalling them always gives me an error during the installation routine. i used these virtual devices a lot to patch sound between applications. any ideas how to get it running again?

    greetz from germany

  • Damien356

    i discovered that in el capitan all my virtual audio devices such as soundflower or wavetab wont work anymore… they aren’t even listed in the system preferences audio menu. reinstalling them always gives me an error during the installation routine. i used these virtual devices a lot to patch sound between applications. any ideas how to get it running again?

    greetz from germany

  • Mo Ham

    OS 7 was the best. It just worked. PT3 Studio Vision, ahh… those was the days.

  • Mo Ham

    OS 7 was the best. It just worked. PT3 Studio Vision, ahh… those was the days.

  • Mo Ham

    OS 7 was the best. It just worked. PT3 Studio Vision, ahh… those was the days.

  • queeky

    Ran into problems with the drivers for the US-144 MK II: while audio works, the system becomes repeatedly unresponsive even under normal use (not even using audio software). Looking at the OSX console, it appears that hundreds of errors are being generated every second. I have taken a screenshot:

    http://jonathanfield.com/foo/tascam.png

    This keep scrolling by continuously whenever the Tascam device is plugged in. Removing the driver or unplugging the device causes the errors to stop and the system to become more responsive. Re-installing the driver or plugging the device back in causes the errors to resume and the system to become less responsive again.

    Just thought I’d mention this to save others the trouble of finding out. Having the Tascam unit plugged in makes your system nearly unusable.

    • Christoph DXer

      Same problem here in Austria with my Mac Pro and the US-144 MK II.. Did not find any solution what to do…

      • Антон Помелов

        same trouble, i hear the clicks((

  • queeky

    Ran into problems with the drivers for the US-144 MK II: while audio works, the system becomes repeatedly unresponsive even under normal use (not even using audio software). Looking at the OSX console, it appears that hundreds of errors are being generated every second. I have taken a screenshot:

    http://jonathanfield.com/foo/tascam.png

    This keep scrolling by continuously whenever the Tascam device is plugged in. Removing the driver or unplugging the device causes the errors to stop and the system to become more responsive. Re-installing the driver or plugging the device back in causes the errors to resume and the system to become less responsive again.

    Just thought I’d mention this to save others the trouble of finding out. Having the Tascam unit plugged in makes your system nearly unusable.

    • Christoph DXer

      Same problem here in Austria with my Mac Pro and the US-144 MK II.. Did not find any solution what to do…

      • Антон Помелов

        same trouble, i hear the clicks((

  • queeky

    Ran into problems with the drivers for the US-144 MK II: while audio works, the system becomes repeatedly unresponsive even under normal use (not even using audio software). Looking at the OSX console, it appears that hundreds of errors are being generated every second. I have taken a screenshot:

    http://jonathanfield.com/foo/tascam.png

    This keep scrolling by continuously whenever the Tascam device is plugged in. Removing the driver or unplugging the device causes the errors to stop and the system to become more responsive. Re-installing the driver or plugging the device back in causes the errors to resume and the system to become less responsive again.

    Just thought I’d mention this to save others the trouble of finding out. Having the Tascam unit plugged in makes your system nearly unusable.

    • Christoph DXer

      Same problem here in Austria with my Mac Pro and the US-144 MK II.. Did not find any solution what to do…

      • Антон Помелов

        same trouble, i hear the clicks((

  • Stanislav Palyvoda

    iZotope Ozone is completely not working in Logic Pro X. And RX4 pack as well. However everything works in Cubase 8 including NI plugins.

    • Brad Kemp

      I’m assuming this will get fixed right? I’m having the same problem with Ozone not working!

      • Stanislav Palyvoda

        i’ve got Ozone 8 and RX5 both are working fine

  • Stanislav Palyvoda

    iZotope Ozone is completely not working in Logic Pro X. And RX4 pack as well. However everything works in Cubase 8 including NI plugins.

    • Brad Kemp

      I’m assuming this will get fixed right? I’m having the same problem with Ozone not working!

      • Stanislav Palyvoda

        i’ve got Ozone 8 and RX5 both are working fine

  • Stanislav Palyvoda

    iZotope Ozone is completely not working in Logic Pro X. And RX4 pack as well. However everything works in Cubase 8 including NI plugins.

    • Brad Kemp

      I’m assuming this will get fixed right? I’m having the same problem with Ozone not working!

      • Stanislav Palyvoda

        i’ve got Ozone 8 and RX5 both are working fine

  • Nigel Wade

    Pleased I mostly make music on Windows nowadays. Absolutely nothing broke when I upgraded from 7 to 8 or 8 to 10. After Yosemite borking my web development stack and losing me nearly two weeks work trying to fix it I would scream if it happened again.

  • Nigel Wade

    Pleased I mostly make music on Windows nowadays. Absolutely nothing broke when I upgraded from 7 to 8 or 8 to 10. After Yosemite borking my web development stack and losing me nearly two weeks work trying to fix it I would scream if it happened again.

  • Nigel Wade

    Pleased I mostly make music on Windows nowadays. Absolutely nothing broke when I upgraded from 7 to 8 or 8 to 10. After Yosemite borking my web development stack and losing me nearly two weeks work trying to fix it I would scream if it happened again.

  • James

    My Presonus VSL 22 doesn’t work at all with ElCapitan. No input or output possible. I went back to Yosemite. Also, iTunes didn’t work at all, even with internal speakers.

    • Rodney

      How did you go back to Yosemite?

      • James

        I have a Timemachine backup and you can restore to a previous version that way.

  • James

    My Presonus VSL 22 doesn’t work at all with ElCapitan. No input or output possible. I went back to Yosemite. Also, iTunes didn’t work at all, even with internal speakers.

    • Rodney

      How did you go back to Yosemite?

      • James

        I have a Timemachine backup and you can restore to a previous version that way.

  • James

    My Presonus VSL 22 doesn’t work at all with ElCapitan. No input or output possible. I went back to Yosemite. Also, iTunes didn’t work at all, even with internal speakers.

    • Rodney

      How did you go back to Yosemite?

      • James

        I have a Timemachine backup and you can restore to a previous version that way.

  • Hugh Janus

    Hey, I might be late but I found out that you can open Ableton with no crack needed. Just have to click on the terminal file inside the applications folder>Ableton(control click and click on “Package Contents”>Content>Mac OS and in the Mac OS folder if you click on the file called Live, it starts up and works as long as terminal is open. I just randomly discovered this. Hope this helps!

  • 10.11.1 fixes the issue

  • 10.11.1 fixes the issue

  • 10.11.1 fixes the issue

  • VonMagnum

    iZotope RX 2.0 works again in 10.11.1 (crashed instantly in 10.11.0). Logic Pro 9 is also working fine here so far, but I haven’t tried a lot in it except to make sure I can record and input MIDI (didn’t try it in 10.11.0, though) and my old PreSonus Inspire 1394 (with FW400) also works fine on my old 2008 Macbook Pro I use for portable recording. I’ve had some trouble my Midiman 2×2 Anniversary Edition, though. If I boot with it plugged in, it works OK. If I hot plug it, it will not be recognized by the OS, including after booting with it (i.e. unplugging it and then plugging it back in). I’ve sent feedback to Apple (not sure it will do any good).

  • VonMagnum

    iZotope RX 2.0 works again in 10.11.1 (crashed instantly in 10.11.0). Logic Pro 9 is also working fine here so far, but I haven’t tried a lot in it except to make sure I can record and input MIDI (didn’t try it in 10.11.0, though) and my old PreSonus Inspire 1394 (with FW400) also works fine on my old 2008 Macbook Pro I use for portable recording. I’ve had some trouble my Midiman 2×2 Anniversary Edition, though. If I boot with it plugged in, it works OK. If I hot plug it, it will not be recognized by the OS, including after booting with it (i.e. unplugging it and then plugging it back in). I’ve sent feedback to Apple (not sure it will do any good).

  • VonMagnum

    iZotope RX 2.0 works again in 10.11.1 (crashed instantly in 10.11.0). Logic Pro 9 is also working fine here so far, but I haven’t tried a lot in it except to make sure I can record and input MIDI (didn’t try it in 10.11.0, though) and my old PreSonus Inspire 1394 (with FW400) also works fine on my old 2008 Macbook Pro I use for portable recording. I’ve had some trouble my Midiman 2×2 Anniversary Edition, though. If I boot with it plugged in, it works OK. If I hot plug it, it will not be recognized by the OS, including after booting with it (i.e. unplugging it and then plugging it back in). I’ve sent feedback to Apple (not sure it will do any good).

  • Petteri Valtiala

    Elektron Overbridge sort of half works – the audio streaming & sync work just fine, but plugin control doesn’t. The plugin just doesn’t do anything/keeps dropping the connection to the hardware.

  • Petteri Valtiala

    Elektron Overbridge sort of half works – the audio streaming & sync work just fine, but plugin control doesn’t. The plugin just doesn’t do anything/keeps dropping the connection to the hardware.

  • Petteri Valtiala

    Elektron Overbridge sort of half works – the audio streaming & sync work just fine, but plugin control doesn’t. The plugin just doesn’t do anything/keeps dropping the connection to the hardware.

  • sarine voltage

    Be it this day or that day, something not at all cool happened with the arrival of the Apple-without-Steve-Jobs era… You guys are talking about abandoning “pro” but to me it would be more accurate to say Apple’s new thing is targeting the 6-year-old set.

    I kicked down for a new MBP a few months ago and was high with the excitement of having another new electronic toy to play with–I couldn’t wait to power up and check it out. So I booted up and… instead of being psyched and enrapt for hours (as is my usual “new toy” m.o.), I was dismayed at the sight of these awful little icons that looked like they were made by a 4-year-old (probably some v.p.’s kid is what came to mind). I was so seriously turned off that I couldn’t do anything until I figured out how to replace them. Which was when I next discovered that Yosemite was now my operating system–it too seemed to me to be a step down, not up, and I couldn’t find any “improvement”. It seemed to make my computing life harder, in fact, not easier.

    When I next visited my good friend GarageBand (who I generally spend the majority of my time with–I’m talking like 6-9 hours/day), I thought it would be fun, but OMFG… I thought the icons were weak, but I was horrified–seriously, HORRIFIED (I’m a very visual person) –to see the lame graphics and distasteful disfigurement done to my digital friend by some idiot moron. Don’t even get me started on the newly-implemented features that are even worse (e.g., fat/changing-size tracks SUCK as does the unchangeable default of the “Catch Playhead” button… who would implement features to aggravate and frustrate?!? Seriously!?! I’m one who enjoys change–changing it UP, that is, and improving, not retarding!)

    So, longing to have GB ’11 back and wondering if I could re-vamp my laptop to run Snow Leopard, if not for just the icons and the ease of use with the older version of GB, I visited the Apple store to ask the techs if this was possible and to also ask, “What exactly was [theoretically] improved with Yosemite?!” Nothing save for syncing capabilities between phone and laptop, etc., I was told. Great. What-with the dawning of the age of “homeland ‘ha-ha’ security” etc., I don’t ever sync ANY of my equipment. My dismay continued to grow as I realized the direction Apple appeared to be going in was the opposite of what I had in mind. Laugh if you like, but I was seriously considering changing my system so as to run Snow Leopard (I haven’t yet, but I’m still toying with the idea).

    All that being said, when El Capitan was available, I went for it figuring anything’s better than Yosemite. We’ll see, I’m exploring it now… Steve Jobs, your energy and your being are seriously missed…

  • sarine voltage

    Be it this day or that day, something not at all cool happened with the arrival of the Apple-without-Steve-Jobs era… You guys are talking about abandoning “pro” but to me it would be more accurate to say Apple’s new thing is targeting the 6-year-old set.

    I kicked down for a new MBP a few months ago and was high with the excitement of having another new electronic toy to play with–I couldn’t wait to power up and check it out. So I booted up and… instead of being psyched and enrapt for hours (as is my usual “new toy” m.o.), I was dismayed at the sight of these awful little icons that looked like they were made by a 4-year-old (probably some v.p.’s kid is what came to mind). I was so seriously turned off that I couldn’t do anything until I figured out how to replace them. Which was when I next discovered that Yosemite was now my operating system–it too seemed to me to be a step down, not up, and I couldn’t find any “improvement”. It seemed to make my computing life harder, in fact, not easier.

    When I next visited my good friend GarageBand (who I generally spend the majority of my time with–I’m talking like 6-9 hours/day), I thought it would be fun, but OMFG… I thought the icons were weak, but I was horrified–seriously, HORRIFIED (I’m a very visual person) –to see the lame graphics and distasteful disfigurement done to my digital friend by some idiot moron. Don’t even get me started on the newly-implemented features that are even worse (e.g., fat/changing-size tracks SUCK as does the unchangeable default of the “Catch Playhead” button… who would implement features to aggravate and frustrate?!? Seriously!?! I’m one who enjoys change–changing it UP, that is, and improving, not retarding!)

    So, longing to have GB ’11 back and wondering if I could re-vamp my laptop to run Snow Leopard, if not for just the icons and the ease of use with the older version of GB, I visited the Apple store to ask the techs if this was possible and to also ask, “What exactly was [theoretically] improved with Yosemite?!” Nothing save for syncing capabilities between phone and laptop, etc., I was told. Great. What-with the dawning of the age of “homeland ‘ha-ha’ security” etc., I don’t ever sync ANY of my equipment. My dismay continued to grow as I realized the direction Apple appeared to be going in was the opposite of what I had in mind. Laugh if you like, but I was seriously considering changing my system so as to run Snow Leopard (I haven’t yet, but I’m still toying with the idea).

    All that being said, when El Capitan was available, I went for it figuring anything’s better than Yosemite. We’ll see, I’m exploring it now… Steve Jobs, your energy and your being are seriously missed…

  • sarine voltage

    Be it this day or that day, something not at all cool happened with the arrival of the Apple-without-Steve-Jobs era… You guys are talking about abandoning “pro” but to me it would be more accurate to say Apple’s new thing is targeting the 6-year-old set.

    I kicked down for a new MBP a few months ago and was high with the excitement of having another new electronic toy to play with–I couldn’t wait to power up and check it out. So I booted up and… instead of being psyched and enrapt for hours (as is my usual “new toy” m.o.), I was dismayed at the sight of these awful little icons that looked like they were made by a 4-year-old (probably some v.p.’s kid is what came to mind). I was so seriously turned off that I couldn’t do anything until I figured out how to replace them. Which was when I next discovered that Yosemite was now my operating system–it too seemed to me to be a step down, not up, and I couldn’t find any “improvement”. It seemed to make my computing life harder, in fact, not easier.

    When I next visited my good friend GarageBand (who I generally spend the majority of my time with–I’m talking like 6-9 hours/day), I thought it would be fun, but OMFG… I thought the icons were weak, but I was horrified–seriously, HORRIFIED (I’m a very visual person) –to see the lame graphics and distasteful disfigurement done to my digital friend by some idiot moron. Don’t even get me started on the newly-implemented features that are even worse (e.g., fat/changing-size tracks SUCK as does the unchangeable default of the “Catch Playhead” button… who would implement features to aggravate and frustrate?!? Seriously!?! I’m one who enjoys change–changing it UP, that is, and improving, not retarding!)

    So, longing to have GB ’11 back and wondering if I could re-vamp my laptop to run Snow Leopard, if not for just the icons and the ease of use with the older version of GB, I visited the Apple store to ask the techs if this was possible and to also ask, “What exactly was [theoretically] improved with Yosemite?!” Nothing save for syncing capabilities between phone and laptop, etc., I was told. Great. What-with the dawning of the age of “homeland ‘ha-ha’ security” etc., I don’t ever sync ANY of my equipment. My dismay continued to grow as I realized the direction Apple appeared to be going in was the opposite of what I had in mind. Laugh if you like, but I was seriously considering changing my system so as to run Snow Leopard (I haven’t yet, but I’m still toying with the idea).

    All that being said, when El Capitan was available, I went for it figuring anything’s better than Yosemite. We’ll see, I’m exploring it now… Steve Jobs, your energy and your being are seriously missed…

  • Stanislav Palyvoda

    I think I’m late with the reply here 🙂 But 7 ozone and RX5 work really nice

  • Nathan Talzma

    The pain is real, long story short, music software works, but internet broken. Now with the El Capitan update – it’s more a case of internet works, music software broken.

    In this day and age, what a joke.