Hi,

I've been using VEPro for a while without issue…The current feature film I'm working on has a smaller template than I've used previously on this machine, yet I'm running into problems with both Protools and VEPro quitting.

There are so many variables and options I was wondering if anyone could give some insight?

I'm running the latest version of VEPro, and Protools 10.3.8 on a Mac 6 core Westmere with 24GB RAM, on 10.8.5. VEPro and Protools are hosted on the one machine, and CPU usage rarely goes above 25-30%.

Mostly what is loaded in VEPro is Kontakt instruments, but I also run Dimension Brass and Omnisphere, and the occasional other synth. I run the 64bit VEPro server with KMS not enabled, and Omnisphere set to 'streaming'.

The version of Protools I've installed was a clean install. I've also done the usual PT troubleshooting (trashing databases and preferences), and I've also done a clean install of VEPro and trashed the preferences I could locate!

I run Disk Cache set to 'normal' in PT, and assign 5 cores.

As I say I've run much larger templates on this machine (albeit on Lion with an older version of VEPRo), without issue.

Most of the crashes seem to come when closing PT and opening another session. Either PT goes, or VEPro goes.. Either way they both have to be restarted as VEPro shows as busy unless they are both restarted.

I'm happy to post crash logs if that helps, but I wondered if there was a good place to start for general troubleshooting for VEPro? Maybe there are preferences I haven't properly trashed..?

It would also be useful to have some insight as what best to set the number of threads to in VEPro? 12 are available on my machine, but clearly some will be in use for PT.

Thanks for your help in advance.

Thanks for the input (scuse the pun) chaps....I think I might try an expression pedal under the left foot.... Not as obviously intuitive as a breath controller (especially for a trumpet player like myself...) but better than the other apparent options (none..!)

Thanks for the reply. However, it's not the input that I require... There are lots of options for that, and I already have an input in my DrumKat... The problem is that nobody is currently manufacturing a breath controller.... The Yamaha BC3A which was their last model is now discontinued and has not been replaced.

Hey all,
Just looking for suggestions really.... Ideally I'd be looking for a Yamaha Breath controller, and I have an input to use one (a BC3) on my DrumKat... However, they're no longer in production, and I've been looking out for old stock, or second hand for a while with no joy.

Any thoughts on a useable plan B?

I guess an expression pedal would be one way to go, but my gut feeling is that it's not going to be as natural to use as a Breath Controller (especially for brass and winds)

What other options are out there...?

I too would prefer a clearer and more intuitive labelling for instruments within VEPro...
I'll happily send a message to AVID, and perhaps this could be addressed in a future release (although this would not help either myself or Jeremy, as we are both on PPC, and have sadly been end-of-lined...!)

However, I can't help but notice that Bidule does deal with port naming in a more intuitive way than VEPro. Perhaps I'm comparing Apples with Oranges here, and probably not understanding the issues, and how they might be resolved...?
But when a new instrument is created in Bidule, you name it, and it's name comes up as an option within PT.

For me, something akin to this this would be a fantastic improvement to speed of workflow with VEPro. When running large sessions it's certainly easy to get in a tangle with a lot of numbers....

I'm not sure what you're meaning?

Yes, there are issues with RTAS. However VSL do offer an RTAS format plugin, and as a PT user this is what we're stuck with. My question was simply whether VSL are in a position to improve the RTAS performance of their plugin, or whether there is an issue from Digi or Apple's side which creates a reduced performance?

For what it's worth, there are some plugs which do actually perform better as RTAS than other formats (Superior 2 being a good example). Digi have always claimed that poor RTAS performance has been driven by poor coding. This was specifically in response to questions regarding EW Play. I am simply trying to ascertain whether improvements to the behaviour of the RTAS version of VEPro are on the list for VSL

Hi,
I've been checking out the performance of VEPro with my rig, and slowly feel as if I'm getting somewhere (!)... It does in many ways open a lot of doors with regards to big VI setups.

I can't help but notice however that the CPU hit using VEPro within Protools is significantly higher than it is using the AU version within Ableton Live or Reaper.... Using JUST the VEPRo plug in PT I get CPU spikes hitting 50-60% with the base CPU level at around 38%. On the same machine in Ableton it's more like 6%, with no spikes. This is running at a buffer of 128 both times. I know 128 is low, but it is necessary for recording edrums!

I fully appreciate that there are issues with RTAS at the moment, which hopefully AVID are apparently in the process of addressing. I also am aware that my DP G5 2.3 is woefully underpowered and thus perhaps not the best machine to be running.... However there are a large number of PT users stuck on G5 models due to Apple's switch from PCI to PCIe (actually I'm not one of them as I have a PCIe machine..!) who would benefit HUGELY from the increased number of VI's able to be hosted using VEPro and a slave machine.

I wondered if there are any plans to improve the efficiency of the RTAS version of VEPro, or if indeed it CAN be improved?

Many thanks

Jon Atkinson