PlanetZ forums - scopeusers.com

On 2006-05-10 04:51, gustav wrote:

IRQ 23 Creamware Pulsar2
IRQ 23 Intel(R) 82801GB Serial ATA Storage Controllers - 27C0

I don't think sharing an irq with the SATA controller is a good idea for the Scope cards.


/dave

perhaps but what are the alternatifs ?

in the configuration before it was the pata controller who was shared and I have the impression that the result was worse. (I even tested a only sata drives configuration)

perhaps I shouild try without sata drives ?
I will try to find 2 pata hard disks ...

I had to switch from an Antec P180 case to a Chenbro SR209 because of the space limitations of the Antec. I'm very pleased with the Chenbro, very spacious.

I'm downloading the manual for your board (very slowly) - I'll get back regarding the PCI slot/irq assignment.

/dave

thanks!

some changes :
ITE8211F controller disabled
2 satadrives

its allways making hang windows - this time after 7 minutes on my initial sts-project - this is the best score I ever got on this project with this PC
and I have to renew the test because I've got no windows midi in cubase, only emulated directx - I don't understand why but I will find and test

From looking at the Asus P5WD2 Premium manual, it looks like PCI slot 1 is the best - if you can disable firewire & lan in bios.
Slot 2 shares with IDE controller, slot 3 shares with SATA controller. I would prefer to use sata drives, so I'd use slot 2 and disable IDE on that board.

This may not be necessary, but I've always had success running 3 Scope cards by NEVER sharing IRQ with HD controllers. Maybe your OS drive can be on IDE without problems.
Someone familiar with this board could advise you. If the PCIe (universal PCI-E) slot could accept a PCI device, it would be an ideal slot.

Good luck,

/dave

gustav,

I have a similar set up like yours. Same motherboard for sure. I used to have the same problems. They solved (no hangs during the last month) by removing completely the "sequencer midi dest 1" module from the routing window. Active sensing, dual core, asus, irq sharing etc. wasn't the case. I have removed seq midi dest and somehow all crashes stopped. I am not using this module anyway and I can always buy a cheap usb midi device if necessary!

ps: I am using XTC mode and sx3. The standard mode was acting weird at least before removing the seq midi dest. I haven't try it since...

<font size=-1>[ This Message was edited by: andredai on 2006-05-10 12:25 ]</font>

<font size=-1>[ This Message was edited by: andredai on 2006-05-10 12:27 ]</font>

the usb midi suggestion might be the thing. i have built several machines with the exact same motherboard and the shared irq with the sata controller. all have worked well. there was one machine a few years ago that just always froze using cubase(intel d865perl). we used a cheap usb midi interface(midex3) and solved the problem. maybe there is a construction flaw in the motherboard, that shows itself through pci midi info, i don't really know....

oh thanks ! - I did read something like this on an other post - I will try asap

I did a new clean install - allways with the srb in PCI1-slot and pulsar2 in PCI3-slot
I followed your advice and removed midi seq dest 1 and 2 from the routing window.

The test lasted only some secondes - this is totally frustrating - so no solution in sight !?

What type of ram do you have?
she could be this.

4 GO Corsair Value Select

gustav,

Sorry, I missed your question to me regarding the disabled devices in my BIOS. Working back from your list, I disabled SMBUS (this is mainboard/system-monitoring circuitry that is used by Remote Admins), the USB2 Controller (garyb thought that was okay though), the PRO/1000 Network Conection, some of the USB ports, Serial and Parallel Ports, On-board Sound. I may have the ATA/ATAPI disconnected also, but I do have a DVD/CD attached, so not sure about that one.

I have not had a "Lost communication..." error since I loosened the screws, re-seated the boards, and re-seated the STDM cable. I think tightening the screws was lifting one end of the board/s slightly out of the PCI socket, although it was a very slight amount, if this is what was happening.

I still get freezes when I use an STS sampler. This became *much* less frequent when I set Graphics Hardware Acceleration to 'none.' I thought this had solved the problem with the STS entirely, but I did get a freeze after an hour of use last night. My system works for several hours without a hitch (although much of this time is just playback, not editing/recording) if I don't have the STS in the project.

Regarding midi loops, my controller enters SX3 via USB, then passes into Scope. I have removed the Seq Dest module. There is not active-sensing signal getting to Scope based on the Midi Monitors. There is no return path to SX3.

I haven't tried 'SPD' for the memory, I am using the settings recommend for the Corsair memory that I have installed.

I haven't resorted to (another) fresh re-install yet...

Cory

great - I will check this soon
thanks !

I checked the corsair memory - its ok

Now I'm waiting for my pulsarboard coming back from germany (adat port problem)
then I will have to decide what I will do ...
(actually I have noi idea)

My pulsar card is back since some days - windows is hanging after sometimes only seconds sometimes after hours. I'm giving up. I will look for another mb.

but there are some things I have to be sure :

Shroomz said that cubase does not like loops. Its true for my system but I'm not ready to admit this in general : Are there cubase sx users under windows xp who's system is not hanging ?

And is there any cubase sx user on winXP who can use without problems the sts ? (sts5000 if possible) ?

If there are some users of this kind I can keep hope and try to get a stable system with another mb.

Argghhh!

yes on both counts.

maybe you can lend for Example a sonar or other different sequencer from a friend;
to check if cubase-scope combination is the problem; or you take the trialversion to check
i expirienced a midiproblem between steinberg and CW too to ends in a no more goes on PC; having very different setup;
this is the same on cubase sx 1.0 to x.x and nuendo 1.0 to x.x;
im no expert in steinberg so i never found out how to go;
sonar doesnt make this is ok. so far;
it goes better to not connect any keyboard to cubase; to spread mididata to 2 sequ.sources; to raster the notes in cubase/nuendo (so the note on comes exact on 1.1 bar and has a exact lenght of 1/4 1/8 . . .;
but as many guys on this forum work with cubase and no problem in midi its maybe a setting in cubase i lost;
if you take a trialversion it cost you nothing only time;
good luck

thanks tgstgs but I will not continue testing on this system - too much time lost.
Its time to search a new motherboard I think.

Thanks Garyb!

so what are the motherboards (if possible with 3 PCI slots) that are "sure values" ?

p4p800 ? i'm not sure if I want to take an Asus again ...

DP965LT : how many cards hold - irq issues ?

supermicro Core2Duo PDSBE : any experience ?

others ?