Scope Freezes after I add a device.

Leper · Post by **Leper** » Mon Jun 04, 2007 11:59 pm

Hello,

I've been having a very annoying problem with Scope for a while now.. maybe someone could give me some advice about this?

It usually happens when I add Pro-12 or Minimax device to my project.. about 50% of the time Scope freezes immediately after adding the device. I can play the synth with my MIDI keyboard, but scope software is frozen and not responsive.
SFP.exe takes up 99% CPU in task manager and if i try to end the process, it restarts my computer!

I have 2 cards, Pulsar 2 and Powerpulsar (Scope Project and Pro) linked together in my computer.
If anyone can help me with this I'd very much appreciate it. This makes me afraid to ever use the good synths in my music for fear of freezing. And when I am in creative moments and need a specific sound, the freezing screws everything up

-freakmod

Leper · Post by **Leper** » Tue Jun 05, 2007 12:29 am

Also my Scope card is sharing irq 17 with my network adapter.. I can't seem to be able to change its irq though.. do I have to turn ACPI off?

astroman · Post by **astroman** » Tue Jun 05, 2007 12:33 am

I dunno the reason, but it seems to be related to the loading process of the device.
Never had it with the Pro12, but the Mini frequently caused either a DSP overload or a PCI bandwidth error when added to a project (it's been a while so I don't remember exactly), but in any case the message was unreasonable (lots of resources still available).

It might help to make the Mini a part of the project and save with 0 (zero) voices allocated - when you need it, just activate the # of voices required.

cheers, tom

bill3107 · Post by **bill3107** » Tue Jun 05, 2007 1:02 am

do you have a decent computer, i mean what kind of computer do you have ? even with my "old" Pc (asus p4G8X, P4) i could load 3 instances of minimax (21 dsp) without any pci overflow and so forth... Have you tried to de-activate what is unnecessary in the bios (especially if it shares irq with scope...) ?

Post by **garyb** » Tue Jun 05, 2007 4:21 am

do you need the network card while using scope? if not, you can try temporarily disabling the network card in the device manager.

possibly the order things are loaded is the problem. a big device like the minimax or pro12, which uses several dsps, isn't going to want to span two cards because of timing issues. perhaps if you load another device, then the mini or pro12 and then remove the extra device, the load issue will disappear. also, perhaps the install is corrupt.

Post by **garyb** » Tue Jun 05, 2007 4:21 am

Mr Arkadin · Post by **Mr Arkadin** » Tue Jun 05, 2007 7:28 am

i had this problem with Pro-12 but not Minimax. i ended up having a default project with Pro-12 already loaded - and then if i didn't need it removing it. This way the DSP was already allocated on loading.

astroman · Post by **astroman** » Tue Jun 05, 2007 8:02 am

right the opposite of my case, it was only the Mini and never the Pro...

no network and nothing but Scope running, the infamous TUSL - but of course under Win98 the 'consequences' were much more forgiving than under that 'sophisticated' memory-management-user-access-rights-crap called...
(oops, pardon the rant...)
btw I'm 99% certain that it's in the device, because it's fairly reproducable and can be avoided in the way Mr. Arkardin described

cheers, Tom

Leper · Post by **Leper** » Tue Jun 05, 2007 11:40 am

Hey,

Thanks for all your replies...!
Yes, I have a fairly good PC.. AMD Athlon 64 3200+.. 2 gb ram.. 1 TB hdd space.. good graphics card etc.

Well right after I posted last night I tried to change my pc from Uniprocessor PC to Standard PC in device manager... heh.. that caused me a lot of stress and staying awake til 3:30 am because my keyboard no longer functioned in windows etc.. !

I finally got it fixed but I still cannot assign IRQ's, they are greyed out when I try to change them in Device Manager properties.. Hrm.

bassdude · Post by **bassdude** » Tue Jun 05, 2007 2:12 pm

If you are going to try "Standard PC" then you really should do a fresh install.
Then you allocate IRQ's in the bios and turn plug and play OS off (so you can't assign in Device manager).

However, you could also setup hardware profiles, disabling the NIC when using scope instead of going the Standard PC route (especially since you only seem to have a conflict with the NIC).

Also, more important than CPU and all that is what motherboard are you using?

Leper · Post by **Leper** » Tue Jun 05, 2007 2:55 pm

Hey,

I reverted my install to ACPI Uniprocessor PC. Standard PC seems to be quirky. I'll try the other alternatives first!

Plug & Play OS is OFF in my BIOS.

I'll try disabling the NIC when using scope and see what happens. Hopefully that will solve things, although it kind of sucks not to have internet when making music! Wish there was a way to have my network card on while using scope.

The motherboard I have is a Asus K8V-Deluxe.. I believe it has a VIA K8T800 chipset.. does that help with anything?