If u are one of the lucky guys that have a firewire 410 with normal volume output and stability in drivers (or u think so ) then its fine by me :). I've also tried the firewire1610 and the firewire Audiophile and they both too exhibited the same problem losing the already installed driver plus they exhibited lower than normal volume output and (the 1610 also had hum noise through the analog connections) which in my book doesnt have much to do with drivers but malfunctioning -worse than mediocre - hardware. As the m-audio driver matured the card now behaves correctly all times whereas the m-audio firewire interfaces have proven to be unreliable. PS: I had the very same problem with the usb quattro some years ago with my old compaq p3 and xp pro laptop. The thing here is i had a hell of a time last year with M-audio firewire 410 on my sony FE11 laptop & xp pro sp2 with the system constantly losing the already installed driver so many times that i actually returned back to the very old M-audio quattro (USB) which works brilliantly. External audiocards are highly driver and system config depended and an immature or poorly written driver can lead any type of card to 30-40% cpu usage even when being idle. However, if left open for a long period of time and minimized I find that it starts to act up more upon returning.Īctually firewire also uses cpu but less than usb typically.Their main difference that makes the audio world lean to firewire more than usb, is that firewire has a sustained data transfer whereas usb does not. I usually find this gives it a good clean start. Give priority to background services and disable non-essential services to lower CPU usage.ħ) Restart your computer before starting work on a project and just open Acid by itself. You could also try earlier version.Ħ) Optmize your computer. Version 6.0d seems much better at recovering from this. If the program freezes try to hit the stop button and wait patiently otherwise you will freeze up the program permanently.
Virus and spyware software can also be a huge CPU hog. I have seen CPU spikes with Outlook and other programs open, even AIM. This can cause huge delays if it's busy looking around the drive for data.ĥ) Make sure you close other programs running. (do not partition the drive to accomplish this). Also make sure that in your settings you do not have selected "keep bypassed fx running" otherwise bypassing them will gain no CPU.Ĥ) Try using a different drive for your working/project files separate from the operating system/program drive. I am having good success with my AC97.ģ) Disable/Bypass any plugins/vst/effects until you plan to render the final project. Some other ideas to optimize your experience.ġ) Try a different/better sound card interface (firewire, cardbus, pcmcia, etc).Ģ) Try using ASIO4ALL on the internal sound card for your laptop. ACID will definitely freeze up more while waiting for other devices.
0 kommentar(er)
