PlanetZ forums - scopeusers.com

It seems to happen quite often, I will have a project that is near my dsp capacity but sometimes with maybe one or even two bars remaining on the dsp meter (I have three cards 2 x pulsarII & 1 LunaII). All good so far, save & shut down, but when I reopen the project I get the message that I have basically filled up my dsp capacity & would I like to try global optimization? This always works, but it takes a minute or two & is very annoying.

If the project was working before, why the start up problem? What can I do to stop this happening?

I have noticed anecdotally it seems to happen more, it projects where I using flexor modular synths (though this may just be coincidence, I have been using flexor a lot recently)

because of the order that devices get loaded....

I have been beaten up by SFP in similar ways. Here's a fix that I used.

Dissconnect everything, but leave the project intact.

Go to the settings menu, select projects, save the disconnected version as a start up project. Then re connect everything and save as your project as is.

I don't know why this works, except that the disconnected version gives SFP a heads up for what's coming, albeit in a lite version.


Happy Hunting,

thanks for answers & partial solution, I might even try just disconnecting some of the bigger dsp hogs on saving, without disconnecting everything, & see if that works

here's the instant fix that worked for me:

bought an additional srb

cheers
roman

here's the instant fix that worked for me:

bought an additional srb

ah yes, if only that solution was available to me....

one other things I have noticed is sometimes I have to press "yes" to global optimisation it takes two or three times before it works...why? I would have thought clicking on the button would set of fthe same routine each time? does it try different things?

reshufflin....

on the big mixers you can assign a part of the mixer to a specific board,so at least you could even out the workload over the cards.

The code inside of each device can be dynamically loaded across more than one dsp, that way if one dsp is 'mostly' taken but has some small amount of resources still available it can be put to use. This insures that you can actually load on your dsps more than if the dsp code needed to be loaded in a fixed way every time, but the downside (as you've seen people say here) is that it tends to load differently each time.

It's been said several times here before but just in case the newer users were wondering