AU version of VE Pro in DP (bc MAS version isn't M1 compatible) anyone?

[dix]

Since it may be a long time before VEP works with M1 Macs, I'm creating VEP templates, like the the rest of the DAW hoi polloi, using the AU version. Has anyone tried this with DP? There's somewhat different, convoluted, procedures depending on which DAW is being used apparently. I'm wondering which, if any would be the closest to DP.

Any AU VEP-for-DP tips would be appreciated.

[Michael Canavan]

The Logic tutorial works but you obviously do not need a Logic I/O plug in, in DP.

The one caveat on online documentation.. So the VST and AU VEP plug in can't host more than 16 MIDI channels without adding another Instrument that acts as a dummy track, the VEP Event Input Plug in. You then assign it a MIDI port then you get 16 more MIDI tracks. The caveat is it's a dummy track it's only there to let the VEP plug in have extra MIDI channels, so no audio signal passes through it.

all of it makes you appreciate the MAS plug in, which probably won't be native for another 3-12 months. Vienna are replacing the eLicenser with iLok because Stienberg are abandoning dongles finally.

[dix]

Cool. I thought you might chime in Michael. That's a great tip re the dummy track! It would have taken me while to figure that out. I was thinking you could only have one instrument per VEP instance! This at least makes that avoidable. It also makes it possible to use existing VEP server documents I'd been accessing with the MAS plugin for use with the AU. That's huge.

Yes, I've been following the Vienna eLicenser-to-iLok info. Vienna recently posted that would happen "sometime this year". And an AS version of VEP, that will take place sometime after that, so yeah. We're looking at fall maybe?

Thanks so much for this

[Michael Canavan]

Cool. I thought you might chime in Michael. That's a great tip re the dummy track! It would have taken me while to figure that out. I was thinking you could only have one instrument per VEP instance! This at least makes that avoidable. It also makes it possible to use existing VEP server documents I'd been accessing with the MAS plugin for use with the AU. That's huge.

Kind of... I've got one VEP plug in loaded for East West Symphonic Orchestra, but 7 Event input plug ins. and you have to go through and assign those in DP by hand if you had a single instance of MAS for that same setup. So it doesn't save you that hassle in DP, just the hassle on the VEP server side.

Yes, I've been following the Vienna eLicenser-to-iLok info. Vienna recently posted that would happen "sometime this year". And an AS version of VEP, that will take place sometime after that, so yeah. We're looking at fall maybe?

I think that sounds about right. The whole death of eLiscenser explained why they didn't get busy coding the M1 version, but they IMO should have, at least of the freaking MAS and VST3plug in... but who knows what other issues there are right? it might be that the GUI framework needs substantial work and that the plug in needs to know the eLicenser or iLok is there, and it's not as easy as I think. But yeah, fall sounds like a good guess, hopefully sooner. We should see the iLok transition in less than a month.