1. Register NOW and become part of this fantastic knowledge base forum! This message will go away once you have registered.

Apple iMac New OS X EL Capitan not working with Cubase

Discussion in 'Cubase' started by ChrisH, Apr 19, 2016.

  1. ChrisH

    ChrisH Active Member

    Hi Everyone,
    Some super frustrating news..
    Just updated to El Capitan OS X (That's when this problem started)

    The Problem:
    - No audio output being sent to my Apogee Symphony system even when routing is correct.
    - When I go to record I get the error "ASIO Driver not running" from Cubase and no audio track begins to play or lay, just silence.
    - Audio from iTunes and Spotify work though, that's how I know this is a Cubase and El Capitan issue.

    Everything is up to date, updated driver for the Symphony System, updated Cubase.

    No luck..
    Everything worked fine with the old Snow Leopard OS

    This was posted from Steinberg Last September, what a joke and a nightmare.

    Looks like I'm going to have to figure somehow to go back to an older OS, which is where the problem gets even worse because Apple sets up operating system updates to only go forward and doesn't allow you to uninstall/revert back to earlier OS X's.
    So frustrating, I don't know what to do, I'm in the middle of finishing a project.
    This is very disappointing in Apple and Steinberg.
  2. Sean G

    Sean G Well-Known Member

    Sorry I can't give you any advice Chris, I gave up on Apple when they moved on from Tiger OS, and unfortunately I have no experience with Cubase apart from a one recording session as a musician around 5 years ago.

    According to the Steinberg link you posted it sounds as though there are compatability issues, that was dated 28 September 2015 so you would think there would be an update or they would have sorted this out 7 months on.

    Someone has dropped the ball big time by the way I read it.

    Have you checked any forums that may be dedicated to Cubase for any update?
  3. DonnyThompson

    DonnyThompson Distinguished Member

    I'm hip. There's no excuse for that. Not these days.
    That notice was posted in September of '15 and they still haven't done anything about it? 9 months have passed and it's still not compatible?

    I'm not a Mac guy anymore either, but if it were me, I think I'd be rolling back to the last OS where everything worked. ;)
  4. Sean G

    Sean G Well-Known Member

    I could be wrong, I'm no mac guy either, but I'm not sure you can do that with a mac retrospectively unless you use time machine to back up your mac

  5. Sean G

    Sean G Well-Known Member

    I also found this if its useful...


    And there is this -

  6. ChrisH

    ChrisH Active Member

    I really really appreciate you guys being understanding and chipping in with your intelligence, thank you.
    This is a migraine for me until I get it sorted out.

    No worries, man.
    I appreciate your help. I have searched and searched on forums with no resolve.

    You're right, no excuse, such a joke.
    Steinberg has let me down more with version 7.5 of Cubase then any software manufacture ever has.
    From not responding to emails, to this kind of crap. Garbage.

    I'm trying to figure how to roll it back, calling around to local apple repair shops trying to find someone that knows a way to install any of the earlier OS X over El Capitan.
    Coincidentally I recently got a new backup drive and so all my Time Machine backups are with El Capitan :( I only wish I could do the procedure in that video.
  7. ChrisH

    ChrisH Active Member


    It has came down to two options...

    1. Take my computer into Apple Repair store and pay $200.00 for them to install earlier version of OS X + a headache of re-installing all programs and plugs, including Cubase.

    2. Pay $150.00 to "upgrade" to Cubase 8.5, since they claim is works with El Capitan.
  8. Kurt Foster

    Kurt Foster Distinguished Member

    LOVE IT ! .......... (not)
    ChrisH likes this.
  9. ChrisH

    ChrisH Active Member


    When "Upgrading" from Cubase 7.5 to 8.5, will I still have my old VST Instruments, I cannot remember if they get overridden or not?
    I need to keep them from Cubase 7.5 to finish some projects.
  10. Kurt Foster

    Kurt Foster Distinguished Member

    perhaps you can find a local computer geek on CraigsList to reinstall the older OS for less than $200?

    my "stepson" does this for us whenever our computers get all clogged up. it really doesn't cost anything except the time it takes to do it.
  11. Sean G

    Sean G Well-Known Member

    It has always been my understanding that your VST instruments and effects will remain after you upgrade your DAW, as long as the upgrade was designed to operate on the same platform as the current DAW...ie - 32-bit or 64-bit.

    These VSTs' are seperate files that are stored on your hard dive, they are stored as program files on the C drive in their own folder.

    Although if you went from a DAW that was designed to run on 32-bit platform to one that was designed to run on a 64-bit platform and your VSTs' were all 32-bit compatable only, then they will not work on the 64-bit platform DAW without a bridge.

    You would therefore have to download your VSTs' in 64 bit again if you are upgrading to the higher platform from 32-bit if your DAW does not accomodate a bridge to run the 32-bit VSTs'.

    IMO using a bridge is like a band-aid solution, it opens the door to problems which at times can cause your DAW to freeze or plug-ins not processing correctly.

    From reading your last post again, it seems that biting the bullet and upgrading to Cubase 8.5 may be the better option...at least you won't have to re-install all your programs and plug-ins again...and if you look at it optimistically, was there a chance you may have upgraded in the future anyway?

    I'm sure that there are newer features that may be an added bonus with the upgrade, maybe those and the fact that re-installing everything on your system again is such a PITA make it the more attractive option...or the lesser of two evils.
    ChrisH likes this.
  12. Sean G

    Sean G Well-Known Member

    Yep...my bad :oops:

    I edited that post to clarify
  13. DonnyThompson

    DonnyThompson Distinguished Member

    Isn't there a designated "bit bridge" program? I think it was originally designed to run with Sonar, but I think it's now been updated to work with (most) any DAW... not sure about Cubase, though.

    But, I can't say for sure. Samplitude has its own bridging system, I didn't have to install a third party prog, or even do anything - it just did it on its own.

    I'm mostly 64 bit with plugs and VSTi's these days anyway, but there are a couple 32 bit plugs and VSTi's I still have and like, and Samplitude handles them just fine.
  14. ChrisH

    ChrisH Active Member

    I ended up learning this the hard way (before I saw this/your post), after I bit the bullet (I agree, the better bullet) and got Cubase 8.5 installed NONE of my plugins were there, I started getting sick.
    After stressing out thinking I was going to have to buy all new plugins, I discovered you can boot up/bridge mode Cubase 8.5 in 32 bit mode instead of 64, which I did, all is well now, very thankfully.
    You're right, I probably would have updgraded anyway, given I've been a Cubase user for 10 years now and to switch to a different daw at this point wouldn't make sense for creative and intuitive reasons.
    There are some nice features I've noticed already.

    What's up with 32 vs 64 bit?
    Sean G likes this.
  15. Sean G

    Sean G Well-Known Member

    Progress...In a nutshell you can utilise more RAM on a 64-bit operating system and DAW program, meaning that you can have more tracks and more plug-in processing happening simultaneously on 64-bit DAW programs than their 32-bit counterparts before things start to lag or crash.

    "The terms 32-bit and 64-bit refer to how much of your computer's memory (RAM) can be used by the installed operating system and the applications that run within that operating system.

    There are 32-bit and 64-bit Operating Systems as well as 32-bit and 64-bit Programs.
    The terms 32-bit and 64-bit refer to how much of your computer's memory (RAM) can be used by the installed operating system and the applications that run within that operating system.

      • A 32-bit operating system typically only allows for up to about 4 gigabytes of RAM to be utilized by the OS or any of the installed programs. Therefore, it makes sense to only install 32-bit programs on a 32-bit operating system, as a 64-bit program would not be able to access any more RAM than a 32-bit program on a 32-bit operating system.
      • A 64-bit operating system allows for much higher RAM access and capacity. See your specific operating system specifications for further information on how much memory (RAM) can be utilized by your specific OS.

    A 64-bit operating system will allow for both 32-bit and 64-bit programs to be installed.
    Although both 32-bit and 64-bit programs can be installed on a 64-bit operating system, a 32-bit program will only be able to access up to about the first 4 gigabytes of memory (RAM).

    By contrast, a native 64-bit program installed on a 64-bit operating system will be able to utilize a much higher amount of memory (RAM), allowing for much larger projects and more memory-intensive operations.

    A 64-bit plugin can only run in a 64-bit host program.
    Although this fact is always true, some 64-bit hosts allow for a "bridge" program enabling the abilty to run a 32-bit plugin in a 64-bit host".

    Kurt Foster likes this.

Share This Page