DSP sync/async ?

King of Snake · Post by **King of Snake** » Mon Oct 22, 2007 11:45 am

Hey guys,

can ayone tell me what the "sync / async" values in the Scope dsp meter indicate exactly? More precisely, what does it mean when it indicates what looks like an unusually high async value for a particular dsp.
I've been having some problems lately with unexpected dsp overloads and noticed sometimes a very high async value on one of the dsp's.
Wondered if it might have anything to do with eachother.

valis · Post by **valis** » Mon Oct 22, 2007 11:49 pm

This probably has a lot to do with the devices you're currently favoring.

King of Snake · Post by **King of Snake** » Tue Oct 23, 2007 3:09 am

hmm, well according to the DSP meter I'm not really maxing out the power or anything. There were also some communication errors with one of the boards though so yesterday I took out all the cards (1x Powersampler, 1x Pulsar 1, 1x Pulsar 2) and reseated them and the STDM cable. Will have to give the thing a good run-trough again tonight to see if problems persist.

btw the Pulsar 2 has two STDM connectors... does it matter at all which one you use?

still curious btw if it is normal/harmless if the async value for any of the DSP's is very high? Does it indicated anything wrong with the project? I noticed that if I reloaded the project the high value would dissapear...

valis · Post by **valis** » Wed Oct 24, 2007 1:36 am

Reloading the project causes a reallocation of resources.

King of Snake · Post by **King of Snake** » Wed Oct 24, 2007 4:17 am

I realise that

dante · Post by **dante** » Fri Nov 09, 2007 12:11 am

Ive had DSP overload and communication errors coming from scope, only to find the problems have occured elsewhere in my system. EG if I have overloaded Cubase (native CPU ) or Reason - for example streaming large NN-XT sample libraries in Reason from an external USB drive. Stressing the PCI bus or the native CPU in any way shape or fashion seems to result in SCOPE errors even if its not the SCOPE DSP's under stress, but some components of the host system itself (such as PCI / USB / CPU ).

Ive seem the Cubase performance meter max out but it isnt Cubase that complains - its SCOPE that detects the problem and reports it first.

Does anyone else have this experience ?

valis · Post by **valis** » Fri Nov 09, 2007 2:50 am

The Asyc portion executes on the host cpu and communicates back & forth to the dsp's. Overload the cpu and Scope will complain about not getting its data in time, just as with ASIO or Midi errors. Don't mistake me to mean that a high cpu load affects the Async values displayed in Scope's dsp meter though, that's entirely dependant on what you have loaded in Scope. And again for King Of Snake, if you're seeing more Async usage than you're used to in the past I suspect it's due to the devices you're preferring lately.

valis · Post by **valis** » Sat Nov 10, 2007 9:14 am

Mind you that's entirely surface level insight (or even heresay) as I have no access to the Scope code, just info I've gathered from conversations here & there.