PlanetZ forums - scopeusers.com

PT LE sucks... I wish I could use my Scope interfaces with Pro Tools software... =/

Oh well.. thank you for all your help.

Just one more thing, why didn't Vinco wrapped like the other plugins?

I think the high CPU is due to using a different driver. I reported this to S|C and they basically did this mode was not supported. Check your HT status. It might hang without it though as multi-threading might be the only thing that keeps the system alive.

Yes, you can tread the DSP as regular ...

I think the high CPU is due to using a different driver. I reported this to S|C and they basically did this mode was not supported. Check your HT status. It might hang without it though as multi-threading might be the only thing that keeps the system alive.

Yes, you can tread the DSP as regular ...

I've had some CPU issues too, but that was even using the Scope ASIO driver. With as different driver the system would just hang. Now I have tweaked the DAW to work nicely with the Scope ASIO driver, but haven't tested again with a 3rd party driver. I can try again and see if the system hangs. If ...

I did it!
Since my Mac Pro only has PCIe slots, I installed my Pulsar 2 (6DSPs) on a PC with an MBox while having my Mac Pro with a Digi003.

I wrapped the VSTs to RTAS and have most of the plugs working (masterverb pro, optimaster, delays, phazers and such... but I can't get Vinco nor PSYQ to work ...

Tau wrote:I think the Mac Pro doesn't have PCI slots, only PCI-E.

You'll need an external PCI chassis, such as a Magma, or a Scope PCI-E solution, such as the XITE-1

Cheers,

T

Won't I get into hardware conflicts?

Thank you so much for all your help. =)

By the way... does anyone knows of any problems on doing this in a 2 x quad-core intel xeon mac pro (OSX 10.5.7)?

And on having 2 scope cards connected to each other, one with 4 DSPs and the other with 6 DSPs (in the same environment)?

Sorry if there's ...

Yes, the processing will be on DSP. Some CPU is required for GUI and interfacing, but that is necessarily not only fo XTC mode.

Everything you need to know is posted in this thread and or related threads linked to in this one. Please re-read it.

You might also want to locate the "XTC patch guide ...

I think you mean the scope plugins.

If so the answer is that any scope plugin is using DSPs.
Keep in mind that there are always also some CPU cycles neede for GUI, I/O etc.
This holds for XTC mode as well, even if these plugins are visible as VST plugins in your VST host.

Your native plugins ...

Can someone tell me if the plugins use scope's dsp or the computer cpu with this method?

Thank you!