Audiport RTAS wrapped with "VST to RTAS"?

[blizzard]

Has anyone here had any luck with running Audioport within ProTools with the FXpansion VST to RTAS adapter?

Fingers crossed...
Andrew

From the Audioport FAQ:

Does AudioPort Universal work as an RTAS plug-in within Protools 8? Or would I have to wrap it with a VST-to-RTAS Adaptor (wrapper) from FXpansion?

We have recently attained promising results in initial tests using FXpansion's latest RTAS-to-VST wrapper around AudioPort Universal's VST plug-in on a PC in Protools 8. We have yet to test it on a Mac. As they say in the car ads, “your mileage may vary,” and at this time we can’t recommend such a solution until we have done more extensive tests.

[JH4music]

This did not work for me. The plugin would open and connect to the host properly, but the audio coming through was static. But, I am using Pro Tools TDM 6.4.1 on OS 10.3.9 though, which doesn't run on the newest version of the VST to RTAS wrapper, so it may work in PT 8.

What does work excellent for me is running Plogue Bidule as a rewire device, and hosting the audioport VSTs in there. You can configure Bidule to have as many as 96 rewire outputs.

[blizzard]

Well that seems like a do-able option. I am probably going to be upgrading to PT8 and I have the newest VST to RTAS so when I get a chance maybe I'll test it.

What kind of latency are you dealing with using Bidule?

So then when loading a project you have to load the ProTools file, then the Bidule template, then on your Slaves you also have to load your Virtual Instrument project? Or does Audioport automatically load all your instruments that are hosted?

I would love to have a setup that I only have to load the ProTools file and everything is loaded immediately (like FXteleport does). But if not, no problems, as long as I can get low latency I'm happy.

Thanks,
Andrew

[JH4music]

Latency is negligible, I haven't bothered to measure it because since I've offloaded many of my templates to audioport slaves they still sound exactly the same.

You can save an entire template on each slave, it's as easy as opening audioport and opening the file, it loads everything you had the way you saved it. On the recieving end you need to open PT, wait for Bidule to launch as a rewire device, then open a saved template within Bidule. Not a one click solution, but easy enough.

On my pro tools system I also have to manually assign the IP address and channel pair for each audioport pair if the computer has been rebooted, but it only takes about a minute to do... I just name each VST object in Bidule as the channel pair and last 3 digits of the IP of it's slave machine, so I know exactly what to click on. I'm pretty sure this is only because this system is older(G4 PPC with OS 10.3.9), so I have to use the older discontinued/unsupported PowerPC version of Bidule on it.