I have the same problems, also with a good spec PC with 2 drives and the RME hammerfall. I heard that it's the implementation of ASIO that's the problem - ie it's not implemented properley. RME are using Cubase VST as their test software and it is supposed to work just fine with that. Apparantly it's up to emagic to do their bit. As soon as I enable PC AV in logic, midi timing turns terrible and I get the CPU overload messages (PII 450). Anyway, I hope emagic fix the bug for version 4.05 as I'm sick of wasting timing tweaking the technical side. Cheers, jono

Hi I tried all tweaking, had different graph cards installed: nothing has real and lasting effect with the CPU error. Ansi; I just set the G 400 hardware acc to full again because, indeed it didn't make a difference as my card works fine and other audio prg suffered. For those who believe its an audio matter: I've seen it playing ONE miditrack, while before and after, working on songs with 14 audio + plugs and 10 midi and not seeing it at all. The only thing is, when pushing your system you'll see it more often and it will event. come with the "fail to recover pc av bla...." No crashes here, just irritation because of short interruptions in my work. Random audio has to do with graphics, but prob. in the way logic handles it. My card settings have no effect on that. Emagic: are you shure your graph interface works right? Is there a way your "filling the CPU gaps" method reacts or releases too slow thus creating a short overlap thus creating the errors ? Can you measure that ? Just a shot in the dark Cheers Budy

One possible clue is my experience yesterday running Samplitude 2496(audio) and Logic(midi. the AV box is unchecked in audio preferences) together on the same machine and having them both chase MTC coming from my Darwin. They each had their own windows open on my desktop (small enough so they don't overlap). If I had Logic "focused", sampitude would quickly get starved for cpu cycles, sputter and stop. However... if I have samplitude in focus then they both ran just fine together. On my system Logic 4.04(oink!) and the system (windoze 98) take up 60 MB. Add Samplitude and it goes up to 90 MB. When running the windows performance analyzer, with Logic 4.04 the cpu is always at 100% but running Logic 3.5 it never goes above 55%. Budy wrote: > > From: "Budy" <thirdeye@l...> > > Hi > > For those who believe its an audio matter: I've seen it <SNIP> interruptions in my work. > Emagic: are you shure your graph interface works right? > Is there a way your "filling the CPU gaps" method reacts > or releases too slow thus creating a short overlap thus creating the > errors ? Can you measure that ? > <SNIP> Thanks, -Randy Hammon Savage Resurrection TranceKat Music "Trance Polka for the Next Millennium"

Thanks Johnathan >>I have the same problems, also with a good spec PC with 2 drives and the RME >>hammerfall. I heard that it's the implementation of ASIO that's the problem >>- ie it's not implemented properley. >>RME are using Cubase VST as their test software and it is supposed to work >>just fine with that. Apparantly it's up to emagic to do their bit.

>>Random audio has to do with graphics, but prob. in the way logic handles it. My card settings have no effect on that. Emagic: are you shure your graph interface works right?<< FYI, I get the cpu too slow errors, and I have a Diamond Viper V770 w/32MB RAM, P2-300 w/256MB of RAM!