Uniwire & Protools 8

[dtmprod]

I own Receptor Pro & use along with PTHD. I've tried using Uniwire with the VST wrapper in the past with PT 7, but it was never stable enough to use. I just updated to Leopard & PT 8 & just tried using the wrapped Uniwire again. Voila! Everything works really well. I created a small demo session with mostly Receptor instruments & a couple RTAS VI's. It runs really smooth without any hiccups so far. I'm able to close the session & everything boots back up & works just as before. I'm a happy camper. I'm running on an older PPC G5 dual 2.7.
Dan

[batgab]

Nice!

[mrmost]

I own Receptor Pro & use along with PTHD. I've tried using Uniwire with the VST wrapper in the past with PT 7, but it was never stable enough to use. I just updated to Leopard & PT 8 & just tried using the wrapped Uniwire again. Voila! Everything works really well. I created a small demo session with mostly Receptor instruments & a couple RTAS VI's. It runs really smooth without any hiccups so far. I'm able to close the session & everything boots back up & works just as before. I'm a happy camper. I'm running on an older PPC G5 dual 2.7.
Dan

What PT buffer size settings are you using? My experience with the old protools was that it worked at, say, 512 but not at the other sizes. And can you let us know what the plugin's latency setting reports, and receptor's buffer size reports, when it is working? And what PT hardware you are using?

Thanks! This is great news.

- Michael Ost
Muse Research, Inc.

[dtmprod]

Yes, I am running at 512 buffer with Protools HD. I'm using a 192 interface. The uniwire plugin shows a latency of around 1532, if I remember correctly. I don't engage an audio input channel like they normally do for rtas vi's. Now I did experience some flakiness yesterday when I instantiated some more cpu intensive 3rd party vi's like machfive, omnisphere, etc. But a quick reboot of the session got everything running again. I am running with just 1 processor like they recommend, but I'm gonna try with both engaged & see if that makes a diff. But if I'm just running uniwire & smaller programs like Hybrid, Xpand, etc, it feels real solid & reliable.
So when are we gonna have more of these vi's ported over to the receptor? I wanna be able to arrange everything off my receptor & forget about trying to run vi's in the mac.

[looneytunes]

If I understand you correctly, you won't be able to run Hybrid/Xpand (etc) on Receptor. These are purely RTAS plugs, and Digi doesn't port them to be run on anything except the SAME HW/DAW ProTools is running on. Digi also doesn't let others hosts port Digi RTAS plugs.

The only thing you can hope for is that VST plugs will be ported to Receptor, and then they will be "seen" in the DAW (via Uniwire).

Hope this makes sense, Regards,
Kevin L

[dtmprod]

If I understand you correctly, you won't be able to run Hybrid/Xpand (etc) on Receptor. These are purely RTAS plugs, and Digi doesn't port them to be run on anything except the SAME HW/DAW ProTools is running on. Digi also doesn't let others hosts port Digi RTAS plugs.

The only thing you can hope for is that VST plugs will be ported to Receptor, and then they will be "seen" in the DAW (via Uniwire).

Hope this makes sense, Regards,
Kevin L

I realize that Hybrid, Xpand only run in Protools, I'm not trying to run them in Receptor. Just trying to point out that instantiating large cpu intensive plugins within Protools while running Uniwire tends to mess up the Uniwire connections. If I stick to less intensive plugins, I can keep working. But some of these 3rd party plugs like Omnisphere, etc would be much better to run in Receptor. Just wishing that Muse would port them over sooner.