PlanetZ forums - scopeusers.com

I'm not sure 100% that this is the fix since I've done two things: 1. I've changed PCI latency to 128 and 2. I've disconnected the MIDI Destination module (MIDI IN was connected to MIDI OUT in the project). Now MIDI source is connected only to various synths.
So now my dual Xeon with hyperthreading enabled (4 CPUs, 2 virtual) and in ACPI Multicpu mode, works flawlessly with MIDI clock and active sensing on the MIDI bus.
Can anyone confirm this?

Hi BingoTheClowno,

Creamware's midi implementation is the worst I've encountered on a audio card. The most simple things completely f@@ked up, what were they thinking off?

I tried your solution and it doesnt work here.... I just use my midiman and lynx2 (perfect every time). I know many who use CW midi but Im no fan of it. Ive spent hours trying when I first got into creamware with several keyboards, all the same result --- stuck notes, random keys etc.

thanx
CFG

Well that's good to know, I'll have to think hard what else I have done then.
I used to get BSODs whenever I enabled the internal clock sync on my synth. For some reason now it works flawlessly. I wanted to check if the last changes have had anything do with that.

Hi,

I think Sonicore should take note of this whenever they get round to releasing an updated versions of the Scope cards (fingers crossed, soon). This little problem does not hinder music production in anyway.

Creamware is solid apart from this one thing... it could be just my setup also..
Cant wait until new hardware is released!!

CGF

Yeah, and mine doesn't even do a half decent Cappucino !, It's Bloody outrageous !

Why Cppn , of course