PlanetZ forums - scopeusers.com

Hello
I'm the owner of 3 lovely sonic core cards (1xscope + 2xpulsar2).
I use most of the time the prodissey and minimax keyboards, but when i tried last time to load the Vectron or Vectron player, it makes the system totally freeze in a second...the device don't load at all, i can just hear the hard disk which access to the data half a second before freezing the system.
The same thing occurs with the kickme2 device ( and maybe others, but i've tried lots of synth like paradox or lightwave, Synthetic, and more and they load and work fine).
I hope i didn't exchange a bad dsp file or thing like that when installing third party devices, because I don't know which file it could be
Do you have an idea for this problem please ? That's not a big issue for me by now but if it can be fixed...and i'd like to know the sound of the Vectron

I got another problem wite stm24/48: After a while, the numbers of the channels disapear and never come back at reload. If I want them back, I must delete and reload the stm. Have you got a solution or a workaround for that thing ?

Thanks for all

that doesn't sound normal. there must be something wrong with the install...

32 or 64bit?
is there a v4 folder on the computer?

Nice to meet you Gary !
Yes, i got the 4.0 installed (not in the same folder as 5.0 of course).
It's a windows Xp 32 bit system.

if you're loading old projects and have a v4 folder, they try to load from the old location, which makes hay.

try renaming the v4 folder.

No, i'm using a new scope project for 5.0
I've seen that i haven't got any masterverb and masterverb pro avalaible in my 5.0 configuration, is it normal ?
In fact, I 've bought a scope card with 5.0 last month, so i installed without formating or deinstalling the 4.0 version I had with my pulsar.

you cant have both 4 and 5 working at the same time

unless you are using a dual boot system

like some who still use sdk4 they have a boot system with scope 4 and sdk4

and a boot system with scope 5 on

the drivers are not compatible

and the software keys will also be a problem as they are different versions for 5 and 4

you need to do a fresh install of version 5 and remove version 4

then it should work fine

Thanks for your answer !
But they are not "working" at the same time, I always launch only the 5.0 version (witrh 5.0 drivers installed), and the 4.0 is never open. I thought that I could go to the 4.0 only by changing the drivers if needed.

I just installed a ghost on a new motherboard (p7p55d with 3 PCI AND i7 860), and The pci bandwith is too low...It can be for me the occasion to verify the cards (the scope one shares irq with the graphic card). I can only launch 7 masterverbs (that I took from the 4.0 install) and the synth polyphony is low too.
Maybe a system reinstall will change the irq...

Another thing I was wondering : in the p7p55d motherboard, I can see that the third pci belowthe card is named pci1 and the first PCI3.
Is it important to put the big scope card on PC1 or can I let it on the 1st one (so which is named PCI3) as it is by now ?

well i can tell you is that i had similar problems no masterverb pro no delays working at all

i did the same as you had 4.5 installed

and 5.1 installed with 5.1 drivers but i was still having problems

i had to remove scope 4.5 totally

and re install a fresh 5.1 to get everything working correctly

Ok, that's clear now
Let's go for a reinstall party !
Thanks !

Its covered here, under 'Other Misc / Hardware Version XX Detected'

http://www.hitfoundry.com/issue_11/tsg_mast.htm

with some info about deleting the old spf startup in registry if needed.

Very nice !
I've never heard this one before:

Issue: Crackles and Pops: Assigning Interrupt processing to specific processors in a multi-processor system: For the record, with Scope PCI cards on XP 32bit-W7 32'n 64 bit, Interrupt-Affinity Filter (IntFiltr) can do all the jobs you need in resolving potential IRQ issues.

Suggestion: Set affinity and mask to a single CPU for your SonicCore stuff and that's it! Use the standard out with your multimedia player. I don't tweak the BIOS, or Windows. Do other tweaks to raise the power of your DAW... if you have to.


Does it mean we can totally avoid interrupt even with an irq shared with graphic card ?

no. not necessarily.

if you need to set affinity, wrong motherboard. is there another slot?
i've seen systems with an irq shared with the graphics card that worked, but it's not what you want.

if you have clicks and popsm first turn these things off in the bios, the names may only be similar and you may not have every setting:
Intel EIST or Enhanced Intel SpeedStep Technology
Intel C State
C1E Support
Overspeed Protection
Hyperthreading
Execute Bit Support
Set Limit CPUID MaxVal to 3 (maybe not so important)
Intel Virtual Tech
Intel VT-d Tech

next go to start\programs\accessories\system tools\system information\hardware resources\conflicts/sharing and tell me all that is sharing an irq with your card(s).

in control\panel\power options click on "change plan settings"and make sure that only the display is allowed to turn off, sleep should be "never". click on "change advanced power settings" and open the "PCI Epress" menu. turn "Link State Power Managemet" off. this will keep your cards from being disabled if you leave the computer unattended for a long period of time.

for best performance, i recommend that you press start and then right click on "Computer". choose "properties". on the left click on "Advanced System Settings". click on the advanced tab and then press the "settings" button in the "performance" section. put a check in the "adjust for best performance"

I've read your recommandations days ago about the bios, graphic card and windows settings, and applied them with no real differences (it adds 1 masterverb in fact and scope is a maybe little more smooth). Idem with cset.ini
Ok, so I won't try the affinity..
I think the Asus P7P55D is the problem...It's a shame that it's a good motherboard, but maybe not for Scope. Anyone got it with Scope here ?
I'm thinking about the Intel DH55HC one, but seems to be hard to find now.
Is there other 1156 motherboards with 3 PCI that have been tried with success (good PCI bandwith) with scope ?
SpaceF said that it could be the ddr3 memory which could be in fault (but good with memtest), maybe should I try to change them...
i'm gonna put some screens of the famous irq (i'm with my home computer now). I've already deactivated the usb port that was shared with scope.
Thanks again for your help !

socket 1156 motherboards have been pretty good in my experience. the Asus should work. the Intel has worked in the past for me.

ok, before thinking about changing the motherboard, i should first reinstall everything.
If the pci bandwith stay low, i'll try the memory...I got gskill ddr3 1600, p55 is 1333, but it can go to 1600 on the motherboard. I've tried twice without more success).
I must say that Scope is very stable till this point, but I can't load much more 60% of dsp without pci bandwith problems.
I've seen that adding polyphony the synth slowly (1 voice each time) increase dsp charge smoothly.

% of dsp and pci bandwidth may or may not be related quantities.

it depends on exactly what devices are loaded.

Even when loading synth and adding voices ? I thought that polyphony was linked to PCI bandwith.

Polyphony is linked to DSP usage because synth polyphony takes place on the DSP.

The things that rely on PCI bandwidth are audio to/from host DAW and a few specially coded plugins such as VDAT, Masterverb/reverbs and some 3rd party filtering etc (indicated as ASYNC on the DSP meter).

even ProTools won't always let you load 100%.

there are a number of factors. i could tell you more about what went wrong if i saw the error message.

if the message allows a "global optimization" then try that, a few times if necessary. the better synths can be pretty heavy in dsp usage. for exable, one voice on the minimax can eat about 2 dsps. if there are other things loaded and you enable several voices, the dsp chips that are loaded may be on opposite ends of the card and physically very far from eachother. this can create timing errors that make it impossible to generate a sound. a "global optimization" tries to shuffle the dsp assignments for all the devices in order to make everything fit better.

not all errors indicate that something is wrong, as in broken or just won't work. some Scope errors can be worked around through a reloading of the dsps.

remember, there are many different resources involved. when any of them max out, that's the end, even if there is still dsp or pci space.