14 + 6 + 4 = 24 + 1 more extra DSP free or just bad math !?

[Shamk]

Is there a scope 15 DSP and the DSP count is wrong ... something feel terrible wrong ...

[garyb]

most of the big Scope(Power Pulsar) cards are 15 dsp. only the last few runs were 14dsp.

the meter looks fine to me.

[Shamk]

But below only 14 DSPs are present... why ?

[jhulk]

one is used for communication

[garyb]

if you have a Power Pulsar, it's 15dsp card. as jhulk said, the 15th is redundant and only used for sytem communication anyway.

does everything work? if so, then it's A-OK.

[djmicron]

I can confirm this, it's normal with 5.1 and it runs flawlessly.

[jhulk]

from his dsp usage everything looks great at 50%

on both of my systems 2 x15 dsp and pulsa2

and 1 x15 and 2 pulsa2

both only show 14 dsp for the scope cards as being used for dsp usage

[ARCADIOS]

The DSP meter just reports 1 more, and I believe this is left from the older pro pci boards that were 15dsp cards.
The latest releases of scope pro cards were 14dsp (one dsp less than the older scope 15dsp). You can see where exactly the 15th dsp used to be placed, because there is an empty space with the dimentions of a SHARK dsp + a few chips less at the scope 14dsp cards.
I have one 14dsp pro card and + my 6dsp pulsar the DSP meter is reporting "wrong" the number "21", but below at the list they appear correctly one by one 14+6.
and offcourse it works perfectly, for 8-9 years now EVERYDAY.

[Shamk]

Nop, i still got PCI limit reach on project load.... i was looking to load Pulsar 15 DSP first ... with a "simple" project STM 4896 + 2 Masterverbpro, + all ADAT IO
I'm out of idea to make all running fine on my MSI P45 Neo3-FR (PCB 1.0) ... i've checked everything inclued :

Brand new STDM cables
Card connector cleaned
PCI card order
No IRQ Sharing, PCI bus latency test from 96 to 128, and even unused USB ports are disbled


Scope card order
Scope, Pulsar II, Pulsar I

Code: Select all

[hw]
[b]intBlkSize=256[/b]
SelectDriver=1
numboards=3

[Host-Config]
Numboards=3
Board1=Host

[board0]
boardid=1 

[board1]
boardid=0

[board2] 
boardid=2


[SC Scope]
Build=v5.1.2709-x64

[Runpep]
InScreen=0
Language=english

[FileBrowser]
All Files=0
STS-Samples=0
LastPath=C:/Program Files/SCOPE PCI/Devices

[AudioFormats]
Wav=Wav

[Installer]
Version=5.0
App=SCOPE PCI
OS=5.0.2201
ProductID=1

[ReferenceResolver]
All files_Paths=C:\Program Files\SCOPE PCI/;
Modules/Devices_Paths=C:\Program Files\SCOPE PCI/Devices/;
Presets_Paths=C:\Program Files\SCOPE PCI/Presets/;
All files_AutoUse=1
Modules/Devices_AutoUse=1
Presets_AutoUse=1

[StaticPath]
Modules=
Modular=C:\Program Files\SCOPE PCI/Modular Modules/
Projects=C:\Program Files\SCOPE PCI/Projects/Examples/
Effects=C:\Program Files\SCOPE PCI/Devices/Effects/
Presets=C:\Program Files\SCOPE PCI/Presets/
HardwareIOs=C:\Program Files\SCOPE PCI/App/Application/IOs/Hardware/
SoftwareIOs=C:\Program Files\SCOPE PCI/App/Application/IOs/Software/
Bitmaps=C:\Program Files\SCOPE PCI/MRC Skins/
Devices=C:\Program Files\SCOPE PCI/Devices/
Samples=C:\Program Files\SCOPE PCI/Samples/

[Path]
Bitmaps=C:\Program Files\SCOPE PCI/MRC Skins/
Projects=C:\Program Files\SCOPE PCI\Projects\Examples

