core audio / virtual instruments

[rex]

How do I get core audio to recognize my native instruments stand alone applications?

I would use (battery3 for instance) as a plug in but I want separate outputs to the board and it seems like I have to create 5 separate instruments to do that. How can I use it as a stand alone?

anyone anyone anyone?

g4 /sawtooth / 10.4.10 / sonnet 1.8 gig processor / 1gig ram /

dp 5 (slow as a dog) anyway to make it faster?

anyone anyone anyone?

Thank you kindly...

[Frodo]

How do I get core audio to recognize my native instruments stand alone applications?

Generally speaking, you need to open the preferences panels in your standalones to set the desired interface connections there. Built-In or various outputs on whatever audio interface drivers you have loaded will be recognized by the VI and should appear as options in its prefs.

I would use (battery3 for instance) as a plug in but I want separate outputs to the board and it seems like I have to create 5 separate instruments to do that. How can I use it as a stand alone?

anyone anyone anyone?

I don't have battery3, but I would think, once again, that you could assign different outputs from the standalone's preferences. This seems to be essential for something like Battery.

g4 /sawtooth / 10.4.10 / sonnet 1.8 gig processor / 1gig ram /

dp 5 (slow as a dog) anyway to make it faster?

Maxing out RAM is one place to start. Running all those VIs with 1GB total is bare minimum these days. I'm running 10.4.11 and Safari-- just took a peek at Activity Monitor and I see that 490MB are wired. That's about half your physical RAM right there. Doesn't leave much to work with, which means that Virtual Memory will be working overtime. This alone can slow down applications a lot, especially those that shuffle complex audio from one place to the next.

Sawtooth RAM is wonderfully cheap these days, so it's quite a painless upgrade to make.

Now-- you've had a sonnet upgrade. Most of the G4's had either a 1.5GB or 2GB RAM capacity. The first PCI graphics G4 max'd out at 1GB.

I suspect that the Sawtooth featured AGP graphics, so it would take 2GB-- if memory serves me correctly. In any case, don't hesitate to put some more RAM in. Remember that DP as a 32-bit application can address up to 4GB, so give it as much real estate as your computer can handle.

It's an old lesson from the OS9 days: more RAM = better performance. (There are diminishing returns on systems that take more than 4GB, depending upon what application is used and how it addresses RAM over 4GB-- but that's a whole other story.)

Hard drive configurations on this model is another issue. On later models, PCI slots were faster than FW ports. But on the those G4's, both FW and PCI busses were 33Mhz. Still, a PCI eSATA host for external hard drives may yet be the better option.

At some point, though, you may at least want to consider getting a G5 (if you don't want to go Intel just yet). It's things like L2 Cache, frontside bus speed, PCI slot bandwidth/speed that boost a computer's performance (and its apps) just as much or more than the CPU speed itself. Bus clog is among the worst offenders, and there are limits with older systems.

First things first-- check those VI preferences and audio settings to get those working.