Hey Slackmaster

  • Thread starter Thread starter tubedude
  • Start date Start date
tubedude

tubedude

New member
I was trying to look through that other huge thread, but its too big... what are your recommended settings that you ahve come up with for your delta in getting best performance with XP?
I am not one of these people that have been having problems (knock on wood) but then again, I built an excellent system with no holds barred and everything works like a dream to this point ( over 3 months). I think a big part of the problem is not M-audio at all, its these people with Dells and Gateways that have major corner and cost cutting done within the mobo's and chipsets and other hardware. Crappy stuff with bad drivers will reflect on other items in your computer. Seen it a million times.
Anyway, what are you recommeneded settings, I have never gone through the trouble to twaek it past its default settings, for the most part.
Also, in Sonar 2.0 with my delta, my latency slider only goes down to around 8ms. I know some people can slide it down to 1.5. Mine shows a minimum of 8ms, any idea why?
Peace!
Paul
 
Actually man I use the 1010 on Win2k. I personally am not a big fan of XP at this point.

That said, I wouldn't do much tweeking if your system works. Seriously, tweeking is often times a big mistake.

Hopefully somebody else will have a few useful tips for you...but don't do anything that doesn't feel right. And especially don't do anything that makes "too much sense." That might sound funny, but most of the completely unnecessary tweaks out there are attached to some rather long winded explanations that are logical but incorrect. Often times they blame microsoft for accidentally doing something that makes the machine perform poorly. Funny stuff. Also, watch out for old tips (that were never that great in the first place), like disabling video accelleration, fixing the swapfile size, defragging once a week, etc.

I would look for tips such as using msconfig to control your startup programs...or disabling services that aren't necessary and are safe to disable (for instance I doubt that anything would suffer badly if you disabled IIS).

Always make sure that you can demonstrate a MEASUREABLE increase in performance after performing a tweak. And don't be fooled by the fact that your machine will always run a little snappier after it's been rebooted! I have a large n-Track project that really maxes my system out...it just barely plays back without hiccuping. I use this test project to measure performance....if playback skips, I did something bad...if it doesn't skip, maybe I didn't need to do that...if it doesn't skip and the controls seem more responsive, then maybe I did something good.

As far as latency goes, make sure you need low latency. For mixing, you only need latency values in the 50-80ms range. For doing live work (apply effects to incoming audio, etc), however, the lower the latency the better. Don't expect to get down to 8ms in a 24 track project though, it's probably not going to happen.

I think that the higher minimum latency thing was introduced to the delta drivers when m-Audio was trying to fix the WDM issue that bdeminil and I raised a while back. I haven't really played with the new drivers yet. I think with ASIO you can still get way down there, but Sonar doesn't support ASIO does it...hmmm.

Slackmaster 2000
 
Cool.
So are there some NEW delta drivers? Where are they and what do they address? anyone having luck with them yet?
THanks.
 
You must log in or register to reply here.
Back
Top