PlanetZ forums - scopeusers.com

that shouldn't be needed with the core2 cpu.....

The crackles only disappear if I switch Cubase priority to the highest position and SFP.exe to normal.

The changing of the SFP.exe to only a single CPU did not change the crackles.

Gary:
I have three pulsar cards.
Pulsar 1 (PCI-0) + Pulsar SFP(PCI-1) + LUNA II (PCI-3)
The SFP Software sees the Luna always as first card,
In the Cset.ini I have BOARD 2 = host

I connected an ADAT to the Pulsar 1 and use the ADAT for all incoming and outgoing signals.

But still the behavior of the ASIO-Signals is not as good as on my old machine.
little pops and glitches as I mentioned above only dissapear if CUBASE is set to Realtime priority.

thanks a lot

The Luna should be your primary card in cset.ini for sure. Also I think you should give doubledawg a shot and check your other PCI devices to see who's hogging the interrupts.

Also I'm guessing you're using the SMP mode in Cubase, which is rather poor compared to the multithreaded operation of other applications?

Lastly, did you set the System panel's preferences to prefer Background or Foreground tasks (ASIO being a background task).

Hi valis,

first thanks!!!

I have a tool that is called latency timer to check that, but that unfortunately does not show PCIe cards-Ionly see the onboard ethernet controller and for sure the 3 pulsars. I check doubledawg a little later.

No I use multiprocessor Mode in CUBASE SX3.

System panel has two possibilities 1 for Prozessor and 1 for the cache.
I have enabled the processor for backgroundtasks and the cache for programms.

thanks again!!

DT

By SMP mode I did mean 'Multiprocessor'. Locking Scope.exe to a single cpu has no effect on the driver. I tried this back in the days before 3.1b brought stability to users of dual cpu's (which I had/dave). However a priority level resolving the conflicts sounds like either something is using a lot of cpu in the background, or that you're dealing with Cubase projects that exceed 80% of available resources...

PCI tweaks actually usually impact PCI performance (doubledawg, check the Masterverb tests thread), crackling is typically a cpu bound issue, or perhaps incorrect system timings for RAM reducing performance when dealing with the buffers, but this is highly unlikely on a modern DDR2/3 system.

Thanks Valis,

in between I checked for the CPU Hooks and disabled a lot of unnecessary tasks of windows- but unfortunately the crackles remain if I stay at High Priority.

Only if I change CUBASE SX3 to realtime priority it is OK. So for now I stay with that and fool around with it a while . I do a little music to come back to what its all about.

HAVING FUN!!!

Cheers

SOLVED!!!

After deleting the raid everything is fine.

Lot of work to find out but ..... maybe it was worth to it for others who want to buid a RAIS with intel 965P

RAID PROBLEMS CRACKLES CUBASE SX

Thanks

No I used the intel drivers. The Jmicron did not allow Raid 5.

So finally I start my cubase in Normal Priority and It works, when I start in it in High it's even better.

OK - Whem I and play 15 VSTi and record 10 Audio Tracks or I load 3 Stylus RMX and 3 EZ-Drummer and use 10 10 Plugs it gets bad again but....
no one needs 10 Reverbs and 5 drum machines so ....

thanks to all and I wish creativity for all of you and ---yes--- for me as well!!!

Incidentally, I believe that the SATA drivers from Intel (and all SATA and old PATA type Raid chipsets) use the cpu for things that a 'true' SCSI Raid card would coprocess. This could be the reason for the crackles....