VE Pro 5 fixes AU MIDI limitations (apparently)

[p.pan]

http://www.vdrums.com/forum/showthread. ... VSTi/page2" onclick="window.open(this.href);return false;

That is link.

[studio_651]

back to the OP... VE Pro 5 is out now but i don't see any mention of the workaround for the AU MIDI channel limitation. maybe it's buried somewhere in the manual, but it wasn't featured on the product page from what i could see. i would think they'd really want to call attention to that new feature (if it exists) to help rationalize the $55 upgrade price.

can anyone else find any mention of it? i'm hoping i'm wrong! i really want to be able to house all my kontakts in one instance of VEP.

[AntiPro]

back to the OP... VE Pro 5 is out now but i don't see any mention of the workaround for the AU MIDI channel limitation. maybe it's buried somewhere in the manual, but it wasn't featured on the product page from what i could see. i would think they'd really want to call attention to that new feature (if it exists) to help rationalize the $55 upgrade price.

can anyone else find any mention of it? i'm hoping i'm wrong! i really want to be able to house all my kontakts in one instance of VEP.

The workaround is achieved by the new VE Pro Event Input plugin, which is shown in the VE Pro 5 Overview video at http://www.vsl.co.at/en/211/497/1685/1990/1999/1688.htm.

[studio_651]

The workaround is achieved by the new VE Pro Event Input plugin, which is shown in the VE Pro 5 Overview video at http://www.vsl.co.at/en/211/497/1685/1990/1999/1688.htm" onclick="window.open(this.href);return false;" onclick="window.open(this.href);return false;.

thanks karel! wow, it's not often that you get a response directly from a software engineer responsible for the software unless it's a smaller startup company. looks like this was your first post which means that you went out of your way to help us with info on this issue - very cool!

i'm very excited by the new features in VE Pro 5 - great job! one thing i really like is the audio input plugin seems like a cool method for offloading send effects from your DAW host.

but for me, the biggest one is the fact that VE Pro can now provide up to 32 latency-compensated MIDI ports via AU (i.e. you could potentially house 32 fully-loaded multi-timbral plugins like kontakt in one instance of VE Pro). that's going to be a game-changer for a lot of us. the only other similar product, plogue bidule, can currently only provide 8 latency-compensated MIDI ports due to the limitations of the rewire spec.

if i could, i'd like to make a humble suggestion: you guys might want to think about listing this as a major new feature on the VE Pro 5 product page (specifically on the "product info", "product comparison", and "features" pages). i think there are probably a lot of people out there (like me) who would buy or upgrade to VE Pro 5 solely because of that feature.

anyway, thanks again karel and best of luck to you and your team!

[Frodo]

thanks karel! wow, it's not often that you get a response directly from a software engineer responsible for the software unless it's a smaller startup company. looks like this was your first post which means that you went out of your way to help us with info on this issue - very cool!

+ 1 million.

[williemyers]

Frodo, et al.
I think you've touched on this question in the past, but if could ask (just once more)?

Bottom line, for a user running DP 7.42 on a single MacPro (see sig.), booting 64 bit and 10.6.8 and/or Lion, is there really any advantage to using VEPro in this setup?

I have no doubt that if I were running two or more networked computers, VEPro would be the way to go, but I've never understood whether or not it would benefit me as a single-comp. user.

thanks and apologies for yet again asking what's probably been asked and answered

[Tripi]

I just watched the video, and it looks like a great update. Let me see if I have this right about the event input plugin. In DP, we would need to use VE Pro as an instrument, and then make another instrument with the Event Input plugin. Then, our MIDI tracks will all be assigned to that instrument (instead of VE PRO). I'm still a little fuzzy about how it gets around the 16 MIDI channels though. DP won't let us have an instrument with more than 16 channels that we send to from a MIDI track, right? So, will we need to have an Event Input instrument for every 16 channels we use?

[doodles]

SO unbelievably excited about the AU MIDI workaround. Currently have 18 instances per template to hook up my slave, which seriously bogs down DP.

Is it sad to be this excited?

[labman]

Hey, I am EXTREMELY excited too.

What significance does the new feature 'Full plug-in latency compensation' have for us DP users? Are they talking just about EQ etc type plugs when used inside VEP? Or are they talking about the relationship of DP to VEP as a plugin itself? I dont understand.

[Killahurts]

So, will we need to have an Event Input instrument for every 16 channels we use?

Apparently. I just loaded the new Event Input plug as an instrument. When I checked its MIDI tracks, there are 16 available.

This is still extremely cool, because more MIDI tracks is going to be a lot less CPU intensive than all those server instances. I looked in the VE Pro server, and it looks like we can have 8 MIDI input plugins to choose from, with 16 channels each. Sweet!

But now I'll have to rebuild my templates..

[Killahurts]

Hey, I am EXTREMELY excited too.

What significance does the new feature 'Full plug-in latency compensation' have for us DP users? Are they talking just about EQ etc type plugs when used inside VEP? Or are they talking about the relationship of DP to VEP as a plugin itself? I dont understand.

I think that has to do with using VEP as an effects rack, i.e. sending audio out of the DAW (new feature), into a VEP instance. It will have latency compensation so everything lines up correctly in the DAW after the round trip.

[AntiPro]

Using the Event Input plugin (or VST3/RTAS) you can have up to 32 MIDI input ports per VE Pro instance. The maximum amount can be set in the VE Pro Server Preferences as well as in the VE Pro Server Interface plugin preferences.

Full latency compensation really means full latency compensation, as in all latency is always compensated for and no extra measures are required to synchronize things. VE Pro 4 didn't have latency compensation for plugins running in the instance. Time synchronization in general has also been vastly improved to ensure sample accuracy.

[Killahurts]

Karel,

Thank you, thank you, thank you for this version 5! It is really fantastic, and upgrading was painless and fairly priced.

[studio_651]

Bottom line, for a user running DP 7.42 on a single MacPro (see sig.), booting 64 bit and 10.6.8 and/or Lion, is there really any advantage to using VEPro in this setup?

the main advantages of housing your VIs outside of DP are that you aren't limited by the < 4GB RAM limit that DP has (since it's still a 32 bit application) and also that you don't have to reload all of your samples each time you switch between DP song files. whether it's worth it or not for your setup is all about how big your template is (or how big you'd like it to be).

[Marc7777]

Hello all,

I'm going to be building my new template over Thanksgiving, and I wanted to see how you guys were using this new AU workaround.

Just wanted some feedback from others experience for things to do, or not do, when making a template with this new awesome program.

From reading above it seems, in DP, we'll have our VEP instrument track with the plugin server. Then we'll have several MIDI tracks with the "event plugin" on them? I guess you can just stash those away in a track folder, since i'm assuming, when you make another MIDI track you'll be able to choose one of those MIDI ports as a MIDI output. correct?

I've been reading a few issues from users, but it seems to be user specific related. Anything going on odd that I should know about before jumping ship?

Thanks!

M