Synths crackling after installing new card...

[RP_001]

Hi guys,

I recently replaced one of my pulsar II cards with a scope pro card, so my current setup consists of 2x Scope Pro and one Pulsar II, all with AES/EBU.

I had a very stable system for the last 8 months, but after installing my new Scope card, after a while, the synths included in my project start crackling continuously out of the blue.... This happens especially with Prodyssey, Minimax and Protone. Sometimes after half an hour, and sometimes after a couple of minutes.

I did setup a new project with my analog/spdif modules and all synths, so i dont think it has something to do with "older" projects not being "compatible" anymore...

Things i've tried to solve the problem (as suggested in posts from last couple of weeks);

* New Windows install/ new Scope install (and copy my Scope backup folder on top of that)
* Put the cards in other PCI slots
* Edit the Cset.ini file, and changing the order of the cards. ( 1= scope 2= scope 3= pulsar 2)
* Cleaning the STDM connecters/cards with basic contact spray, which reduced the amount
of "communications errors". (I ordered Deoxit 5, so I will have to test if that'll make any
difference)
* Make sure that cards dont share IRQ with other components.
* Detach the AES/EBU IO from the new Scope card
* Uncheck " Reset board if idle"
* Edit the Bios ( put off all unused USB devices/ Onboard sound, etc)

So, basically, the only thing that is different from my old setup is the Pulsar II replaced by the Scope board, and the use of my PCM91 via digital IO's.

Seems like something is interfering, but i cant find the problem.....

I hope someone has some other suggestions than the ones above...

Greetz,

Rene

[RP_001]

@ stardust

All cards are Type II. The Scope Pro that i installed lately is from 2006.

At first i used all 5 STDM cables, and i found out that reducing the amount to 3 gave me better performance.

[RP_001]

Im not using firewire.

Motherboard im using is Asus P4C deluxe, but that didnt cause any problems so far..

Maybe some of my external gear (Minimax ASB/ Virus C/ Lexicon PCM91) is causing interference when turned on.

Right now im trying to put on every device one by one; First scope, Minimax ASB , Virus C, PCM91, and see if there lies the problem...

[fidox]

hey !

i have the same motherboard, asus P4C800 deluxe and i never figured out what was wrong with 3 cards connected, i replace that mobo with Abit (1x lunaII + 2xPulsar XTC), the same chipset and everything works fine till then,
i still use asus mobo,. but now i have one Luna II inside, so it works fine.

you have Standard PC installed or ?


hope you'll figure out , what's wrong,


matej

[RP_001]

@fidox

What do you mean by standard PC??

[Shroomz~>]

Sounds like it might be a problem in your digital signal paths - a sync issue specifically. I'd try starting with everything except the digital I/O connections (IE unplug all digital cables from the box), then go onward from there connecting them back up step by step.

[fidox]

oh, well, i think it has nothing to do with your problem, but
you have windows installed in Standard PC mode or ACPI mode ?
or you have VIsta ? which i'm not familiar anyway ,

but like i said, it has probably nothing to do with your prob.

hope goes well,

matej

[RP_001]

Hi,

I guess i installed it Standard PC, although i can rembember i used ACPI before. I think that was with my old motherboard. What's the difference between these?? Any difference in performance?

@Shroomz

That was also what came to my mind first. But i thought just leaving the PCM91 off should do the trick. I use it as Aux FX. From the mixer's Aux 1 to the SPDIF input, and from SPDIF out to the Aux1 returns. This is the first time I use digital signal, so are there any things that i should take care of ??


Thanks for your replies!!

[garyb]

Hi,

I guess i installed it Standard PC, although i can rembember i used ACPI before. I think that was with my old motherboard. What's the difference between these?? Any difference in performance?

@Shroomz

That was also what came to my mind first. But i thought just leaving the PCM91 off should do the trick. I use it as Aux FX. From the mixer's Aux 1 to the SPDIF input, and from SPDIF out to the Aux1 returns. This is the first time I use digital signal, so are there any things that i should take care of ??


Thanks for your replies!!

standard pc allows you to set irqs manually. this shouldn't be the problem. have you actually checked for irq sharing? if not please do so and tell what, if anything is sharing an irq with any or all Scope cards...

