PlanetZ forums - scopeusers.com

Hi.

MasterVerb test with aspect of PCI-latency. Pink noise mono input on all MasterVerbs. Wet output levels (dry mute) in meterbridge (running check).

First System:
Board: Gigabyte G41M-Combo (Northbridge: Intel G41 rev. A3, Southbridge: Intel 82801GB (ICH7/R) rev. A1)
CPU: Intel Core 2 Duo E6750 (Conroe, 2.66 GHz, 4 MB L2)
RAM: PC3-10600 Dual Channel (CL-7-7-7-21)
Scope: 1 x Scope (15 DSP), 1 x PowerSampler (3 DSP)
Video Card: ATI HD 5570 (DDR3, 1024 MB)
Result: 13 MasterVerbs (14th brings PCI bandwith error)

Second system:
Board: Gigabyte P35-DS4 (Northbridge: Intel P35/G33/G31 rev. A2, Southbridge: Intel 82801IR (ICH9R) rev. 02)
CPU: Intel Core 2 Duo E8400 (Wolfdale, 3.0 GHz, 6 MB L2)
RAM: PC2-6400 Dual Channel (CL-5-4-4-15)
Scope: 2 x Pulsar2 (12 DSP)
Video Card: nVIDIA Geforce 7600 GS (256 MB)
Result: 13 MasterVerbs (14th brings PCI bandwith error)

Obviously Scope will increase PCI-latency to extraordinary levels. Are 2112 µs critically?

I suppose coherence between PCI-throughput (of the whole Scope system) and number of used PCI-slots too?
1 x Scope (alone, 15 DSP): 9 MasterVerbs

Switched card order (18 DSP):
1 x PowerSampler (host), 1 x Scope (slave): 9 MasterVerbs

Cheers.

ASUS Z87C with Intel i7 4790 (not overclocked) + 16GB RAM + 2 x SSD. Scope running at 48 KHz

1) On Scope PCI ( 1 x Pulsar 2 + 2 x Luna 2 ) - 10 Masterverbs
2) On XITE-1D - 10 Masterverbs.

Not as good a Masterverb result as my older ASUS P5K-E but overall the new system spanks it.

NOTE: On both mobos, Masterverbs reach PCI capacity on XITE-1D at the same count as on the PCI cards.

that should be plenty.

Ok, I'm definitely not lucky...
I bought an MSI Z87-G43 Motherboard with, obviously, a Z87 chispest on board.
I read here that Asus with Z87 features at least 9 Materverb, that would be enough for me.
But with mine I reach only 3-4 Masterverb.

Intel i7
12 GB Ram Kingston
MSI Z87-G43 with built in video card
Windows 7 Ultimate
Scope 15 DSP + Luna 3 DSP
2x PCIe UADII duo
switched off all devices not needed like: parallel, serial, built in audio, etc.

I can use 2-3 poly synth or 2-3 effects, after that, I receive "DSP error"

Any advice for reach a better performance?
Could IRQ sharing creates problems performance PCI?

maybe irq sharing might affect PCI performance, but generally not.
is that a first generation 15dsp card?

I really dunno, how I can discover this?

if you have a v5.1 key for the Luna, you can remove the 15dsp card and recheck.
that PCI performance looks normal for an original Scope card or a Pulsar1.

if you don't have a v5.1 key for the Luna, write to support with the Luna's serial number and request a temporary keyfile. then you can test...

The card is at 98% a 14 DSP (currently I should remove it to count the DSPs) but I used it in the past with another system (socked 1156) that worked well.
So it seems strange, now, with the same Z87 chipset as others to reach only an half of Masterverbs...
I have to check the IRQs

Any particular setting into BIOS to pay attention for PCI bandwidth?

Thanks for your help, mate

there shouldn't be anything extraordinary to do.
you can try raising the PCI latency timer to 96 or 128, if that's available. i wouldn't expect it to help much.
it should work correctly if you do these basic things:
http://forums.planetz.com/viewtopic.php?f=3&t=31345

it's possible that there may be a bios update that will help things. it's also possible that that particular model motherboard has issues(but i wouldn't expect it).

I changed the PCI latency but no changes.
The IRQs are a little messy:



I really don't understand why the system places 3 boards in the IRQ16 when the IRQ18 is totally free!!!
I found no way to change manually the IRQ of Scope... I really miss some old BIOS features that allowed to change IRQ.
How can I change (if possible) Scope IRQ from 16 to 18?
Any tips?

you can't.
the new motherboards REQUIRE acpi. there's no way to set them manually.

the reason that they are set that way, is because of the architecture of the motherboard.

no way to change PCI slot because of the Scope length...
Anyway thanks a lot Garyb, very competent advices

Damn ! It's too bad !

Maybe, you could get something like this :
http://www.ldlc.com/fiche/PB00113548.html

I think there is the same for old pci, make a little research ! You should be able to change your card slot.

Garyb, just a doubt/question: is the XTC mode officially marked as "not supported" in x64 or "not working" because of I had yesterday trouble (PCI etc.) inserting only 2 Softclip stereo in 2 tracks! That's not normal!
Thanks in advance for a reply

no xtc mode is possible in 64bit, at this time.

I have to admit that my MB seems to be not suitable for Scope despite his chipset:



only one Softclip in a empty track, 48khz, 32 bit, 7ms ASIO delay, even if I changed the slot and reached a single dedicated IRQ, with not conflicts



I've lost any hope... any last idea/try before start to search for an Asus?

Thanks in advance.

Sorry I read only after my last post that XTC mode in x64 is not possible, anyway I have only 3/4 Masterverb instances with a Scope Pro 14DSP (I checked) in normal Scope mode.
And I think this result is too bad compared to the 9/10 instances of i.e. Asus MB with the same chipset.

This is my first bad experience with Scope and MB in 15 years... x64, more powerful CUPs, more ram, but very PCI performance downgrade (and NO XTC mode available)

Thinkin to go back to x86 OS...

why not use 32bit?
you can still use extra ram for your kontact samples with jbridge...
http://jstuff.wordpress.com/jbridge/

garyb wrote:why not use 32bit?
you can still use extra ram for your kontact samples with jbridge...
http://jstuff.wordpress.com/jbridge/

You're intending to install a 32 bit version of Cubase in the 64 bit OS?
Is in this way XTC allowed?

(anyway I have still the problem that with few plugins give me the PCI advice)

no. 32bit windows.