Vienna Symphonic Library Forum
Forum Statistics

199,036 users have contributed to 43,150 threads and 258,880 posts.

In the past 24 hours, we have 5 new thread(s), 13 new post(s) and 63 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. macOS High Sierra (10.13) compatibility
  • C
    C

    I too am wondering about VEP 6 and DP 9.5.1 compatibility under OS 10.13.1.

    VSL is working fine with DP on my current rig (OS 10.10.5), but I'd like to upgrade my mac to 10.13.1. From this thread though it appears as though I should wait, correct?

    I was told that, in DP, since we're able to run VSTs AND MAS plugins, that VST versions are more stable with 3rd party software. Is this correct? If so, and since the MAS plugin is the culprit re VSL in High Sierra, is the VST plugin working ok in DP9.5.1?

    Is this not a 'safer' alternative to using the MAS plugin version? What are the disadvantages of using VEPro 6 VST plugin compared to the MAS plugin?

    Thanks
  • P
    P

    Just wondering if there's any progress on this issue. Apple keeps suggesting I upgrade to High Sierra, but I'm in the middle of a large DP/Vienna Ensemble Pro project ...

    Thanks!
  • L
    L

    DO NOT UPGRADE to MacOS High Sierra.  I emailed MOTU since Vienna hasn't mentioned anything and this was their reply: 

    I'm sure MOTU has already received a lot of request for help on Vienna Ensemble Pro 6 MAS not working in DP 9.51 for MacOS High Sierra and there hasn't been any word from Vienna either about resolving this issue that has been going on for a month now. My question is what time frame can we expect for there to be a new update to fix this issue?

    Added by Travis on 2017/11/30 16:59:47 Universal
    HI Lee, 

    Thanks for writing. We appreciate your patience with this. At this time, VSL and MOTU are working together to get this issue resolved. I'm not sure when an update will be available, but I expect it to be before too long. 

    I'll be happy to send you any information I have as it becomes available. 
    Best regards, 

    Travis Hagan
  • T
    T

    Does anybody know if this is fixed in the updated version of VEP released on 19-Dec-2017?
  • PaulP
    VSL Team
    PaulP

    Hi, 

    Unfortunately this incompatibility has not been fixed. We are in touch with our friends at MOTU. 

    Best, 
    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • L
    L

    Any news?.. My music production is frozen. 
  • D
    D

    Dear Vienna Symphonic Library Liason,

    Is there *anything* that can be done to help make the High Sierra / Digital Performer incompatibility a priority? This issue will be 4 months old in a couple of days.  Is there any chance we can have  discount on the next update?
  • C
    C
    last edited
    last edited

    @Dubzee said:

    Dear Vienna Symphonic Library Liason,

    Is there *anything* that can be done to help make the High Sierra / Digital Performer incompatibility a priority? This issue will be 4 months old in a couple of days.  Is there any chance we can have  discount on the next update?

       It either is not a priority or the problem is far more serious than they say....
  • P
    P

    Also sitting and hoping (and being irritated by the constant Apple prompts to upgrade to High Sierra!).
  • marnixM
    VSL Team
    marnixM
    last edited
    last edited

    Hi all,

    A fellow user has posted the following workaround, which MOTU recommended for UAD plug-ins on the MOTUnation forum. It also worked for the VE Pro 6 plug-ins here on our systems!

    Workaround fix for VE Pro 6 plug-ins in DP 9.51 on macOS High Sierra:

    1.) Run the latest Vienna Ensemble Pro 6 (OS X) installer from https://www.vsl.co.at/en/MyVSL/software_installers. Restart the computer.
    2.) Open the Applications folder and drag the Digital Performer application to the trash. If you have multiple versions of DP, be sure to drag all versions to the trash.
    3.) Hold the Option Key while clicking on the Finder's "GO" drop-down menu, select Library, then open the Preferences folder. Find the com.motu.MotuAudioSystem folder and drag it to the trash. Empty the trash.
    4.) Download the DP 9.51 installer available at motu.com/downloads and run the installer.
    5.) Find the VST folder (System HD/Library/Audio/Plug-Ins/) and rename the folder to anything other than “VST” (for example, “VST_temp”).

    Your Audio Unit and MAS VE Pro 6 plug-ins will now be available in Digital Performer 9.51. Please be aware though, that your VST plug-ins will of course NOT be available after renaming the VST folder!

    I hope that helps until MOTU and our developers can find a real solution!

    Best, Marnix
  • L
    L

    Marnix,

    Just to clarify, MOTUNation.com is not in any way connected with the company MOTU so I don't think this fix was officially from MOTU. 

    I really do hope VSL and MOTU will get the DP/VEPro/HS problem fixed soon.

    **Leigh
  • L
    L
    last edited
    last edited

    @Lionberg said:

    Any news?.. My music production is frozen. 

    I do not know, what you guys are doing there, but I had to switch DAW...
  • C
    C
    last edited
    last edited

    @Lionberg said:

    Any news?.. My music production is frozen. 

    I do not know, what you guys are doing there, but I had to switch DAW...

    Don't know why this problem hasn't been addressed at this point but I too am considering switching from DP to Logic or Cubase.  I called MOTU in early November to ask about their progress with Vienna and they told me it was Vienna's problem. No wonder MOTU is not in the top 5 category of DAWs.... they are becoming irrelevant.
  • D
    D

    As others have noted, Apple asks daily for me to upgrade to High Sierra. The MOTU/VEP issue is the only reason I haven't done so. At the moment, I'm not inconvenienced by sticking with Sierra for now, but experience teaches that fairly soon, High Sierra is going to be a necessary upgrade.

    Moving to another from DP9 to another DAW is, after decades of using DP, a high stress proposition, but I'm beginning to wonder if this will become necessary. And this is STRESSFUL to consider.

    If I have to switch I want to go to a DAW which will provides the easiest path to porting over all my DP projects. One that has the lowest learning curve for a DP user. Has great tech support, etc.

    What are the CONTENDERS? Anyone made the switch and can speak with first hand knowledge?

    And finally a question for VSL support: Is the problem not fixable on the VSL side?

    Man, this is frustrating.

    It seems like MOTU and VSL are behaving like Republicans and Democrats on this by the way...Surely there is a programmer in either company who knows how to fix this. After all, we put a man on the moon...

    PaulR
  • L
    L
    last edited
    last edited

    @daerp said:

    . . .

    Man, this is frustrating.

    . . .

    PaulR

    Yes, it is and neither MOTU nor VSL will say, "We're sorry so many of you are having a problem that so directly affects your bread and butter. Representatives of both programming teams will be talking this week and come up with a fix."

    I'm just surprised that VSL isn't taking the lead on this. They are usually very responsive to their customers.

    **Leigh
  • D
    D
    last edited
    last edited

    @daerp said:

    . . .

    Man, this is frustrating.

    . . .

    PaulR

    Yes, it is and neither MOTU nor VSL will say, "We're sorry so many of you are having a problem that so directly affects your bread and butter. Representatives of both programming teams will be talking this week and come up with a fix."

    I'm just surprised that VSL isn't taking the lead on this. They are usually very responsive to their customers.

    **Leigh



    I just wanted to let everyone know that I contacted both VSL and MOTU about this problem.  VSL gave me a bit more information about the problem.  Tldr, it's a big problem that won't be solved any time soon.  But here's both companies responses:

    "Please be assured that we are absolutely aware of the urgency of this matter - our developers have in fact spent the best part of this week investigating what could possibly cause this incompatibility, unfortunately without any success.


    So they have sent all their findings to their colleagues from MOTU yesterday, as we are cooperating to find a solution, and they have already answered to our requests.
    I am sorry to say though, that they are actually as clueless as we are when it comes to finding the actual cause of the problem, let alone a solution to it...
    Their suspicion is that this is an OS bug involving loading multiple dylibs that depend upon other common non-OS dylibs. It may have something to do with the fact that DP loads multiple plug-in formats simultaneously. They’ve reached out to their contact at Apple but so far haven’t heard back.

    So this is the current situation and I must admit that it is extremely frustrating for us as well simply not to know what might possibly cause the incompatibility.

    Our developers will continue to investigate in cooperation with MOTU and Apple and I sincerely hope that a solution can be found soon!

    My apologies for not having better news at the moment and thank you again for your patience!"

    MOTU had a more....lame response to my inquries:

    "Like yourself we are waiting for VSL to issue an update that addresses compatibility with DP under OS 10.13.  MOTU can not predict VSLs development schedule therefore we can not tell you when that update will be released."

    Hope this helps,
  • G
    G
    For those of you that feel frozen by this, let me offer some advice: first just because a software update is offered doesn’t mean you need to use it. If the version you are using works, leave it alone. Usually updates are offered for various bug fixes. If you don’t have that issue, don’t upgrade. Concerning updating to high seirra, someone mentioned that sooner or later he’ll HAVE to update. We actually, the only reason to update is for safari compatibility, and security issues related to that app. Otherwise, think of this like a hardware synth. The version you buy is the version you get. The other thing is if you are doing this professionally, then you need to have one or two other cloned drives a available in case your drive fails. If you do an update of anything, especially the OS, do it on your cloned drive. That way you don’t lock yourself out from work. Then when bugs like this get fixed, you can test it and then convert to the new OS. On that note, I use DP 9.0.1 still, as the later versions don’t allow for generating plug ins in real time, and pregen hasnever worked for me. On my protools computer I was using systen 10.9 until recent. Why? Because it worked. It was only becuase of some library that I decided to update. So yeah. Eventually you will have to update. But that day is a long way away.
  • S
    S

    Gluppy... Gee thanks for telling everybody that they shouldn't upgrade to a newer system. Now to reality... I bought an iMac Pro that only runs on High Sierra. So what am I supposed to do. I can't go back. There were no warnings about the problem from either VSL or MOTU. Unless you dug into the bowels of the VSL or Motunation forums and knew what you were looking for, nothing popped up.

    MOTU told me VEP 5 would work .... Nope! I can't believe this hasn't been a priority fro both MOTU and VSL for months. Obviously it isn't. VSL has been cranking on Synchron Strings. I get it from their side but with the number of composers using DP and VSL together it seems a bit dangerous from a customer service perspective.

    Sadly, I have another couple days before I have to pull the trigger on another DAW to start a new project. Love DP, not a fan of Logic but it's looking more like I don't have a choice.
  • G
    G
    Lol. I was addressing the guy and others that upgraded from a previously working OS and versions of DP and VePro. Where is your previous computer? Same principle applies. You use the old hardware system until you’re sure the new one has all the bugs worked out. Now if this is your first system ever, well then, what can I say, you’re screwed. And until this bug is worked out, you have a very shiny mac paper weight. Sorry. My post is meant as advice, not an admonishment. I started with DP using a Mac plus, so I do have some experience in these matters. And I have three studios that I work out of, so I am very much sensitive to any upgrade issues. Changing one thing in one means I have to change in the other two. Bottom line, if it ain’t broke, don’t fix it. The only time I upgrade is when a sound library requires it.
  • G
    G
    Also, if I am not mistaken, the Is the AU, VST and the MAS version of the plug in. While you are limited to only one set of 16 midi channels, in the AU version, it does work yes? Could be a work around.