Q10 and Input Monitoring

[Basscount]

I am having an awful time using Input Monitoring with these new A/WDM drivers and Sonar. What happens is after i have applied an effect all will be fine for a little bit, i can hear the effects fine, but after a little bit when i try to dlete an effect the system starts acting jittery and it takes quite a bit for the effect to remove itself. Then i can no longer hear the instrument at all anymore, no signal at all from within Sonar or the Aark manager. Also, at that point, just closing anything in Sonar freezes things for a few moments before it responds, and even closing Sonar itself is the same. My whole comp when i get out of sonar acts sluggish then. And if i reopen Sonar, i still can get no signal at all from any of the Inputs on the Q10 and I have to reboot. I have tried this with up to 20ms latency and its the same, and 20ms latency for input monitoring is useless anyway because of the delay. My system is an AMD Thunderbird 1700, with an ABit KG7-RAID motherboard. I have 512 RAM. I don't know why i am having so much trouble, can someone please help me?

[Rv-Sound]

It works fine here. Did u disabled hardware monitoring on the aardvark?
check the A-WDM sonar setup guide that is on aardvark's website.
Also, what chipset does your mobo has?

[Basscount]

My motherboard has a 761 chipset. I followed the directions from the A-WDM Sonar setup guide on aardvark's site. I am getting all kinds of weird issues now though, not just with input monitoring. I did some recording with my jazz trio tonight with no input monitoring. I made some nice recordings, but some weird stuff would start to happen. For instance, one time after recording a tune, i opened the options menu in Sonar and the whole system got jittery and slow again. I had to close out Sonar altogether. then, when i reopened Sonar, it said that the Q10 drivers could not work with the current audio options in Sonar, But I had Changed absolutely nothing at all, and I had just done a bunch of recordings with the current audio options. Furthermore, when i tried to open the Aark Manager, it would open for a second at most and would immediatley close, and i mean as soon as you opened it, you see it pop up and just as quickly it would close. I don't know what is going on. I never had this problem before. I do also have a SoundBlaster audigy Platinum card as my second soundcard. Do you think this is causing some kind of conflict. I am getting so frustrated. This computer is much better than my old one and i am having many more problems now with these new drivers. Please, someone help me

[Rv-Sound]

Could be a good bet. DS Sultan (another fella from this board) was having problems with his Aark 24, the new a-wdm drivers and his creative card under win2k. The aardvark system service was shuting down on its own. He narrowed it down the the Live's wdm drivers.
A lot of people are having problems with creative cards with wdm drivers running along other cards. I will seriously double check if this is the cause by removing completly the audigy and its drivers and check the aardvark on its own.
I really do think the problem is related to the creative card, as I'm running a direct pro on an iwill mobo (via chipset) with onboard hardware sound (C-Media, not creative) and it still works flawlesly.

[DS_Sultan]

I did not even have to remove the card or the drivers. All I had to do was to disable them in device manager. Then bingo! 2ms latency and rock solid performance.

[Basscount]

Yea, That was it it seems. I disabled the Audigy and I am now able to use Input Monitoring without a problem so far, but I have only been trying one track. tommorrow i will be doing 5tracks probalby. we'll see hot i goes.

[DAW-Freak]

Hi, I also had all kind of weird things happening in Sonar with my Aardvark Aark 20/20+. After many days (and nights)of tweaking and testing I found out the following:
1. Aardvark and the A/WDM driver doesn't seem to like too much using other soundcards (having other drivers enabled)in Sonar. My second soundcard is a M-Audio Delta44. When I disabled it from the drivers list in Sonar things started to work better.
2. Manually changing the DMA buffersizes from the suggested 48 to 64 did improve the performance even further, (it has very little impact, if any, on the latency).So now I'm able to run many tracks of audio with plenty of DX-plugins etc. with a latency of 1,5-10ms! http://www.audioforums.com/forums/smile.gif

BTW I allso have an Abit KG7-Raid mobo.
The AMD 761 chipset does seem to be pretty good for audio cos I never had any problems related to the mobo.

[This message has been edited by DAW-Freak (edited 05-01-2002).]

[This message has been edited by DAW-Freak (edited 05-01-2002).]

[DS_Sultan]

One thing to bear in mind, Aardvark wrote those A|WDM drivers almost exclusively for Sonar! It is not surprising to me that other sound cards are having issue with them. In fact, I can't run any other WDM drivers on my system without having issues with the Aark drivers.

[Rv-Sound]

Well, I'm using the A-WDM on my editor software and ASIO on my multitrack software. My mobo has built in hardware sound too (based on C-Media, not creative) and it is not disabled. Everything works fine with a combo of drivers for each software. However, I can't seem to use the A-WDM drivers on some software as well as using ASIO on other (running each standalone of course, not both at the same time).
I think the drivers still need some minor work to fix this little details, but so far these minor details haven't stopped me from getting the card to work stable with small latencies.
I wonder if anybody has a pair or more aarvark cards working (properly daisy chained) on a single PC with these new drivers. I mention because in the readme included with the drivers there was a note about problems under this situation. I really want to get another 2496 soon...

[Basscount]

Yea, check this out now. I use fruityloops too, and I have my SB Audigy disabled now, so I am using the Aark ASIO drivers and all of a sudden the ASIO drivers failed to work when i opened fruityloops. It would say something Like ASIO drivers Failed to connect. So i had to reboot to get it running again, because when i tried using the Q10 emulated drivers i would get nothing but a choppy, popping sound from them. Also, if i try to play samples before importing them in Sonar, the system gets screwy again and i have to reboot to get it right again. So, for now i can't preview my samples that i make in fruity before importing them into Sonar using the Aark as my soundcard, which Kinda sux, But i am Hoping they will fix all this. When i talked to them on the phone before when i was having all the original problems, they seemed a little reluctant to admit at this stage if it was their drivers. But, it was pretty obvious that it is their drivers, because I didn't start having these problems until i got the new drivers. They did say, however, that they were looking into "possible" conflicts with SoundBlaster drivers in general, and if they determine it is their fault, they will fix it. So, maybe they will fess up. I hope so, because i shouldn't have to be jumping loops (no pun intended) to use my different software and hardware.

[jrummer]

Can you post your system specs and any tweaks you did to track all 8 inputs at once into sonar. i have it all running on a P4 XP box that i just built and i would like to head off any problems i might run into. thanks. i will email you this same request.

Originally posted by DS_Sultan:
I did not even have to remove the card or the drivers. All I had to do was to disable them in device manager. Then bingo! 2ms latency and rock solid performance.

[SonarAardvark]

Originally posted by Rv-Sound:
I wonder if anybody has a pair or more aarvark cards working (properly daisy chained) on a single PC with these new drivers. I mention because in the readme included with the drivers there was a note about problems under this situation. I really want to get another 2496 soon...[/B]

I am running 2 24/96 cards in XP with the new drivers without problem in SONAR.

BTW, I am looking to sell my 2nd one (I bought it to do a band project with that I am now finished with) if you are interested.

[This message has been edited by SonarAardvark (edited 12-09-2002).]