[APPEARANCE]
ToolTips=1
DragWindows=1
StandardCursor=1
GridY=6
GridX=6

[LOAD]
AlignSurfaces=1
LoadMixer=STM 1632.dev
LoadMixerEnabled=1
LoadDefBoard=0

[AUTOCONNECT]
InstrumentToMixer=1
EffectToMixer=1
AudioSrcToMixer=1
DeviceToMidiSrc=2

[SEQPATH]
Path1=

[ASIO]
XTCMode=0
application=C:\Program Files\SCOPE PCI/App/XTCApp/XTC.pro
Pluginwrapper1=C:\Program Files\SCOPE PCI/App/XTCApp/vstsynthplugin.mdl
Pluginwrapper2=C:\Program Files\SCOPE PCI/App/XTCApp/vstplugin.mdl
Pluginwrapper3=C:\Program Files\SCOPE PCI/App/XTCApp/vstplugin.mdl
Pluginwrapper4=C:\Program Files\SCOPE PCI/App/XTCApp/vsthostplugin.mdl

[XTC-Config]
AddHost=1
SelectDriver=1
intBlkSize=256

[Host]
Scoperev=128





[SFP]
Favourites_Minimized=0
Favourites_Size=102
FileBrowser_Minimized=0
FileBrowser_Size=435
ReferenceResolverOptions_SizeY=300
ReferenceResolverOptions_SizeX=332
ReferenceResolverOptions_PosY=106
ReferenceResolverOptions_PosX=315
ReferenceResolverOptions_Show=0
Dsp Load_SizeY=543
Dsp Load_SizeX=194
Top_Minimized=0
Top_Size=634
About_Show=0
About_PosX=254
About_PosY=14
ControlRanger_Show=0
ControlRanger_PosX=289
ControlRanger_PosY=89
ControlRanger_TopLevel=2000
SFPBar_PosX=1265
SFPBar_PosY=620
SFPBar_SizeX=238
SFPBar_SizeY=733
SFPBar_TopLevel=100000
SFPBar_RestoredSizeY=582
Bottom_Size=88
Bottom_Minimized=0
DSPLoad_Load=1
Dsp Load_Show=1
Dsp Load_PosX=1608
Dsp Load_PosY=334
Dsp Load_TopLevel=2000
Registry_Load=0
ModuleRegistry_Show=0
ModuleRegistry_PosX=300
ModuleRegistry_PosY=102
ModuleRegistry_TopLevel=2000
Options_Load=1
Options_Show=1
Options_PosX=296
Options_PosY=96
Options_TopLevel=2000
Resolver_Load=0
ReferenceResolveOptions_Show=0
ReferenceResolveOptions_PosX=302
ReferenceResolveOptions_PosY=104
ReferenceResolveOptions_SizeX=332
ReferenceResolveOptions_SizeY=250
SFPRouting_Show=1
SFPRouting_PosX=253
SFPRouting_PosY=4
SFPRouting_SizeX=1536
SFPRouting_SizeY=1163
SFPRouting_TopLevel=0
FileBrowser_Show=1
FileBrowser_PosX=10
FileBrowser_PosY=559
FileBrowser_SizeX=207
FileBrowser_SizeY=387
FileBrowser_TopLevel=0
Splitter_Size=0
Splitter_Minimized=1
SFPDesktop_PosX=780
SFPDesktop_PosY=216
SFPDesktop_SizeX=1920
SFPDesktop_SizeY=1159
SFPDesktop_Maximize=1
PulsarConfigSurface_Show=1
PulsarConfigSurface_PosX=599
PulsarConfigSurface_PosY=444
PulsarConfigSurface_TopLevel=2000