with digital, there can be only ONE clock, therefore only ONE clock master. if you use the pcm91's digital i/o you must either set the pcm91 to slave OR Scope must be set to sp/dif slave. both machines set to master will create clicks and pops, as the samples will not be timed correctly between the two systems. both machines set to slave will make no sound, as there will be no clock to time sample playback.

[Shroomz~>]

Gary's pretty much explained it for you. The only thing I'd add is that if you don't have success with one as master & the other as slave, try it the other way round.

[RP_001]

Hi,

My system is much more stable now. I switched the digital cable from my pulsar II to my scope card's digital in, and changed modules in my project. Seems like there is a weak communication to the other boards when it is connected to my pulsar. All boards have seperate IRQ's, and do not share IRQ with other devices.

There were also clicks en pops caused by loading a prodyssey or protone device, but it seems that was created by the midi clock sending messages out to other devices. Changing to external clock on the synth or switching from master to slave mostly did the job without the system crashing..

I will clean the cards with some deoxit cleaner when i receive it. Next days will tell if it gets any better , but at least i am able to make music on a acceptable level till then

Thanks again

[RP_001]

Hi,

Im still having major problems. After installing my 2nd scope a 5 weeks ago problems started, but with some of the tricks and configurations written above, i had quite a stable system after a couple of weeks. Especially cleaning the IO plates with Deoxit D5 reduced the amount of communication errors a lot. The only problem that was left, was still the crackling of synths, but changing master/slave did solve the problem most of the time, this time without the system crashing. Anyhow, i was able to make music on an acceptable level again.

This week my 3rd scope card arrived, and some major problems occured again... Most annoying thing is the incredible amount of feedback occuring out of nothing. I do not dare to put my amplifier up, because it will definately screw my ears.. Also the "communication errors with other board" starts again..

I made a project without the SPDIF (PCM91) modules in it, which i suspect to cause the glitching/crackling. Main problem is the feedback though.. I really cant work like this... I know it can be solved somehow....

Very, very strange; I did have quite a stable system with 3 cards connected (1x scope, 2x pulsarII) for months, but when connecting 3x scope cards major problems occur...

I will do a comple new OS/scope install again, and see if it gets any better.

System;

Mobo; Asus P4C800 deluxe
Processor; Pentium 4
160 GB Maxtor HD (sata)
1.5 G of kingston DDR Ram

I hope someone has some other ideas to solve my problem....

[dbmac]

Hi RP
I used a P4C800e for years with3 scope boards, it will work.

Some more details about your setup would help. What video card, anything else on the PCI bus, how many stdm cables, what outboard midi device are connected to scope midi in...?

Also, make sure multi-threading is disabled in your Asus bios.

The feedback problem is another issue, not related to scope crackling.

/dave

[RP_001]

@DbMac

videocard is a cheapo Gforce Mx400...

Nothing else is one the pci busses, except for the 3 scopes.
1st scope in 1st PCI (under the videocard)
2nd scope in 2nd PCI
3rd scope in 4th PCI

Changed it couple of minutes ago to the 3rd/4th/5th PCI bus, but now my 1st scope is IRQ sharing with USB2 controller. Also the feedback is occuring again.

I use a MIDIman 4x4 for my midi devices. None of the scope midi ports is used (yet)

Hyperthreading is off in Bios.

Is it possible that it's project related? That even after deleting suspicious modules/devices, some settings are saved within the project??

I will change boards again, and build my new project from scratch.

greetz

[dawman]

The USB MIDISport can still operate on a disabled port.
Many times members are unaware that USB can still power their MIDI box's and controllers w/ the USB ports being disabled in the Device Manager.
This could be helpful when doing the IRQ sharing assignments.

[RP_001]

Good thing to know!

I have disabled the USB2 controller before, and could still use the Midiman 4x4, although sometimes i had to plug in and out the usb cable to work properly again.

Right now, i switched boards again, so all scope cards have seperate IRQ, with nothing shared.

I also started a new project, but after a few minutes the screaming feedback occurs again

I will do a fresh OS/Scope install now, but im afraid it's hardware related. I think i checked all the available options so far....

Is an extra cooler for the scope boards recommended?? The boards seem to get really warm, although i have an open case.

My quest will go on.................

[dawman]

I never had a need for those, even though the first DAW had a PCI Dual Fan Card.

It's so hard to stop spending money sometimes, but once a Scope DAW gets set up w/o problems. It will run forever, outlasting the HDD's, and even a QWERTY PS/2.