Here are the steps:

1. In the software instruments dialog, create an AU3 multitimbral track with 1 part
2. Track>Other>New track with next MIDI channel (ctrl-return)
3. Repeat step 2 until you have as many channels as you want for that port up to 16 channels (stop when you get to 127 channels)
4. Select the last track, Change to port n+1, channel 1 in the track inspector
5. Select there second to last track and do step 2 (this back fills the previous port)
6. Select the last track and repeat steps 2 through 6 (stop at 127 channels)

It's even easier...

After creating port1, channel 16...

6a Rename port 1, channel 16 to port 2, channel 1

6b backfill port1, channel 16 by selecting port1 channepo 15 and create new track with increementing channel.

I found a way to make this work.

Using the old instructions, after step 6 (where you rename channel 17 to be port 2, channel 1), do this:

6a. Select and delete either one of the tracks that are port 2 channel 1.

6b.  Select the second to  last channel again (e.g., port 1, channel 15) and then select Track>other>new track with next midi channel as before.  

These two steps break the link between what was port 1 channel 16 and what wants to be port 2 chanel 1.

yeah, you have to do that in the environment. 

This doesn't quite work.  When I try to change the track 17 to port 2 channel 1 in step 6, it also changes the track 16 to port 2 channel 1.  So those two tracks aren't unique.

I was referring to getting it to work at all.  The plugin doesn't load unless you have allocated enough audio outputs in your server preferences.

I agree about the midi channel limitation of 127.

This worked for me.  Thanks for the insight.

Dewdman, you need to increase your audio outputs per instance preference in VE Pro Server to 50 for the multi output version of the plugin to work.

Originally Posted by: Dewdman42

But I'm also quite overwhelmed about how best to dig into it.  

If you look in the Music section, the demos with the red buttons have tutorial files you can download.  I'd recommend you look at some of these to see how others use the library.  VI Pro allows you to see which articulations are used even if you don't yet own that library.  Caution is advised in that this will only make you want to buy more libraries when you see you don't yet own a specific articulation that makes you go "oh, wow.  I need that one".

deleted

Here are couple of things to try.  I've seen these work on other apps that are not designed for Mojave.

Make sure your elicenser app is up to date first.

Also, before doing any of the following, make sure synsopos is not running (force quir it if you have to using activity monitor).

1.  Try disabling and re-enabling the security and privacy checkbox in the automation panel.  

2.  If that doesn't work, you can reset the TCC database using the following command in a terminal window:

tccutil reset AppleEvents

This will remove all occurances odf the Sysnsopos.app items in the automation tab.  You can see this happen if you have that window open at the time.  This will require you to authorise each app once again as you did initially.  

If one of these works you probably need to do it each time you update the elicenser app,

3. As a last resort, you can launch elicenser and leave it running while using VEP 5. Then VEP 5 won't need to control synsopos since it will already be running.

My general rule is leave two for the DAW, and divide the rest evenly between VE Pro instances.  You have 24 total.

Originally Posted by: Dewdman42

Thanks for the idea.  Seems to help a lot...  what is a good rule of thumb on the thread counts, on a 12 core system?

I would allocate 22 to VE Pro leaving 2 for Cubase.

Are you using VE Pro Server or are you instantiating VE Pro directly in the sequencer?  If the latter, there may be some preferences to set in the sequencer for thread allocation but I am not familiar with Cubase.  If you are using VE Pro Server, then the thread count should have made a difference.  Also, if you are using Server, then there is a buffer number in the server window that you can adjust.  Are these the same in both cases?

Check your instances preferences and be sure to allocate more threads per instance since you only have one instance. 

See page 22 of the manual for guidance.

I have two computers (both Macbook Pros, 2.7GHz, 16GB, quad processor).  One is 2012 vintage and the other is 2016 vintage.  The newer one has a very fast SSD, the older one has an SSD that is significantly slower but still pretty good.  On both machines I am streaming from the internal SSD.

I have a midi file that stresses the SSD pretty hard (over 400-500 voices in some parts depending on the mic preset).  The older machine has problems in the more stressful parts of the playback.  The newer machine has no problem ever with this file.  When looking at ther CPU monitor, the older machine hits 100% in several places and it is here that I hear samples cutting out.  The newer machine never gets over 75% even with the lowest preload setting.  The old machine hits 100% often even with the highest preload settings.  But the preload setting does make a difference.

The SSD speed is the only significant difference between these machines.  I suspect the SSD speed is why some people are having problems and others aren't.

Anyway, the logic pro project and midi file are at the link below so you can test on your machines and monitor the CPU to see if it gets to 100%.  I think that is when the samples are cutting out.

https://www.icloud.com/#iclouddrive/0cns36_RgsPKidH8NUCcurESA

Try rebooting.  I needed to do that before it shows up in Logic Pro.

OK, thanks.  I also found the script and looked at that. 

I see that this has been released and it seems to allow the Vienna Suite Pro AUs to work once again.  So what exactly did this do?  What files got installed and where are theyt located?

You need to make a new playback configuration first.  The default configuration is not editable so new users can't get into trouble trying to modify the playback confoiguration.

Originally Posted by: Paul

Hello everybody, 

Very sorry about the trouble, this is now fixed with a new update, available in your User Area. 

Alternatively, here is the direct download link for VE PRO 6.0.16012 for macOS, please restart the computer after applying the update!

Best,
Paul

Still crashes for me even after reset.  I've sent a crash log.

OK.  Thanks.

For the purposes of the core allocation preference settings in VE Pro, should I assume that the VE Pro Event Input is equivalent to an instance?  So for example, if I have assigned VE Pro and 3 VE Pro Event Inputs is that equivalernt to 4 instances, or is it still just one instance?

I see.  So this is just a naming convention you used to differentiate library licenses.  

Thanks.