Haaaa , , , Pulsar eat CPU !!! Why???

Signal X · Post by **Signal X** » Wed Nov 07, 2001 3:37 pm

After a lot of experiments, I found Pulsar 3
eat a lot of CPU under Win 2K.
It all looks ok when starting to work with Pulsar & Cubase 5.06 (I also tried 5.07pb5)
untill VST "CPU performance" goes to 40-50% or more.
Both Pulsar & Cubase start to react very very slow.
In Win98 it all worked perfect !!!
Where is the fucking problem ?
Cubase? Pulsar? Windows?
Damn I have 18DSP, P-III 1000MHz, CUSL2, 512MB, Matrox G550, 4 SCSI HD, WHY?

at0m · Post by **at0m** » Wed Nov 07, 2001 4:01 pm

Hi

Not Pulsar users CPU, but ASIO does. you may have 64Ch ASIO there- start of w 4-8ch ASIO, chk cpu again.

Signal X · Post by **Signal X** » Wed Nov 07, 2001 4:30 pm

I use ASIO2 16 Bit Source.

JoeKa · Post by **JoeKa** » Wed Nov 07, 2001 5:07 pm

I have the same problem, under W98.
Must be the V3 ASIO drivers that are much more CPU-hungry than those of 2.04...
But I have only 500MHz, so you can easily guess what remains for working.

I want those old ASIO drivers back! They were really ok in the matter of CPU-usage.

At the moment it´s only possible to record stuff either via the Wave drivers or to my SCSI disc. IDE and ASIO won´t do it, but it used to with 2.04.

I just hope, CW´s gonna get this fixed. It´s the last problem left on my system, and I tried it all, every proposed tweaking of system parameters and stuff, but none helped.

algorhythm · Post by **algorhythm** » Wed Nov 07, 2001 8:28 pm

has anyone tried loading their v2.04 ASIO drivers into V3?

that might work (?)

JoeKa · Post by **JoeKa** » Sun Nov 11, 2001 5:29 pm

I tried the "old" Asio drivers, but the problem stays, my machine has so little CPU-ressource left via the pulsar asio that I can´t even have a nice VST delay running and modify it real-time... does anyone have an idea where the problem has its roots? Where is my VST-performance gone? It all worked great in V2.04a, but now it doesn´t. I don´t even want to have Pulsar running in XTC mode but rather in normal mode, I find this much more flexible than XTC...
But what happened to CPU ressources?
I use the "normal" VST5, so I can´t really use the 32bit ASIO.

subhuman · Post by **subhuman** » Sun Nov 11, 2001 5:48 pm

There are new ASIO drivers in V3. eg. the 64 Channel ASIO or ASIO Flt64 etc and they will take more CPU...

JoeKa · Post by **JoeKa** » Sun Nov 11, 2001 6:08 pm

But I´m talking just about a pure, simple Stereo ASIO connection, one for recording and one for Monitoring, nothing more...
This makes me mad, I can drive Pulsar to the limit or not, but VST won´t even playback one second of audio or VSTi-sound without stuttering and crackling.

dbmac · Post by **dbmac** » Sun Nov 11, 2001 6:38 pm

Yeah, somewhere in the changes from Pulsar 2.04 to 3.01 and/or from VST32_5r5 to 5.1
the ASIO engine has degraded. Audio breaks up when recording while playing multiple tracks. Didn't happen before.
/dave

at0m · Post by **at0m** » Mon Nov 12, 2001 3:15 pm

On 2001-11-07 20:28, algorhythm wrote:
has anyone tried loading their v2.04 ASIO drivers into V3?

that might work (?)

On 2001-11-11 17:29, JoeKa wrote:
I tried the "old" Asio drivers, but the problem stays, my machine has so little CPU-ressource left ...(cut)

There's ASIO*.dsp too probably. look for other asio.*, and try to replace them. backup first what you're overwriting so you can always undo!

That's how SP/DIF is updated in 3.0 on Pulsar1 cards too, it's not only the '.dsp' but also a '.ol' file.

So check your ASIO*.dsp, .pep and .mdl's.

a t

m i c

bolster · Post by **bolster** » Wed Nov 14, 2001 4:09 am

I had the same problem when I first installed v3 - cpu load in Cakewalk went for 5-10% upto 30-40% and screen redraws slowed right down. I uninstalled all Pulsar software and reinstalled from scratch and everything was fine. Just remember to back-up all projects and any presets you want to keep as the uninstall process tends to delete everything !

Air_PoLLo · Post by **Air_PoLLo** » Wed Nov 14, 2001 10:54 am

I saw all the posts here and I made a test; 32 channels of ASIO from Logic to Pulsarmixer then from there routed with 32 channels of ADAT into a Digitaldesk.

I didn't notice much CPU usage... everything rather normal. I use Logic 4.8.1 with pulsar 3.0.1 and MacOS 9.2.1 I'll make some tests with nuendo and cubase. (Nuendo will be a crack version, let's hope it works anyway)

JoeKa · Post by **JoeKa** » Wed Nov 14, 2001 3:22 pm

Bolster, yep!

Reinstallation of my whole stuff was what I wanted to avoid if possible. But I read your post and finally, I did it, complete new system installation on another HD, WIN98SE, all drivers, PulsarV3, the 3.01update, VST5.0 and the 5.1update, in this order.

And now, it seems to work properly. I hope it is REALLY bullet-proof this time, I never want to do all this again!

But it´s not complete yet, there´s still a huge load of various plug-ins waiting for installation... free synths´n´FX for both, VST and Pulsar. I hope it all stays stable along the completion of my setup.

subhuman · Post by **subhuman** » Wed Nov 14, 2001 3:35 pm

Now that you finally have it working make a diskimage (or Norton Ghost), then you don't have to mess with configurations anymore (until the next versions, but you'll have a ghost image to go back to, right?

JoeKa · Post by **JoeKa** » Wed Nov 14, 2001 4:14 pm

That´s exactly what I want to do, but first I´m going to test it all to the very limits... and if the promises are kept, I´ll copy the complete HD to another one, and THAT goes into a locked-away box until it is needed.