Looking for how to host VSTi inside Pro Tools 12

[Darryl Ramm]

32Lives does AU and VSTi and runs in Patchwork if you need it. But the simplest approaches are nearly always best.... just run Native AAX-64, run Bluecat Patchwork if needed for VSTi, add 32Lives! If 32 bit is needed, and by all means run VEP if you need to offload stuff, it's the go to choice there.

Sent from my iPad using Tapatalk

[lesbrunn]

I use loads of VI's, and Pro Tools usually doesn't like that, so I mostly use the VSTi' versions in both VE Pro and Patchwork. They are both reliable; Patchwork is cheaper, but crashes certain plugins in PT. VE Pro runs those same plugins smoothly. I run just a few AAX Vi's directly in PT.

[briaboy]

Originally Posted by cshaw

I use blue cat patchwork as well with no problems. If you also need to run 32bit plugs then buy a copy of 32Lives.


Sent from my iPhone using Tapatalk

Agreed, then you can use VSTs and AUs, as well as AAX.

[Franklyn]

Originally Posted by briaboy

Agreed, then you can use VSTs and AUs, as well as AAX.

+1

Blue Cat Audio Patchwork is the best for me, because:
1. you can you use AU & VST Plug Ins
2. Starting Patchwork dont need time scaning new installed AU & VST. You have only to to open the Plug In on your Harddisc without waiting
3. You can make Plug Ins Chains and Paralell processing
4. Works with very low latency
5. You can use Patchworks and Patchwork presest on different other Apps as AU, VST, AAX Plug In (Logic, Cubase, Maschine, Ableton) and use the same Presets
6. DOnt need more CPU as the same Plug In in AAX
7. its very easy to use you dont need any manuals.
8. It works very stabil in PT

I tryed a lot others and I am very happy with this Tool

[theom]

When you use Patchwork as a VI host are you running the stand alone application and rewiring back into PT? Or do you use the AAX plug-in version?

[Southsidemusic]

I think everyone use it as a insert plugin in AAX64 bit in PT

[lesbrunn]

I agree with Darryl that the simplest, most direct route should be best (AAX). But in the world of PT, it isn't always so. PT has a long history of problems when you run tons of Vi's simultaneously, so I use only a few tried and tested AAX Vi's. The rest are hosted so PT doesn't see them directly, only sends MIDI and receives audio. This simplifies things for PT, and I have very few crashes these days, compared to when all my Vi's were in PT.

Patchwork is great if you want to run a few VSTI's. If you need to run tons of them, VEP is the most elegant solution yet that I know of. Reaper worked very efficiently for me some time ago when I had a less powerful PC, but the routing was murderous. I couldn't route stuff quickly on the fly, so I used the excellent templates provided by Shan and modified them to suit my workflow. I dropped Reaper like a hot coal after trying VEP, which is extremely intuitive once you've wrapped your head around the way it works.

[musicman691]

Originally Posted by lesbrunn

I agree with Darryl that the simplest, most direct route should be best (AAX). But in the world of PT, it isn't always so. PT has a long history of problems when you run tons of Vi's simultaneously, so I use only a few tried and tested AAX Vi's. The rest are hosted so PT doesn't see them directly, only sends MIDI and receives audio. This simplifies things for PT, and I have very few crashes these days, compared to when all my Vi's were in PT.

Patchwork is great if you want to run a few VSTI's. If you need to run tons of them, VEP is the most elegant solution yet that I know of. Reaper worked very efficiently for me some time ago when I had a less powerful PC, but the routing was murderous. I couldn't route stuff quickly on the fly, so I used the excellent templates provided by Shan and modified them to suit my workflow. I dropped Reaper like a hot coal after trying VEP, which is extremely intuitive once you've wrapped your head around the way it works.

Enjoying VEPro 6 for instruments; haven't used it for effects yet. The routing in and out of it isn't so much of a problem per se but the labeling used is - there isn't a good example anywheres in the documentation or on the net of exactly what everything means in a routing selection. What is needed is a good example of what each word or term in a routing selection in PT means (what is the server instance, what is the track in VEPro, etc.). I ended up learning this piecemeal with one server and one instrument in VEPro and escalating from there. Wasn't easy and when anyone starts to get into this I suggest making plenty of notes on what is what.

[lesbrunn]

Originally Posted by musicman691

Enjoying VEPro 6 for instruments; haven't used it for effects yet. The routing in and out of it isn't so much of a problem per se but the labeling used is - there isn't a good example anywheres in the documentation or on the net of exactly what everything means in a routing selection. What is needed is a good example of what each word or term in a routing selection in PT means (what is the server instance, what is the track in VEPro, etc.). I ended up learning this piecemeal with one server and one instrument in VEPro and escalating from there. Wasn't easy and when anyone starts to get into this I suggest making plenty of notes on what is what.

+1. Not exactly a steep learning curve, but it took me a while to understand how it worked. I also learned it the same way you did. The documentation could have been 10x better. That said, once you understand what they are trying to say, it's very simple.

Ive tried it on effects too, and that has to do with sending audio from PT to an input channel in VE with the effects on that channel and back into PT. I tried that once with parallel effects. You can smash/EQ/ distort the sh**t out of a signal before sending it back into a parallel PT channel. Also very easy once you get it. Works very well.

I use both VEP and PT on the same PC smoothly without issues. Sometimes with 10 to 25 channels of VI's into that many PT channels (you can also mix it all in VEP before it hits PT). I sometimes add compression/EQ etc before sending the synth tracks into PT. No sweat at all. Just try doing all of that in PT alone and see how complicated your life will suddenly become!

[Southsidemusic]

Why would one need VEP? We are finnishing up a two song job for one of the best imho artists out right now
(even though she is a former Disney Star) with 211 tracks and we have 38 VI instances not yet bonced to audio with 29 VI already printed and bonced, still everything runs like a dream on the nMP with 32GB ram so why would we need VEP? Anyone who can sell me on that would be great