http://www.homerecording.com/bbs/showthread.php?t=138942
That is the 2 page long thread that is still being built on over at homerec on the same issue(s). If you can't read that, let me know and I'll copy and paste the bulk of it on here for you. Hopefully you can skim through it though, because there's a lot of trial and error stuff that was kept track of on that thread.

Actually I'll post some of the stuff here anyway, incase you want the summary of it all anyway.
Basics:

this battle never ends with this Q10.
So here's the just of it.
In Vegas, I can play a limited number of tracks with effects no problem.
I opened up a project I was working on a few months ago (with the Delta44 - and I had no problems at all with it...it ran smooth as a babys butt), and immediately tons of pops and clicks.
Boosted the buffer size in the Q10 control panel to 512, with ASIO Turbo activated (I dont even know what this does, but it makes the delay time less so I clicked it, i'm using vegas 5 too, by the way). With this, I get maybe a pop/click in one playback of a song.

I recorded a new project the other day, just 2 mics at a time, no clicks or pops - I'm worried that If I start recording 2-4 mics at a time, with 10+ audio playing back as well, that I'll have clicks/pops in the recording (which I CANNOT have) - will this happen?

Should I keep boosting the buffer size higher? How high is too high? With TURBO MODE and 512 selected, 11ms latency. Without TURBO MODE, it's 20ms. And, I dont REALLY even know if turbo mode is working with vegas!

So another big problem, I started working on one of those projects, had an effect or 2 or 3 on all 15 of the tracks. No big problem yet. I added Ozone 2 DX to the master channel (never used to be a problem). Whole computer stops responding, audio never stops playback, extreme amount of clicks/pops, its just going crazy. I have to turn the sound down quick (its lound and annoying and sounds like death), and then press the reset button on my box to force restart the computer. WHAT!?!? what is my problem here???

AND in the meantime, I STILL have this problem:
I get pretty choppy playback from anything opened in windows media player, winamp, and also in fruity loops. In FL, the only way to make it bearable to listen to is by putting the Direct Sound buffer size IN FRUITY LOOPS up to the MAX. What else can I do in the Aardvark control panel to fix the rest of these issues (there are direct sound buffer size thing, but it seems like it has no effect on anything)?

Computer:
-ASUS A7V333 KT333 MB W/ ATA133, USB 2.0, 5.1 AUDIO
-AMD Athlon® XP-2000+ Processor AS22
-60GB 7200 RPM UDMA 133 HD
-130GB 7200 RPM Western Digital HD
-1gig PC2700 333MHZ DDR MEMORY
-Microsoft Windows XP Pro
-ATI Radeon 9200
-AMD Certified ATX Medium Tower Case - 350 Watt
-52X CD +/- R/RW
-4X DVD +/- R/RW

Hardware:
slot 1:
slot 2: Network Card
slot 3:
slot 4: Q10 (sharing NO IRQs)
slot 5: Firewire (nothing plugged in, AND disabled in windows)

I have tried disabling the network card as well, no luck.



The biggest problems seem to come now when I put something like OZONE on a fairly big project. Only reason why this angers me is because with the delta I didnt have this problem. For some reason, though, Vegas is choking up with the Q10.

latest post on it is pretty important I figure though:

Project set to 16-bit in vegas. Aardvark set to 16 OR 24 (either one..i guess this just sets how it will record the audio). Windows classic wave driver. White noise gone! haha.

I don't know what this means...but maybe it means something to somebody else? haha.

EDIT: But with those settings, the comp still bottlenecks up and crashes with something like ozone running as well...and windows media player of course still starts after a 5-10 second delay because that has nothing to do with veags, ha.

Thanks!!

Didn't you mention in another post that you bought the Q10 used (ebay)? If so, if may be defective. I assume you've tried different Q10 drivers to see if this makes a difference. Also try unistalling and reinstalling the drivers. At any rate, the PCI card can become damaged through improper handling (static can zap them). I also assume that you confirmed that the Q10 will work properly with your mobo/chipset before purchasing?? Clearly since all seemed to work well with your previous m-audio card, this is an issue with the Q10 and not Vegas.

drbam

What forum is that thread in on home Recording? What is the thread's title?

This sounds like a driver/hardware issue, whether configuration or otherwise. I have an older Aardvark card and have no issues with it and Vegas. The drivers are a bit flaky - always have been - but it works with out any issues.

Peter

I don't understand why people blame Vegas for problems with their sound card or the drivers for those cards. It's not the fault of Vegas. Get a decent sound card and appropriate drivers and Vegas will make you happy.

then again...

HOME REC: It's under "computer recording" , then the thread title is, "so it turns out the Q10 WONT work right..ha..great."

yes I'm aware the Q10 could be messed up, I'm hoping not. I'm just tryin to make it work.


wobblyboy: i dont know what you're talking about, ha. who is blaming vegas? i'm just tryin to make it work man, chill out. ha.

I recorded 8 channels last week for 2 - 75 minutes continuous sets with Vegas 4 and the Presonus Firepod using a Compaq PIII 1.2 laptop.

No pops, clicks, drop-outs, or other spurious noises. Just clean audio.

- Mark

"I recorded 8 channels last week for 2 - 75 minutes continuous sets with Vegas 4 and the Presonus Firepod using a Compaq PIII 1.2 laptop.
No pops, clicks, drop-outs, or other spurious noises. Just clean audio."

- Mark


Just curious, when using your PIII laptop, what did you use for your audio record drive(specs), for these multiple 75 minute 8-track sets . Also, what bit/sample rate?

Best regards,

Billy Buck