Vienna Symphonic Library Forum
Forum Statistics

199,030 users have contributed to 43,150 threads and 258,878 posts.

In the past 24 hours, we have 6 new thread(s), 14 new post(s) and 61 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. macOS High Sierra (10.13) compatibility
  • 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.
  • D
    D
    Interestingly, VSL does seem to be taking the lead on this, as they are the only ones responding. I’ve been leaning on Apple, whose only response is “Go ask the developers.” MOTU is essentially saying, “Not our fault, go ask Apple.” Hopefully, the good people at VSL will be able to get some cooperation from the other parties at some point. Meanwhile, I definitely feel the frustration, with several thousand dollars worth of hardware and software sitting on the desk. Dexter
  • D
    D
    last edited
    last edited

    Hi it's me again.  

    @marnix said:

    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



    Can confirm after doing myself that this ONLY WORKS ONCE!  In order to get it to work 'every time', you must delete the audio unit and VST (more in the edit) CACHE files inside the com.motu.MotuAudioSystem folder EVERY TIME after you have closed out of DP.  If you've customized which plugins you're loading, especially VST's (see below) then do NOT erase the Audio Plugin Prefs file. The downside to this is that it rescan's the plugin's every time you start the program after deleting the cache's -- not a terrible solution if you work in one solid chunk on one single project the entire day and you dont have a million plugins.  

    Also, to a few someones out there, telling people not to upgrade is basically telling them to 1) accept security flaws that could put their identity/finances/computers at risk and 2) accept that developers don't have to care about getting upgrades correct.  Shame on you.


    EDIT: I can confirm after some testing that you can have DP load VST's through this method, though it takes FOREVER.   Therefore you do NOT need to change the VST folder name, of you can change it back to normal if you go through the above steps, then select which VST's you wish to load through preferences.  This will add a Audio Plugin Prefs file, which you'll need to keep so that all the plugins you desire will load after deleting the cache's.  I suggest, however, not loading the VEP VST, because that's probably the issue, but since this is a Mac only problem just use the AU.  The other methods described on other forums don't work unless I'm doing it wrong.  It's a bad solution, but a solution nonetheless.
  • A
    A

    Sooooo. It's now March 6th 2018 and this thread is dead. I bought a laptop in Dec which came with High Sierra, DP 9.51 has been fine with all other plug-ins (waves, NI, PSP) (although 9.51 on my 12 core Tower running 2 OS's behind has issues where it chokes if you save while playing and that hasn't been updated for 12-14 weeks either - yes I know, it's not a show stopper). I took my VEP dongle home to work, VEP launches fine but now I can't use my in progress DP session on Macbook pro off site unless I use this temp. Fix. Why all of the silence on this? I'm guessing Motu is the issue? Any word from Vienna here? It's been months and VE is one of the few that actually take the extra step to make a MAS plugin so I find it puzzling that it's still broken! Any info would be appreciated.

    thanks~
  • L
    L
    last edited
    last edited

    @marnix said:

    EDIT: I can confirm after some testing that you can have DP load VST's through this method, though it takes FOREVER.   Therefore you do NOT need to change the VST folder name, of you can change it back to normal if you go through the above steps, then select which VST's you wish to load through preferences.  This will add a Audio Plugin Prefs file, which you'll need to keep so that all the plugins you desire will load after deleting the cache's.  I suggest, however, not loading the VEP VST, because that's probably the issue, but since this is a Mac only problem just use the AU.  The other methods described on other forums don't work unless I'm doing it wrong.  It's a bad solution, but a solution nonetheless.

    This solution does not work if you need to use Event Input.

    I deeply appreciate VSL's long explanation of the situation. 

    **Leigh
  • marnixM
    VSL Team
    marnixM

    Hi all,

    This is to let you know that Apple just released macOS 10.13.4, which in fact seems to fix the incompatibility issues between VE Pro 6 MAS and DP 9.5.1!

    Best, Marnix 
  • P
    P

    Obviously they were waiting for me to break down and get Logic, which I did just a couple of days ago!
  • D
    D
    [size=9][/size]THANK YOU!!!!!!!!! 😄😄😄😄😄😄😄😄😄🎶🎶🎶🎶🎶🎶🎶🎶🎶🎷🎷🎷🎷🎷🎷
  • D
    D
    On the bright side, Logic has many great sound effects in the Foley section of their library. You can bounce some down and use as sound design and other things. They are well worth the 200 bucks. Logic is also great for the quick project that doesn't need live instruments/ players ; where you just want to drop the curser at your starting point, or even a hard hit. It's also a quick DAW for bouncing something in place quickly and scrubbing quickly.
  • P
    P

    Good points all. Plus, I have long wanted Hermode tuning, which Logic has and DP does not; and it just happens that I'm having a problem with the NI S88 and DP, the the S88 works like a charm in Logic. So all in all I'm pleased.
  • L
    L
    last edited
    last edited

    If you need to use Metric Halo's MIO Console software, do NOT update to 10.13.4:

    @Another User said:

    To All MIO Users: 


    The latest update to macOS 10.13 (High Sierra) appears to introduce a bug that is not allowing MIO Console to launch properly. 

    The driver will still stream audio, but you will not be able to use MIO Console to make configuration changes. 

    For that reason we recommend that for the time being you DO NOT UPDATE to macOS 10.13.4. You should be fine up to version 10.13.3. 

    We will post again when we have more information. 

    Best regards, 

    Jon Stern 
  • K
    K
    last edited
    last edited

    So is it safe now to upgrade, or will there also be a fix coming from VSL?

    @marnix said:

    Hi all,

    This is to let you know that Apple just released macOS 10.13.4, which in fact seems to fix the incompatibility issues between VE Pro 6 MAS and DP 9.5.1!

    Best, Marnix 
  • R
    R
    last edited
    last edited

    I just upgraded from 10.12 to 10.13.4 and everything worked fine with VEPro 5

    @Kevin Kliesch said:

    So is it safe now to upgrade, or will there also be a fix coming from VSL?
  • T
    T
    last edited
    last edited

    @marnix said:

    Hi all,

    This is to let you know that Apple just released macOS 10.13.4, which in fact seems to fix the incompatibility issues between VE Pro 6 MAS and DP 9.5.1!

    Best, Marnix 

     

    I just upgraded to 10.13.4 and DP 9.5.1 using templates previously working in DP 9.5 & Sierra.  VE-Pro 6 plugins appear to be loading fine; none of the errors I was receiving before are appearing.

    I also just opened up a blank project and added some VE-Pro MAS instrument tracks and those appeared to load without previously seen errors either.

    Somebody was escalating issues they were still having on another thread, however I'm not experiencing that issue.

    https://www.vsl.co.at/community/posts/m270832findlastpost-VEP-and-DP-9-5-1-High-Sierra#post27083