As detailed in the other forum (https://www.vsl.co.at/community/posts/m269814-macOS-High-Sierra--10-13--compatibility#post269814) the solution that involves deleting the com.motu.MotuAudioSystem folder  and 'renaming' your vst folder and such DOES actually work, however it is incorrect. (http://www.motunation.com/forum/viewtopic.php?f=1&t=64443)

1) You must go to com.motu.MotuAudioSystem folder and delete the Audio Unit and VST Info Cache files 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.  This means that yes, you must reload them upon opening DP, but it also means that YOU CAN USE YOUR VST PLUGINS! (see #2)

2) You DO NOT have to rename the VST folder, and as such you can use your VST's (at least after you've done the steps.  You can go back, rename the folder, and then have DP examine the VST's).  However, I would in the preferences refrain from loading VST VEP.  You have AU and MAS that will work via this method, and I'm too lazy to test if it works (it probably does).  I'd also suggest only having it examine the VST plugins you actually use, because while the AU ones are fast, the VST's take significantly longer.  If you only use VST's as eq, compression, and virtual space, for instance, you can do all of that in VEP so...a strange work around but yah.

3) I have tried the above method of deleting the .bundle files for VEP.  Did not affect this method at all, except that I wasnt able to use the MAS versions of VEP.  Hey, with the above method, you can use the MAS VEP.

I highly suspect this glitch has to do with how DP analyzes plugins the first time around and then creates an info cache.  Since deleting the cache fixes the problem until DP is restarted, I'm honestly not sure why a simple programing fix involving those plugins cant be done on MOTU's side.  There, I'm finally pointing the finger at the software company with the real problem, and they have done little about it except pointing fingers at everyone else.  I'm not losing any money on this issue yet, but for any of you who are, I think this is probably grounds for a lawsuit.  Feel free to lawyer up!

I hope this helps.  Maybe its a system by system problem and theres a billion different solutions for this issue and all of you are right, but this one worked for me.

Five months since the high sierra release date and still no fix to the problem....😕

@rickindies said:

I finally managed to get it work! So apparently the cause of the problem is Vienna Ensemble Pro.bundle & Vienna Ensemble Pro Audio Input.bundle located in : system - library - audio - plugins - MAS. I managed to get DP & VE PRO running on High Sierra without having MAS on VE PRO (I can live with that as long as I get my DP AU & VE PRO working together)

I dont know about the VST folder folder thing. I managed to get it work just by removing those bundles. At some point I forgot to rename my VST folders  to VST_TEMP & it still works (if you install new plugins, some plugins will automtically create new VST folder on you plugins folder.

The weird thing is it even works with DP 9.13! (I'm running 9.13 this whole day & installing Altiverb, Waves etc). I tried to switch between DP 9.51 & 9.13. Both works with VST folder on it! Aparently on my system the only problem is the VE PRO MAS bundle. Has anybody tried to remove their VE PRO bundle from MAS folder?

Anyhow I haven't work on a "big session template" today. So  I don't if its gonna be fully compatible. But so far I installed Waves, Kontakt, Altiverb, Amplitube 3 etc & DP hasn't crash while also running VE PRO 6

This worked for me! I hope there are no problems with the AU version of VEP Event Input.

**Leigh

@leigh said:

This worked for me! I hope there are no problems with the AU version of VEP Event Input.

Event Input does NOT work because the AU version drops note-offs.

**Leigh

I'm totally dependent on the MAS plugin (my DP project is MIDI only, all audio is mixed in VE Pro), so the suggested workarounds did not work for me. Had to go back to Sierra, and I feel I'm now stuck with it. 

Its been six months since high sierra's release... Come on now.... what is going on?? Is MOTU helping?? 😠

@crescentmoon52_8709 said:

Its been six months since high sierra's release... Come on now.... what is going on?? Is MOTU helping?? 😠

It is frustrating.

I do appreciate that MOTU did listen to some feedback I had given when previously escalating as I requested a bit more front-facing public disclosure with critical problems.  Had they explicitly stated in release notes last fall that VE-Pro MAS wasn't working, I never would've wasted a day updating then having to revert back.

Their website now explicitly states this in the update/download area and I hope they continue to maintain that type of detailed transparency with future releases if major issues present themselves.

As an end-user, knowing more information up front is always better than less - especially when it has the possibility of disrupting individuals' productivity & time.

Light at the end of the tunnel?

http://www.motunation.com/forum/viewtopic.php?f=1&t=64664#p552561

**Leigh

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 guess they were an update ahead of us.

10.13.4 seems to be stable.

sorry for the confusion and anger, I was an update behind.