PlanetZ forums - scopeusers.com

New Computer - new porblems.
I fetched myself an abit NIS7 with Corsair Dual DDR 400 Ram , 1 Gb, 2 x serial ATA Raid H´ds running my pulsar 1 and pulsar 2 SRB. In the driver menu the bitdepth is locked to 16 bit. I can only run the system at the highest latency. Selecting 13 ms for 44.1 khz samplerate will force the mai´nboard to beep and shutdown the computer, although I changed the systems setting fo maximal cache for hidden services as it is recommended for lowest latency.

With my old one I have been able to operate at 13 ms latency.

Sometimes whe I open just one synth I get the message: DSP capacity limit reached.
(I got 10 DSPs - pulsar 1 and 2 srb)

Does anybody have a clue on this?

only guessing; pci trouble
Looks like your pc would't let CW work as expected.

right, the message almost certainly reads: PCI capacity limit reached
afaik Windoze doesn't care about bit depth - you can use a 24 bit driver but it's just not visually represented - the same applies acoustically...

cheers, Tom

Well, i know just too well theis 'DSP capacity limit reached' message. And it's different from 'PCI capacity limit reached'

I also have Pulsar1 mixed with new generation card (luna2) and this message appears when scope has trouble loading stuff onto dsp.
Or when dsp code is split between the two cards.

Never found any solution for this except thrash the pulsar1...

Sorry

If you use 96khz, the "DSP Capacity Limits Reached" thingy can happen if you try to load a device that is too big for a single card (like a big STM mixer on a Luna.) You can partially resolve this by putting the board with the most DSPs as the first one (involves a bit of CSET.INI magic.)

If your problem involves projects that used to work fine, then I don't know. Maybe the order of the cards changed between the 2 installations, so I guess it's worth trying the .ini stuff.

well the cpacity limi reached feture is gone since I tried different slots...but I still have different settings for both cards in the device manager?!

And I just could get the 13 ms latency at 44.1khz with editing the cset.ini to 512 k.

PCI clock issue? I tempered the bios using 64 instead of 32. But that didn`t change anything.

I`m still cluesless.

by the way - Did anybody ran dxdiag without error messages those days?

Pulsar 1's don't go under 13 ms latency.

On 2004-10-18 16:56, symbiote wrote:
Pulsar 1's don't go under 13 ms latency.

If coupled with generation 2 cards the latency is managed by the new ones, so the platform behaves like there were only new cards.

I have a Scope, a Pulsar2 and a Pulsar1 with 1 STDM cable for all 3 and another one only for Scope and P2. The P1 is shown as last card in the dsp load values panel (where the laods are shown, not in the header), and I had this dsp overload very very rarely, maybe 1-2 timws every 6 months. I usually like to run huge projects with all real time.

I get the main monitoring (ADAM), the recording AES-EBU inputs and an adat connection for noah from scope, P2 analog outs go to an amp with ns10's and I use P1 left analog I/O for a vintage davoli spring reverb (transistor but point to point, great on guitars and it's fairly flexible with levels). All midi ins are used too.
So I need all the cards, and fortunately they give no probs..

<font size=-1>[ This Message was edited by: alfonso on 2004-10-18 19:23 ]</font>

Yeah I knew that 13 ms issue, but I wanted at least 13 ms, which i only got by editing the cset.ini to 512. If I use the Ulli settings in the menu, the mobo beeps and the computer is shutting down.

And I weren`t lucky to ste the boards in the cset.ini to make the pulsar 2 SRB the master one.