Odd drop-outs in 8.5, win 7 64bit while recording- why?!

I've recently upgraded my puter to win 7 64 bit, 8 gig RAM, ssd C drive, all that stuff- and now when recording, I get these surprise DROPOUT's for no apparent reason. The CPU barely registers any load, no soft synths hardly, just dies suddenly. Then works fine... What's up with this?! 

I saw a post about opening the aud.ini in audio options>configuration and it said to change the text file in aud.ini to a longer dropout time. Anyone do this and like it? 

I appreciate any advice!-
Ev

Soundcard? 

Why Legacy drivers? 

focusrite suggests you use older drivers than the most current up to date ones?  IME the only reason a company would do that would be because they are aware of a bug in the drivers for your paricular platform.

are you recording your audio on the SSD drive?  or do you have a separate audio drive?

what kind of FX and softsynths do you have in your projects during these dropouts?

AH! that makes more sense!  according to some of the computer builders in the hardware forum it may not be necessary to use the legacy firewire drivers any more.  they have stated that win7x64 SP1 has overcome those past problems.  FWIW I am running the current win7x64 SP1 firewire drivers with my MOTU and I have had no problems.

the reason i asked about FX and softsynths, tho, was for a specific reason - you said "hardly any" but I was looking for specifics on which ones because one of my problems in the past has been with a particular version of Kontakt causing crashes for me in sonar.

evansmalley


lots of geeks advise to do so in win7 64 bit- I don't know why- tried it both ways, seems to be better so far! (Focusrite also recommends it)

Pretty sure Focusrite has new drivers for 64 bit windows. Check their site. They don't recommend old ones anymore.
John

evansmalley


I've recently upgraded my puter to win 7 64 bit, 8 gig RAM, ssd C drive, all that stuff- and now when recording, I get these surprise DROPOUT's for no apparent reason. The CPU barely registers any load, no soft synths hardly, just dies suddenly. Then works fine... What's up with this?! 

I saw a post about opening the aud.ini in audio options>configuration and it said to change the text file in aud.ini to a longer dropout time. Anyone do this and like it? 

I appreciate any advice!-
Ev

I tested firewire and the Pro 40 a year ago on i7 860, W7 x64, 8G ram but ordinary hd's.

Is your firewire card sharing irq with controller for ssd disks?

When trying to use 128 samples latency I got dropouts with synths. I could run projects with 20 tracks of audio only just fine.

My theory was that the firewire cards had very different reported latency for in and out, like 128 in and 192 out etc.
When setting latency to highest, like 192 it was fine.

So Sonar is calculating or handling synths in a wrong way it seemed to me. It was an empty project with just one synth like DP and after a couple of notes from keyboard it crackled.

It ran on 128 samples in Reaper just fine, audio or synths.

Anyway I gave firewire the boot, and got an internal card based RME interface instead. But the Pro 40 sounded really nice, and for that price I would say unbeatable. (It's a pity with only 55dB gain which could not handle my favourite mike so even their OCTA series is too weak for me.)

Other things I did for better performance:

1. turned off core parking in bios
2. turned off dynamic overclocking
3. I also found legacy driver using half cpu from original, even though vendors claim to support new w7 1394 drivers.

Just a few notes from my testing....