Scope Project and Core Duo

Eduard · Post by **Eduard** » Fri May 11, 2007 11:11 pm

I've changed my PC for the one with Core 2 Duo processor and this problem appeared. Computer stops completely from time to time - nothing but reset works. The problem appears only when Creamware Scope is instaled. When using onboard sound with Scope disconnected no such problems happen. Maybe some new drivers needed? Can anybody give any advices?
Thanks.
Eduard

Eduard · Post by **Eduard** » Sat May 12, 2007 5:52 am

Yes I did. I used all combinations (onboard on, onboard off, even tried not to install onboard drivers), tried to reinstal system but got no result.

Post by **garyb** » Sat May 12, 2007 9:43 am

!. go to start/programs/accessories/system tools/stytem information/harware resources/conflicts-sharing and tell me if the scope card is on the list, and, if it is, what is it sharing with?

2. in the scope routing window, go to midi and select the midi monitor. open the surface and connect the module to your pulsar midi a source. are there an endless stream of active sensing and/or midi clock messages?

Eduard · Post by **Eduard** » Sat May 12, 2007 11:48 am

Hi Garyb,
Thanks for being in contact.
There is Creamware Pulsar 2 in conflicts/sharing (record IRQ 21),
it stands with Intel(R) ICH8 Family USB Universal Host Controller – 2835.
On Scope MIDI monitor there are records Activ SNS, and while pressing the keyboards Ch.1 Note Off etc. records appear.

Eduard · Post by **Eduard** » Sat May 12, 2007 12:48 pm

What this active sensing mean? I'm not so strong computerman so hope you'll excuse me.

Post by **garyb** » Sat May 12, 2007 2:47 pm

you have two problems.

here are your solutions.

1. go to start/control panel/system/hardware/device manager. open the usb section and find the controller named "2835" and disable it. close and reopen system information and check to see that the scope card is off of the list.

2. in the routing window, go to the midi menu and get a midi filter. connect it between the pulsar midi a source and the sequencer midi dest. use a midi monitor to be sure you are filtering active sensing.

this should fix your problems.

Eduard · Post by **Eduard** » Sun May 13, 2007 9:25 am

HI GUYS,

WANT TO SAY A GREAT THANKS TO GARYB AND STARDUST FOR HELP AND CONSIDERATION! I'VE DONE THOSE TWO THINGS AND NOW IT'S ALMOST 10 HOURS WITHOUT ANY FREEZES!

THANK YOU VERY MUCH.

SINCERELY

EDUARD

Post by **garyb** » Sun May 13, 2007 11:08 am

Post by **hubird** » Mon May 14, 2007 2:15 pm

osgary

Post by **hubird** » Tue May 15, 2007 1:21 pm

Post by **hubird** » Wed May 16, 2007 8:05 pm

Throttler · Post by **Throttler** » Thu May 17, 2007 12:08 am

garyb wrote:1. go to start/control panel/system/hardware/device manager. open the usb section and find the controller named "2835" and disable it. close and reopen system information and check to see that the scope card is off of the list.

What do you mean by that. It didn't go away in my setup. Did I do something wrong?

Post by **garyb** » Thu May 17, 2007 12:28 am

on his computer, that was the controller that was sharing an irq with the scope card. what is your card sharing with?

Throttler · Post by **Throttler** » Thu May 17, 2007 10:09 pm

I'm not at home right now. If I assign through the M/B the specific IRQ to the PCI slot, is that ok ?

Post by **garyb** » Thu May 17, 2007 10:11 pm

sure, but it doesn't matter if you do that if the os is installed in acpi mode.

check system information and see what it says.