[RecentFileList]
Entry5=
Entry4=C:/Program Files/SCOPE PCI/Projects/Examples/DefaultTest2.pro
Entry3=C:/Program Files/SCOPE PCI/Projects/Examples/NumerisationSPDIF(MD).pro
Entry2=C:/Program Files/SCOPE PCI/Projects/Examples/Default.pro
Entry1=C:/Program Files/SCOPE PCI/Projects/Examples/DNB-Elegant4.pro
Entry0=C:/Program Files/SCOPE PCI/Projects/Examples/DefaultAllInputs.pro

right now, i'm out of idea ....

[Eanna]

If you dismiss the dialog on project load, does the problem re-appear during your session?
If you load a 'basic' project with a small number of simple devices, does the problem appear?

If your project has a device that demands alot from the PCI bus (something that uses alot of DMA memory addressing, e.g. reverb/chorus) then the action of loading the DSP chips with the software while initialising those devices may push the PCI communication bus into an Over...

[garyb]

PCI overload is as much a function of the motherboard as it is the card. all systems have a limit. you can't just use asio channels and reverbs forever. the question is at what point are you getting PC overflow?

why not do a masterverb test? that will show how well the system is running.

[Shamk]

you can't just use asio channels and reverbs forever.
.

Why ?

the question is at what point are you getting PC overflow?.

The problem come on the project load, it was just a test project with 60% DSP usage ... and it failed ! My system isn't stable, i'm looking for a stable dual core hardware... i 'll may use HP XW6xxxx to reach stability ...

[Eanna]

Why ?

I presume you're messing!
Each ASIO channel and each Delay Line in a reverb device requires a stream of data between PCI Card and motherboard RAM at 24-bit depth and at 48kHz or whatever rate... The PCI Bus is a set size / bandwidth, so you will hit a max at some point. That max is primarily dependent on motherboard.

The problem come on the project load, it was just a test project with 60% DSP usage ...

What devices have you loaded? Like I said, if this only happens when the DSPs are being transferred to the chips and while each ASIO or Delay Line is initialising, then some motherboard PCI Busses may choke up under that load.
My question is if this regularly occurs during your session once you dismiss the dialog? (You may need to briefly switch your Sample Rate in the Sample Rate dialog to trigger a reload of the DSPs).

I see you've resolved IRQ sharing - but is there DMA address sharing too? DMA is the Memory Addressing protocol... I'm not sure if that is your problem, but it's worth investigating, especially since you're familiar with msinfo32.

I've also heard it said that Gen2 Scope PCI cards handle PCI bus better...

And Gary mentioned the Masterverb test.. Here's that thread:
http://forums.planetz.com/viewtopic.php?f=19&t=17078

[Shamk]

That max is primarily dependent on motherboard.

So the masterverb test is there to test it, ok i got it now. I supposed that all data can transit on the mobo as long i have DSP free ... i was so wrong.

My problem is on project load, it's a "fake project" to test all after different message error, but i may start by masterverb test after all ... i'm considering to buy old workstation if it's offering more PCI bandwith !

Thank you Guys !

[Shamk]

I had 2 masterverb before PCI overflow ...
After removing cards, just pulsar 2 all is ok (8 masterverb before DSP Saturation)

Gen 1 cards are really not a good deal ... even with a lot of DSP ...

yes, the pulsar1 definitely throttles down performance. 9 masterverbs indicates a properly working system with a type 1 card mixed with a type2.

Yes definitely

[djmicron]

it depends on what you load on your projects, if you do lot of synthesis, then gen1 cards are ok, but 2 masterverbs is poor result for gen one, it should be 8 at least.

[garyb]

i'd say it should be 5 or 6 at least for a gen 1 card....

[djmicron]

i'd say it should be 5 or 6 at least for a gen 1 card....

maybe on more recent chipset it's more limited, but on my older amd 3400 pc, it reaches 9 with pulsar2 + 2x scopes 15 dsp first gen.

[garyb]

that motherboard just works exceptionally well.

[Shamk]

i'd say it should be 5 or 6 at least for a gen 1 card....

Exactly !

I mount it on a old pentium 4 card (pulsar 1 + scope + scope 4.5), and it's up to 6 before overflow