HELP!Dropouts,crackles,error messages,smoke,sparks and flame!

  • Thread starter Thread starter acidrock
  • Start date Start date
acidrock

acidrock

GO PACKERS!
Just kidding. :rolleyes:

Everything is running fine and I don't need any help...right now.
 
I was on my way. :D

I'm glad you're OK.

I was having some issues earlier but I think I worked it all out. I was getting some drop outs here and there but I guess it's cool now.
 
The sparks and flames are actually normal behavior if you use Console View.

It's sorta like a warning system from god. :D
 
dachay2tnr said:
The sparks and flames are actually normal behavior if you use Console View.

It's sorta like a warning system from god. :D
Click to expand...
Veeery funny! You're just jealous of my two screen setup (apparenty)... :p
 
I've noticed how much traffic has slowed in this forum,and attributed it to the fact Cakewalk and computers have gotten sooo much better.
This thread is for people who are having no problems. :cool:
 
Um............. maybe you should stop by CW's Sonar Forum. Plenty of folks with Sonar weirdness.
 
I've been fucking around with this thing all afternoon. I'm about to give up on Darla20 drivers. Did a system restore to prior to Sonar and Darla, reinstalled them, and damned if it won't lock the sample rate, then I got a bluescreen memory parity error again.

Know anything about DEP? It's in WinSP2. I may go back to SP1 to get away from that nonsense too.
 
Last edited:
Time to start from scratch. :(

From reading your thread,it sounds like you overtweaked.
I think todays systems are much hardier and a lot of that tweaking is a leftover from the underpowered computer days.

Running two soundcards can be a problem.

Can't speak to the Darla,I've had both the M-audio Audiophile and Delta 66 and never had a problem with either.

Bigger than shit, I can hear the audio echo through the Audigy, but I got nothing in Sonar's meters
Click to expand...
Do you have input monitoring enabled on the track?

Normaly I mute the input on my soundcard and enable input monitoring on the track.That way I only hear what Sonar is hearing.
It sounds like you're doing the opposite.
 
I got the Audigy to record flawlessly. I had to get in the Win mixer and check "what you hear" to get Sonar to see the input. Sounds okay. Sounds like a soundblaster.

The Darla just doesn't want to cooperate. Sonar doesn't seem to recognize the tracking frequency, even after running hardware profiler multiple times. When I had Darla in the old p3/500 it wouldn't run right until I put in a second HD and loaded CW9 and all the audio files onto the second drive. Maybe that is the fix here too. Maybe trying to read/write across a 250g SATA drive is too much to ask. It shouldn't be, though. Darla played well with an SBLive card that's still in the p3.

What's really throwing me off the Darla drivers now is how well the Audigy is working. The video isn't locking up, CPU usage is minimal. No snap/crackle/pop.

I'm gonna make some calls Monday about a Layla3G. Digitraxx has them for $439 with free shipping so I'm gonna quit trying to put yesterday's tech into today's machine.
 
You do have Identical bit/sampling rates checked in both Sonar and the Darla software?

I'm gonna make some calls Monday about a Layla3G.
Click to expand...
Have you checked around to see how this plays with Sonar?
 
You must log in or register to reply here.
Back
Top