PlanetZ forums - scopeusers.com

Hello again,

Well I am slowly getting the hang of things, with version 3.1c and I can now at least get going again with music making. Thanks to everyone who has responded and helped. I am however still using the big mixer from version 2.4 as I still can't get my head around the new STM mixer as far as creating the same type of projects I was using in 2.4. I love the new synths by the way (the Lightwave , Prisma and Vectron player)

But.......Since using 3.1c I now get (more often than before) "PCI Capacity reached."
I have tried the tips suggested in the support section of the manual but with no luck. I'm not using much in the way of resources. So I'm not pushing it to the limits. I relaunch it and Logic 5.5.1 too and then it will work ( after I have done this about 3or 4 times). One time, the Pulsar card let out this really horrible,loud, constant noise that I could stop until I pressed CTRL+ALT+Delete. It was bad!!!! I was wearing headphones at the time and I just hope I haven't had damage to my ears (they still hurt). It was excruciatingly loud!! If had been running it through my monitors I am sure it would have blown the speakers.
I have read in previous posts that the "PCI capacity reached" problem could be USB related, but I need USB for my midi interface and my dongle for Logic. This problem I should add doesn't occur when I use only Reason and Pulsar and there I am using my USB interface. So I don't think it is USB related. In fact everything works perfectly with Reason.

I still use Win 98 and an old PC (a 450). But I am upgrading this week to a faster machine (a 2.8ghz) with all the bells and whistles and XP. Will this help solve the problem? Or should I consider using a MAC, or does the same thing happen with them?

Thanks in advance for your responses.

<font size=-1>[ This Message was edited by: Weirdo The Weird on 2003-07-26 01:25 ]</font>

I'm having the same "PCI limit reached"problem on a new AMD machine. Still haven't found a cure for it. It's not the USB for me, and I usually can continue after pressing "retry" one or two times. Never saw this on my old (Pentium) system...

Or should I consider using a MAC, or does the same thing happen with them?

Well as a Mac user i could just say go for it, but really there are lots of things to consider (ie. cost of cross-grading sequencers, other apps etc.). Certainly i've never experienced nor heard of any Mac users having their hearing damaged from a Pulsar, so i don't think you'll get any nasty shocks out of a Mac.

However their are plenty of PC users here (more than Mac) who have no such problems, hopefully they may be able to help . So it boils down to: do you mind tweaking PCs and getting dirty to get your system running smoothly, or do you hate all that and want a simple dimple system? If the answer's the latter get a Mac (that's what i did).

Cheers,
Mr Arkadin (simpleton)

PS. i would seriously dump Big Mixer and get with the STM range as they are far far better. The learning curve really isn't that great if you've used Big Mixer and hardware mixers.

<font size=-1>[ This Message was edited by: Mr Arkadin on 2003-07-26 06:38 ]</font>

Weirdo, you don't have to 'use' USB, it's polled every 2ms (afaik in Win98). It's acting exactly like the auto-insert notification of the CD Rom, which you probably disabled for obvious reasons
I dunno if the software quality of USB drivers is improved under XP, but those machines usually run 4-6 times faster than your current one. So it is not so time critical, if a task is delayed for some cycles due to the USB-hello-something-happened-?-poll.
If an application (for example Reason as a rather modern product) anticipates those interuptions and sets it's data buffering and timing accordingly, there are no problems.
But Logic is way older (I assume they didn't rewrite the app's core routines) and it may get trapped in some situations. Logic seems to have a kind of primadonna behaviour, on my system it even looses it's ASIO sync while running empty with nothing to do, just for the fact I switched it in the background

cheers, Tom

Logic seems to have a kind of primadonna behaviour, on my system it even looses it's ASIO sync while running empty with nothing to do, just for the fact I switched it in the background

That's easily fixed by changing Logic's priority to "AboveNormal".

Kim.

tnx Kim, but how is this done in Win98

actually I'm not having a problem with this, it was intended more in the direction of an example. If a program doesn't even notice it's running idle then it might not be the most smart piece of code on earth.
This doesn't affect it's general use as a sequencer of course.

cheers, Tom