"Unexpected DSP Overload".....help

Derek_K · Post by **Derek_K** » Mon Jun 23, 2003 3:42 am

GARY: SORRy ...but what is dma?

Derek_K · Post by **Derek_K** » Mon Jun 23, 2003 3:42 am

GARY: SORRy ...but what is dma?

Derek_K · Post by **Derek_K** » Mon Jun 23, 2003 7:07 am

i'm not sure???? sorry for being difficult!

Post by **garyb** » Mon Jun 23, 2003 12:20 pm

Direct Memory Access.this option MUST be enabled in the hard drive settings in the device manager in the control panel window.

a better option would be to install the latest version of intel's applications accelerator(iaa)available on the intel website,free.

also,before ANYTHING was installed,i hope you installed the mobo drivers.

without these steps nothing will work right.

orbita · Post by **orbita** » Tue Jun 24, 2003 12:54 pm

Hi Kim,
It's interesting that you suggest Minimax has caused problems of this nature since I also discovered dsp overload problems with a project using only 3/4 dsps on my 33dsp system and yet when I removed minimax the dsp overload messages went away. However, I only ever run at 44.1khz.

I also use the 48channel mixer pretty much all the time so that I can have space to have my various external synths and asio channels permanently patched in. Could this mixer be causing problems do you think?

Maybe I should start using the 24channel mixer and only attach the modules that are required for the project.

On 2003-06-22 06:19, kimgr wrote:
@dehuszar: I don't quite understand the reasoning in your post, or what the Creamware guy meant, but:
You need as many S-TDM connections between cards as possible. They carry a certain number of audio channels between the cards.(144 @44.1/32bit pr. cable if I remember it corectly.) So, more cables= More channels.
In the example above with 2 Scope cards and a Luna, you connect 5 cables between the 2 scopes, and the first cable goes on to the Luna.

About the "unexpected dsp-overload" message:
Usually it has nothing to do with hardware setup or software installation;
It is specific devices that's causing it, under certain conditions...
One example is the Minimax: It does not work proberly in 96KHz. Another example is the big mixers, with phasecompensation on.
It has to do with dsp allocation as far as I can tell; What will fit on one chip at 44.1 or 48, wont at 96. (I'm fighting with this on one of my own designs.) So the Minimax and other devices will need an update to function proberly at 96KHz...

Kim.

orbita · Post by **orbita** » Tue Jun 24, 2003 6:54 pm

hm its happened again
Ive been working with a project this evening. Pretty simple one with the 24 channel mixer and sts5000. everything running fine. I added the minimax and still all fine.
I save everything and reboot the computer. Now when I load my project I get continous DSP overload messages. When I drop the voices of minimax to 0 the dsp overload messages go away.
As soon as I readd the minimax voices the errors come back.
Ive tried reinstalling the latest version of minimax and its still occuring.
hmm

Immanuel · Post by **Immanuel** » Tue Jun 24, 2003 6:58 pm

tried removing the minimax and reloading it?

orbita · Post by **orbita** » Tue Jun 24, 2003 7:22 pm

ok this is getting interesting..

First I tried what you suggested Immanuel. I removed the minimax and reloaded it. I expected that to work but really to be an inappropriate solution since this dsp overload is occuring every time I reload the project. As it is, it didn't work.

Normally when I try to resync the project after these dsp overloads occur I try the following..
i) set sync to slave and then back to master
ii) set clock rate to 32khz and then back to 44.1khz

In this situation setting to slave and back has no positive effect and when I set it to 32Khz it manages to get sync but when I attempt to return to 44.1 it loses sync again and the dsp overload error reoccurs.

However, and this is where it gets interesting...

If I change to 48Khz it syncs fine! And when I try to return to 44.1Khz it successfully manages to retain the sync and the dsp overload error goes away!!!

So it looks like I have a solution, lets hope it remains relevant whenever this error occurs!

I wonder if it is a problem due to the various syncing going on.

I have all my digital ports connected as follows.

