There's still all the other additional features to upgrade for of course. Such as plugin latency compensation, surround support, fully mappable touch parameter automation, more flexible routing using the post effects rack, dockable windows, and a ton of other general improvements. These are not related to the Audio/Event Input plugins in any way. I'd recommend you to at least demo VE Pro 5 ;)

@Karel said:

I'd recommend you to at least demo VE Pro 5 😉

Thanks again Karel, that I'll surely do! 😉

Cheers

Arceo

Just remember that while VE Pro 5 is fully backward compatible with VE Pro 4, you can't load VE Pro 5 projects with VE Pro 4. So be sure to keep backups.

Good point Karel!

I'll be careful to not mess with metaframes versions...[:S]

Not just metaframes, also your master host project.

Yes sir, you're right again!

Of course if I save a DP song with VEP5 plugins there's no way to open it when I roll back to VEP4. Well, I think that DP will open it but it will complain that a plugin is missing since it cannot find VEP5 which the song was saved with.

Another point taken! [:P]

Currently the situation in DP with regards to the Audio/Event Input plugins is as follows:

- In DP's Audio Plug-ins preferences, you have to disable Pre-gen mode for all plugins. Otherwise the Audio/Event Input plugins will not work properly.

- Bouncing (offline rendering) does not work, but Freezing (real-time rendering) does work. It is possible to bounce by first freezing and then bouncing the resulting frozen tracks.

The manual will soon be updated with this information as well (as well as information about workarounds in Logic).

IMPORTANT: This only applies to the Audio/Event Input plugins in DP. VE Pro 5 still works just as well as VE Pro 4 for regular operation.

Sorry for the inconvenience. 

Hey Karel,

this seems like a very reasonable workaround untill you find a way to definitely solve it and release a new update.

I really appreciate your efforts, thanks!

Arceo

This will indeed be included in the manual and should have been from the beginning. My apologies.

@haydnwalker said:

If not already DP users need to be warned of this issue. It just totally screwed up a deadline of mine!!

Sorry to hear that.. 😞

Didn't "Freeze" turned helpful for your job?

Anyway I hope that Karel and his team wil soon address this issue.

Best Wishes

Arceo

Hi Karel,

any news about Bounce to Disk addressing issue?

I could really make use of it in a project that starts in a week...

Please let me know, thank you.

Arceo

Unfortunately it seems that this issue is unlikely to be solved due to the way DP handles bouncing, so when using Audio/Event Input plugins in DP, freezing first is the only option at this point. I'll have a look at the viability of a MAS version of the VE Pro 5 Server Interface, which will at least circumvent the single MIDI input port limitation of AU without breaking bounce to disk functionality.

I for one am EXTREMELY excited to have the new VE Pro 5 functionality in DP!!!

Kudos to the VSL team for really listening to their users who have lobbied for a solution to the midi port issue for years now.

Bounce to disk is a non issue for me as I always submix everything down to a final stereo track (and stems) and run a print in real time anyway. The freezing tracks is also an acceptable workaround as I can freeze all my VI's in one pass if need be.

You guys are awesome and I just wanted to land some positive feedback as we often only comment in forums when things are exibiting problems.

cheers!

I'm a very happy DP7 user working with VEP5.

I don't use bounce though - I bus the inputs directly to stems in real time which is something DP can do which Logic and Cubase can't. I go from up to 90 or so VEP inputs to 12 mix stems then down to 3 delivery stems all in a single pass. I found that when I bounced mixes, too often there were glitches so Id have to review the mix anyway so I decided at least mixing to stems in real time, I know the whole mix is clean and it doesn't take any longer than checking the mixes. I still freeze things from VEP and that works fine but I wouldn't do that with each line of a mix unless I was going to prepare prerecords for a protools sessions when working with live players and mixing in an outside studio. Freezing works really well for that.

I'm far more frustrated by DP's lack of 64bit which is causing daily problems. (sigh)

@flashman said:

I'm a very happy DP7 user working with VEP5.

I don't use bounce though - I bus the inputs directly to stems in real time which is something DP can do which Logic and Cubase can't.

What makes you think that Cubase can't do this?

DG

Really can Cubase do that? I never found a way of doing that, but I will go and have another look. I know Logic can't (unless you use Apogee Symphony and VBus). I have to say I'm really impressed with Cubase overall and if I moved off DP then I think Cubase would be a safer bet than Logic at the moment.

@flashman said:

Really can Cubase do that? I never found a way of doing that, but I will go and have another look. I know Logic can't (unless you use Apogee Symphony and VBus). I have to say I'm really impressed with Cubase overall and if I moved off DP then I think Cubase would be a safer bet than Logic at the moment.

Cubase can record directly to an audio track from a Group track or an output (real, or dummy), so recording stems in real time is easy. . Let me know if you want to try it, and I'll talk you through it.

Cubase can also do a quick bounce of stems as well, for those people who don't want to listen to their music as it goes down.

DG

Wow. I should spend more time with it. Our first impressions were that Cubase worked really well with VEP5 but most of us here are DP or Logic so we're not using Cubase day in day out. Another tick in the box for Steinberg.