Delta 66 and crackle/sizzle Producer 8.5.X

Hi and HELP!

Recording and playing audio I get a sizzling sound. WDM or ASIO makes no difference. I don't get it in Sound Forge.

Config:
Windows 7 32 bit
latest M-Audio Driver (5.10.0.5074)
P5 750
Intel DH55HCMB
Sonar 8.5.3
ATI RADEON 24HD Video Card

No IRQ conflicts
Tried all 3 PCI slots
disabled all other devices except video and SATA (obviously)
tried asio4all
changed buffer settings to ridiculous proportions
disabled the D66 devices in the Windows Control Panel

If I don't get the sizzle recording, it will show up in playback/mix down. Audio exports with it as well.

I'm at my wit's end - open to all suggestions including recommendations for a decent replacement, I really don't need all the power of the Delta 66, and definitely not all this frustration.

Thanks!!!

Tom

Are you using an M-Audio interface? I read on here that the drivers don't work well with Sonar. Not saying it's true but I just read it in another post.

The latest Delta 66 driver for Windows 7 is Delta_6.0.2_5.10.0.5074.exe. I assume that's what you meant. The M-Audio Delta drivers work fine under Windows 7 so that is not the problem.

Don't use the ASIO4ALL driver. I prefer to use WDM mode with my Delta44.

What are you recording from? A microphone, guitar, etc. ?
How much memory on that computer? You should have at least 2GB or more to run Windows 7.

Need more info and possibly a sample of the sizzling sound.

If it was the drivers I would think the problem would present in Soundforge as well...try changing the metronome settings, or making a click track and have it trigger, say, TTS-1, on different in/outs than your recorded audio.

changed buffer settings to ridiculous proportions

Can you expand on this. what exactly did you change and what did you try? allot of users get the ASIO buffer and the Recoding & playback I/O timing buffers confused.
It helps if you fill in the blanks as to what settings you tried. And make sure you have the latest win 7 drivers. There were recently just updated.
Also, list your Peak dB levels on your tracks, master bus and main outs.
 
If your getting artifacts upon play back and bot recording, it can be 3 things:
IRQ conflict - You already ruled that out
Driver config/not having up to date drivers - This can cause what your experiencing
Clipping/Signals too Hot - This will also cause artifacts upon exporting
 
Cj

Cubase did the same thing.  I did also forget to mention I had this card in an XP box prior to this and it took major tweaking but worked OK.

So I went out and bought a Tascam US-122 MKII for $99. and it worked perfectly straight out of the box. I re-enabled all he stuff I disabled and lowered all my buffers and latencies back to optimal and it still works fine. It consumes half the processor power I was consuming with the Delta 66, there's actually less latency and obviously, no noise.

When I went into the local music store, one of the good stores that has recording studios attached and what not, I told the guy- who really knows his stuff- I had an M-audio card and he said immediately, "that's a shame, they aren't keeping up with their drivers for the newer operating systems. I hear your story all the time. Try this one, it does a decent job for the price and it will work fine for you." Given all the other message threads I've found on this board, M-audio's and others about nightmares with this card, I tend to believe him. Shame.

I'll hang onto the card, it looks like M-audio is still selling the Delta 66, maybe someday they'll get it right and I'll have a really nice setup!

Midiman seems to be having some problems lately with certain products and drivers. I suspect it's the Avid takeover that is throwing some sand in the gears, but I don't know for sure.

That being said, the Delta 66 has been one of the exceptions to the rule although some people still seem to have troubles. The drivers for Windows 7 x64 have worked perfectly for me and I can get 64 msec latency with no pops our clicks when playing Ivory or any of my other VSTi.

In the future though when I buy a new card it will NOT be a Midiman unless they get their act together.

wormser


Midiman seems to be having some problems lately with certain products and drivers. I suspect it's the Avid takeover that is throwing some sand in the gears, but I don't know for sure.

That being said, the Delta 66 has been one of the exceptions to the rule although some people still seem to have troubles. The drivers for Windows 7 x64 have worked perfectly for me and I can get 64 msec latency with no pops our clicks when playing Ivory or any of my other VSTi.

In the future though when I buy a new card it will NOT be a Midiman unless they get their act together.

They've finally released an updated driver for the MIDIMan series of interfaces. I got tired of waiting and bought a Cakewalk UM-3G interface back in December. It works fine, but it was $60 I wouldn't have had to spend had M-Audio had their act together. I'll remember that next time I buy a product.

daveny5

wormser


Midiman seems to be having some problems lately with certain products and drivers. I suspect it's the Avid takeover that is throwing some sand in the gears, but I don't know for sure.

That being said, the Delta 66 has been one of the exceptions to the rule although some people still seem to have troubles. The drivers for Windows 7 x64 have worked perfectly for me and I can get 64 msec latency with no pops our clicks when playing Ivory or any of my other VSTi.

In the future though when I buy a new card it will NOT be a Midiman unless they get their act together.

They've finally released an updated driver for the MIDIMan series of interfaces. I got tired of waiting and bought a Cakewalk UM-3G interface back in December. It works fine, but it was $60 I wouldn't have had to spend had M-Audio had their act together. I'll remember that next time I buy a product.

I did exactly the same thing!
I bought the UM-2G though because I got tired of waiting as well.

I'll remember it as well next time I buy a product and I suspect quite a few others will as well.

I also have a Delta 66 with the same issue. Right now I have Vista but will be upgrading to a Windows 7 cpu. It drives me nuts because I have to record a few seconds of a take to make sure that there's no sizzle on the track. It has nothing to do with recording too hot, etc.
Could be a driver issue with Sonar, don't really know. It happens with ASIO and WDM...my only recourse has been to restart Sonar. I never had this issue with XP....anyone have a fix that still has Vista?
Thanks

Gaffpro


I worked on a new tune last night. I did multiple vocal takes on separate tracks...after about the 8th one, I had the sizzling sound on the track again. It's not my hardware or cables. Cakewalk states that it could be an issue with the Delta 66 I'm using. Help!
Thanks

What latency setting are you using? Have you tried possibly freezing some tracks, just to go over the process of elimination for troubleshooting?