PlanetZ forums - scopeusers.com

Don't seem to be getting a full run of my DSP's on this project. Going from 5 polyphony to 6 gets the dreaded dsp limit exceeded and as you can see from the screen shot I'm using about half. Can't remember if it's the sync or async that shows the actual load across the dsp's? If it's the async then it appears as if my 2 project cards don't want to pull their weight? Anyone have any tips on how to reduce those "dsp optimization" moments. I've found stepping up the # of voices up one at a time seems to help.

reloaded the project and was able to get 6 voices before the dsp's capped out but still not getting close to the limit on the meter? Does the scope software fill the dsp's on the primary card and then use the stdm bus? or does it spread the work load amongst the 3 cards? or is that specific to the way the device is made?

Hit the green percentage widget in the upper right corner and see whats' up........

Ah, ok so that gives a better idea as to the dsp load? Thanks
Interesting. Not sure if it's just my system or the device but it seems like it doesn't want to use the other two cards for resources. The second screenshot is with some stock synths all loaded up.

I would try to take the modular that has the Waldorf Osc and move it onto one of your other cards. Although the DSP % meter shows how much calculation is going on, I don't think it shows memory usage of each DSP, which is also limited, and which is the problem you seem to be hitting.

I know you can allocate dsp's on the xite. Can we do that on the pci cards?
I gotcha on the async/sync - so it just shows the calculations going on not the memory but what about the dsp bar meter at the top. Shouldn't that be showing close to what's avail in dsp pwr?

hey !

you can try to play arround cset.ini settings , where you can add those lines for
boards load order,
[board0]
boardid=1...
you can check in your manual or maybe in pdf document (not sure where).

when i play arround those settings, i can load almost or full DSP meter, without that annoying error message,
but i must write down proper cards orded in cset.ini

Hope it helps anything

Best,
Matej

Isn't this just because the DxCwm synth has been implemented not to span DSPs or cards, for phase management? That would be the obvious reason, given the stock synths will fill the DSPs happily. What happens if you try to load an additional synth in the first scenario, rather than just adding polyphony?

yeah that's pretty much the conclusion I came to. Nice synth though I suppose I could get by with 5-6 poly. I'll never complain about the many generous gifts we receive on this platform.