PlanetZ forums - scopeusers.com

garyb wrote:the main thing i've seen make the computer freeze is either a shared irq(eliminated right?) and midi active sensing. you're using a midi controller with cubase and checked for active sensing and midi clock, right?

Yeah, the Luna board has an IRQ all to itself now.

I'm using a Roland D5 going into the MIDI in port of my Luna board. Nothing is connected to the MIDI out port. This was the setup I had for a long time with my previous machine, and I didn't have any freezes on that system, but maybe the new one is more vulnerable.

Will investigate when I get home from work.

Maybe its not the Luna at all? My laptop has arrived now as well, so I can turn off the LAN port on my mobo, and finally have my machine 100% deciated to music.

the roland very likely does output active sensing. connect a midi monitor to the luna midi source. and open it. do you see a steady stream of active sensing messages? eventually, the will overflow midi buffers. this has been a problem since xp. insert a midi filter(both the filter and monitor are in the routing window under the "midi" heading) in between the luna midi source and the sequencer midi dest. if the filter is set and connected properly, the freezing should cease.

garyb wrote:the roland very likely does output active sensing. connect a midi monitor to the luna midi source. and open it. do you see a steady stream of active sensing messages? eventually, the will overflow midi buffers. this has been a problem since xp. insert a midi filter(both the filter and monitor are in the routing window under the "midi" heading) in between the luna midi source and the sequencer midi dest. if the filter is set and connected properly, the freezing should cease.

Ok, yeah the Roland does have Active sensing. I've put a MIDI Filter module between the Luna midi source and the Sequenver Midi dest. Default settings for it seem to allow through the things I want, and block the Active sensing.

Am optimistic that this is it:

garyb, thanks again.

Should the MIDI filter work in XTC mode? I connect it up in my XTCProject.pro, but if I do this, I don't seem to get any MIDI at all into my DAW.

maybe not. you may have to either turn active sensing off in the controller or filter before going into the computer if you want to use xtc mode...a cheap interface like the midex3 might be an xtc mode solution as well.

garyb wrote:maybe not. you may have to either turn active sensing off in the controller or filter before going into the computer if you want to use xtc mode...a cheap interface like the midex3 might be an xtc mode solution as well.

I have a Midisport 4x4 USB sitting around here. I'd always thought that it would be more efficient to use the MIDI ports on the Luna2. Is the problem with the MIDI handling in the CW drivers? If so, a switch to the USB MIDI interface should fix things, (if this is the problem).

Regardless, I shall switch to using the Midisport, and see if the freezes go away.

active sensing causes midi buffer overuns. the midisport likely won't have a problem. turn off active sensing and the creamware port won't have any problems. either way, i suspect you're up and working now, no?

garyb wrote:active sensing causes midi buffer overuns. the midisport likely won't have a problem. turn off active sensing and the creamware port won't have any problems. either way, i suspect you're up and working now, no?

Up and working as in "at work" . Will hook the MIDIsport up tonight when I get home. Can't turn active sensing off on the D5.

My perfectly stable DAW is just around the corner, I'm sure

Hi guys,

i`ve left the post after the midi filter seemed to fix my problem. it was ok for like a month but now i get repeated freezes again. my card doesn`t share an irq, midi filter is there, what else could be the problem? shouldn`t i go the "standard pc" rout? or install the 3.1b driver?

The 3.1b driver is located at: http://www.shaynesworld.com/3.1b_drivers.zip

Standard PC doesn't work with multiprocessing, if you happen to have that, so you're forced to use ACPI.

Hope that helps.

Shayne

There is also MPS multiprocessor mode..
anyone have any idea what the ups/downs of using that mode are?

As for MPS, it doesn't see the second processor (with P4 Hyperthreading), and irq numbers get high, some devices show even 48 or 116.

I tried Scope and Pulsar 2 cards in two PCs - one i875PBZ / Pentium 4 2.6 HT Northwood based, the other non intel make 865 based board with Pentium 4 2.8 Prescott. Both freeze after some use. Tried everything, even leaving just pulsar and video card installed - still have lockups. All these tests were in ACPI Multiprocessor PC mode, as choosing any other mode disables HT and PC is less responsive - it's not a good option. Waiting for Scope 5....

what i did to fix bluescreens and lockups on intel 875PBZ mobo with HT CPU (winxp sp2):

for version 4
1) install 3.1b driver
2) modify SFP.exe with imagecfg.exe tool to run on one virtual cpu only;

for version 5
no need to change the driver (any older driver wouldn't work anyway)
1) modify the main exe with imagecfg

no need to disable HT or force non-aspi kernel

imagecfg can be found here: http://www.thief-thecircle.com/guides/h ... agecfg.zip

WOW!
i'm gonna try this and see if it helps the xtc mode problem!

thanks!