Luna ZLink -> Creamware A16 (1) 1-8
Scope ADAT A -> Creamware A16 (1) 9-16
Scope ADAT B -> RME ADAT1 on 2nd PC
Scope ADAT C -> RME ADAT1 on 2nd PC
Scope ZLink A -> Creamware A16 (2) 1-8
Scope ZLink B -> Creamware A16 (2) 9-16
Scope SPDIF Coax -> RME SPDIF
Luna SPDIF Coax -> Lexicon MPX1
Scope SPDIF Opt -> Lexicon MPX200 (via Opt/Coax Convertor)

The creamware cards are set to Master, everything is slaved.
Do you think something about this digital configuration could be causing these problems?

***update
I tried the syncing to 48khz on previous project with minimax that was having dsp overload problems and it didnt work, so it doesnt seem to be a fix all solution.

[ This Message was edited by: orbita on 2003-06-24 22:02 ]

huffcw · Post by **huffcw** » Wed Jun 25, 2003 9:32 am

I have had this issue on a PowerPulsar 15 DSP board (only one card in the system). It only appears for me when loading MiniMax for the first when there is at least 4 DSPs out of the 15 being used (it has never come up with any other device and doesn't appear when loading a second Minimax).

The project I am using in particular is only taking up about 4 or 5 DSP out of the 15 -when i load Minimax into the project, I get the problem. The project is running at 44.1khz with multiple ASIO 2 in/outs and ADAT modules. The project also is using the STM 2448 mixer.

I have sent a request to Creamware for help with this issue - hoping for a resolution.

[ This Message was edited by: huffcw on 2003-06-26 09:33 ]

huffcw · Post by **huffcw** » Thu Jun 26, 2003 8:10 am

By the way, when I was running MiniMax with a regular Pulsar card a while back, I never got this error. It only happens with my newer PowerPulsar card. MiniMax is the latest version as far as I know (it was downloaded as part of the synths and sampler pack).

Steve-o · Post by **Steve-o** » Fri Jun 27, 2003 11:17 am

Just bought MINIMAX - same prob here - instant DSP overload and heavy LOUD NOISE when loading NU2 with MINIMAX in project.
...strange phenomenon!

Any ideas?
Steve-o.

huffcw · Post by **huffcw** » Fri Jun 27, 2003 2:11 pm

This is starting to sound like a bug - that needs to be addressed by CreamWare

huffcw · Post by **huffcw** » Sat Jun 28, 2003 10:42 am

Here's an update...

I reported this problem to Creamware and it has been forwarded to the programmers to take a look at. Hopefully they will have a resolution as quickly as possible.

DJOrpheus · Post by **DJOrpheus** » Tue Jul 01, 2003 5:53 pm

..yes, holy jesus. I´m having exactly the same problems with minimax. It really seems mainly minimax is causing this troubles. I have 2 Scope´s and when loading a new empty (ok, nearly empty) project i get this same errors after loading 2 or 3 minimax. Never have this kind of problems with heavy project that don´t use minimax. I hope the creamware-developers catch this anoying bug in my loved minimax

Hope we get some more details about this issue from the programmers...

huffcw · Post by **huffcw** » Tue Jul 08, 2003 12:59 pm

No updates yet from Creamware - hoping to hear something soon.

Kamurah · Post by **Kamurah** » Tue Jul 08, 2003 10:03 pm

Thanks very much for keeping on top of this....I love MiniMax and want it to work properly.

I would be curious to know.....

My system is XP. Which version of Windows is everyone else running? Maybe a relation there?

Cheers

huffcw · Post by **huffcw** » Wed Jul 09, 2003 8:13 am

I am running XP also.

Zer · Post by **Zer** » Wed Jul 09, 2003 11:16 am

in case of updates I woudn´t expect too much since every ressorces they have got is focuused to the noah...their company needs money very badly soooo....

Immanuel · Post by **Immanuel** » Wed Jul 09, 2003 5:16 pm

Oh please - not that again. Look around in the forum. It is flooded with outdated threads about CWs money-issues. Creamware is not broke.

huffcw · Post by **huffcw** » Tue Jul 22, 2003 7:08 pm

Still no updates on this issue from Creamware. Hopefully they are actually looking into the problem and will have it fixed soon.