Thanks Paul, good to ear it's in your prioriites!

Yes, not so simple in fact, I gess...

For the Acqua/Acustica thing, I'm going to dig further because, in my slave (2x Xeon), Reaper is rejecting them too. They are working in my DAW machine (i7) with Cubase and Reaper (same W7x64 OS).

So maybe no a VEP problem.

Can't try to scan them with VEP in my DAW because I only have one license and this will mean two physical dongles plugged in the same machine (CUBASE&VEP)

I had installed Reaper to try the REAMOTE thing (deporting FX computing over LAN) because of the lack of success in VEP with Acustuca's (Only an old N4 version is accepted at scan and very slugish when Acquas's are encapsulated, not usable)

Have a nice day.

I'm strongly waiting this also to be able to deport those heavy Acutstica great sounding but CPU killer plugins.

The insert trick will not work in Cubase due to de VSTi nature of the VEP plugin witch can't be inserted in an audio track. So bound to return to instument tracks :-(

Adding a VST (fx) dll, vst3 (fx) or AU (fx)... for VEP return would be the solution. With the capacity of returning any choosen (pair of) ouput track(s) of the selected instance (FX or Instrument why not?). This seems no so hard to implement, it's the reverse path of the VEP audio plugin.

Maybe we could have to choose between two kinds of instances, Intrument or FX but this not seems necessary with the idea above of the "universal" returning plugin witch would allow very flexible routing capabilities, even for instruments.

@Paul?

Also, speaking of Acustica, VEP7 is rejecting all my Acqua plugins at scan (vst2).

The only solution is encapsulating them into N4 witch is acceped by VEP.