tomixornot


How about downloading and running Rea*** and see if it runs and record ok on your computer ? 

This enables you to verify if it's your PC / Audio interface / drivers fault.

This untrue statement lends nothing to the conversation, but could make this thread entertaining.  : )
 
Brian

Are you recording to a second disk?

Stone House Studios

tomixornot


How about downloading and running Rea*** and see if it runs and record ok on your computer ? 

This enables you to verify if it's your PC / Audio interface / drivers fault.

This untrue statement lends nothing to the conversation, but could make this thread entertaining.  : )
 
Brian

Actually I think it's a good idea.
I did this last week and was able to trace my problems to my interface firmware.
Not that X2 is stable. We all know that it could use a few tweaks.
But my main issue was my interface.


You could also use Audicity but in case it was X2 I wanted something to record with while Cakewalk irons out the beta version of X2. 


Mike

With a bit of work this should be easily fixable - is there anybody in Canada that could go and help him onsite?

Really like this track of yours! Got a real Beatles feel - would be a shame to lose a talent like this from Sonar methinks.

http://www.youtube.com/watch?v=pO01AYKyF_0

Thank you everyone.  I have figured out that the issue is not Sonar so I am climbing in back off the ledge.  I tried X1 and still had issues.  So that confirms everything.  I will be taking these suggestions from everyone and trying them out tomorrow night.  Will let you know how it goes.

One thing.  Sonar is a great product.  One of the things that makes it great is this community.  I don't know if other DAWs have the same.  Doesn't matter.  There is a great sense of camaraderie here.

Cheers

Try the following and see what happens.
 http://www.thesycon.de/deu/latency_check.shtml Download this software and check what it says or post us a screen shot. If you see high spikes you are getting interference so first disable on the onboard sound drivers under hardware devices in the control panel. Then run the latency check again and see if that make any difference. Once we eliminate  the onboard sound system we will try other steps.

First step should be to submit a crash dump to CW for analysis. That will tell you what's instigating the crash, which is a pretty important thing to know before you start troubleshooting.

Damn, Bit.


Diagnosis before treatment? What kind of radical intellectual bovine feces are you trying to peddle here?


Everyone know the answer is always buy a new whatsit.

M-Audio..........

munmun


Thank you everyone.  I have figured out that the issue is not Sonar so I am climbing in back off the ledge.  I tried X1 and still had issues.  So that confirms everything.  I will be taking these suggestions from everyone and trying them out tomorrow night.  Will let you know how it goes.

I would have tried using a competitor's product for that test, because there is a good chance that any code causing problems for you in X2 might have been there in X1 as well.


I highly recommend using one of the latency checkers out there.  That should determine if there is a problem in your system.


If there is a problem with your system, the first thing I would recommend is disabling any network adapter you have.  Especially wi-fi.


Also, don't forget to check your motherboard drivers and BIOS.  I recently had a bad dpc latency problem which was fixed in a BIOS update.  I was especially annoyed because I had just purchased it and it was already several revisions behind.

hey munmun: Welcome back
good you got sorted out..
Maybe you could edit you thread title to reflect this positive outcome. With the recent negative posts around here it would nice  ifyour thread title could reflect your positive result because of the help you got here.
Just a thought. All the best.