VE Pro crashing ProTools 8 on session close

[ThpMusic]

It took me days to figure this out, so I thought I'd post it here in case anyone else has these troubles.

My scenario was PT 8 running VE Pro on the same machine.

For some reason upon closing a PT session I would great crashes every time when VE Pro was running.

I finally realized that VE Pro was fighting with the other Plug-in Aux tracks I had open within PT.

Specifically Kontakt. I had Kontakt instantiated within PT and receiving two aux channels (ST2 and ST3). I also had VE Pro receiving two aux channels (NET3/4, NET5/6). That apparently was causing the crash.

I noticed VE had kicked Kontakt off the channels. So when I changed VE to NET11/12 and NET13/14 (skipping the lower numbers that Kontakt was using) everything worked perfectly.

These bugs may not exist in PT9 but I'm under a huge deadline and can't afford the time to update right now.

Hope that helps somebody.

[tonwurm]

thanks ThpMusic for posting this - it´s very appreciated

exactly the same was happening on some projects with my setup, but I didn´t figure it out what the culprit was

I´ll check this out and post the result back here

[ThpMusic]

After days of crashing every time ProTools closed a session I realized there is a big problem with having multiple VEP instances. I believe the trouble comes when Importing Data into PT from another PT session.

I notice when built from scratch the Aux Inputs in PT add a ".1", ".2", etc to VE Outputs within the channel strip (though when you click on the insert to view your input choices the ".1" distinction disappears). Apparently PT is does this to sort out the multiple instances. There is also a conflict with RTAS instruments within PT fighting with the VEP Outputs.

Loading an instance of Kontakt in an instrument channel along side of an instance of VEP and the trouble begins. If both have Aux inputs set up to receive Outs 3/4 there will likely be a crash upon closing the session.

Is anyone else experiencing this? Was this fixed in PT9?

[bashville]

I think this is somehow related to another problem I was describing in this thread below. Funny somebody mentioned the issue occuring when importing tracks.....

http://duc.avid.com/showthread.php?t=306305

For the record, I had similar issues when I was trying to use VEPro. The biggest reason I stopped using it, though, was not being able to start and stop my PT session when I was inside the Vienna app (used it on the same machine). I really wish it could be used as a Rewire app when you run both on the same machine. Doesn't Kontakt have some trick where they get around the 32-bit limitation even when you're using it as an RTAS plug-in?

[DarylG]

Originally Posted by bashville

The biggest reason I stopped using it, though, was not being able to start and stop my PT session when I was inside the Vienna app (used it on the same machine).

This won't be a problem with VE Pro 5.

D

[ThpMusic]

What is this VE Pro 5 you speak of?

[Keybeeetsss]

I usually have @least 3 instantiates of Vepro.. No more than 5.. No probs other than when I was running version 8008 which was a bad build..

Can u guys PLEASE explain to me why ur running K4 in PT instead of Vepro? Thatz part of the problem there if u ask me...

Sent from EPIC 4G using Tapatalk On'eim...

[DarylG]

Originally Posted by ThpMusic

What is this VE Pro 5 you speak of?

It's the update to Vienna Ensemble Pro 4 that is due out some time over the net couple of months.

D

[bashville]

Originally Posted by Keybeeetsss

Can u guys PLEASE explain to me why ur running K4 in PT instead of Vepro?

For one, I'd rather deal with just the playback buffer within PT as I'm playing, and not having to add the VEPro buffer on top of that, which still applies in playback after I've played. So I have to take that extra delay into account. I'll admit I might not have looked into this enough, but tiered levels of delays start making my head spin...

The other downside with the VEPro concept for me (and I'm well aware this may only apply to me) is that I'm already dealing with multiple outs from the VEPro, then I have to conceptualize the multiple outs from VI's within the Vienna shell as well. BFD used to conveniently name its outputs meaningfully, like "snare, tom1", etc. but with all the VI's mostly using numbered outs (forget about Kontakt's internal design for that), it just gets to be too much. Part of my issue is that I don't do it enough and in a consistent fashion where making a template will be practical for me. So it's only on the edge of being useful for me vs. just biting the bullet and dealing with PT's issues, and keeping it all in one program.

As far as the future is concerned, I suppose anything could happen, including a 64-bit version of PT10, monkeys flying out of my butt, etc.....

[Keybeeetsss]

Originally Posted by bashville

For one, I'd rather deal with just the playback buffer within PT as I'm playing, and not having to add the VEPro buffer on top of that, which still applies in playback after I've played. So I have to take that extra delay into account. I'll admit I might not have looked into this enough, but tiered levels of delays start making my head spin...

The other downside with the VEPro concept for me (and I'm well aware this may only apply to me) is that I'm already dealing with multiple outs from the VEPro, then I have to conceptualize the multiple outs from VI's within the Vienna shell as well. BFD used to conveniently name its outputs meaningfully, like "snare, tom1", etc. but with all the VI's mostly using numbered outs (forget about Kontakt's internal design for that), it just gets to be too much. Part of my issue is that I don't do it enough and in a consistent fashion where making a template will be practical for me. So it's only on the edge of being useful for me vs. just biting the bullet and dealing with PT's issues, and keeping it all in one program.

As far as the future is concerned, I suppose anything could happen, including a 64-bit version of PT10, monkeys flying out of my butt, etc.....

64bit ain't happnening yet; Hence VEPro & K$ which u can use 64bit K4 & whatever VI's u have in it... But whatever works I guess; I've never, & probably never will use K4 in PT; I had it for mths & didn't start using it until I was running VEPro; nut thatz just me...