Alright, so SONAR is acting silly again.

Issue this time:

ASIO Drivers cause Cakewalk to open a project in about 20 seconds after selecting one, and MIDI lag, and a bunch of other stuff. Doesn't have anything to do with my latency options, because I've checked. (this has never happened when I used the ASIO drivers a few days ago)

And when I got tired of the problem, and switched to WDM, I started getting constant audio dropouts, and crashes. SONAR has crashed thrice today! Not sure what's up with this--anyone mind helping me?

Specs:

Windows XP
AMD Athlon 64 Processor 3800+, 2.41 GHz
1.87 GB of RAM

US-144 MIDI/AUDIO Interface, max is 96kHz, 24-bit.
AT2020 mic (back to using that)
M-Audio Keystation 49e keyboard

Project specs are 96kHz, 24-bit.

Can anyone help me please?

Your pc can only handle so much. A dual or quad core pc will handle a bigger load.

And when I got tired of the problem, and switched to WDM, I started getting constant audio dropouts, and crashes. SONAR has crashed thrice today! Not sure what's up with this--anyone mind helping me?

What latency. up the latency. Does your sound card have good WDM drivers?? Maybe you should be using ASIO at a lower buffer if its too much of a lag or maybe what i said above is what you need to do.
If its a new project, then you configured it wrong.
If its a project with stuff in it (you never did say?) then maybe thats all your pc can handle
Whats in this project???? It matters what you have in it Adam. List everything in the project. Maybe freeze some tracks. You know what you need to do and list
Cj

ORIGINAL: CJaysMusic

Your pc can only handle so much. A dual or quad core pc will handle a bigger load.

And when I got tired of the problem, and switched to WDM, I started getting constant audio dropouts, and crashes. SONAR has crashed thrice today! Not sure what's up with this--anyone mind helping me?

What latency. up the latency. Does your sound card have good WDM drivers?? Maybe you should be using ASIO at a lower buffer if its too much of a lag or maybe what i said above is what you need to do.
If its a new project, then you configured it wrong.
If its a project with stuff in it (you never did say?) then maybe thats all your pc can handle
Whats in this project???? It matters what you have in it Adam. List everything in the project. Maybe freeze some tracks. You know what you need to do and list
Cj

I have a dual core, I should add.

There's around three separate files. I bounce the instrumental track once I think that it's final and import it as a wav, and record vocals over the wav if you catch my drift. Anyway, right now, it's all audio, 4 tracks, one of me bass humming, it's about 20-30 seconds, a vocal introduction track with falsetto, and a lead and background vocal track. That's all. I'll try freezing instead. If that doesn't work out, I'll try lowering the buffers in ASIO, but once again, note that when I do use ASIO, just opening a new blank project will take 20 seconds. I don't even want to know how long it'll take to open one like this. Anyway, standby.

I'll try lowering the buffers in ASIO, but once again, note that when I do use ASIO, just opening a new blank project will take 20 seconds. I don't even want to know how long it'll take to open one like this. Anyway, standby.

whats it doing?? VST scan??? disable it, if its scanning. It maybe< that your pc needs to have some cleaning sdone to it and a defrag> my blank projects open instantaniously
cj

Okay, tried everything you said. No luck.

Edit: No, it's not scanning VSTs, it's just being slow, I guess. When cakewalk open's and I press "new project", select a template, the project opens, and then Cakewalk freezes for a while. Same thing happens on playback. It JUST started doing that a few days ago. I don't know what's up with it.

Yeah, that's a good idea. I'll try defragging it. Expect an update in a few hours, but anyway, if anyone else has had this problem, and has found a solution to it, by all means, please, post here.

Project specs are 96kHz, 24-bit.

takes a big rig to handle this. And you won't be able to get it out of a crowded USB buss.

ORIGINAL: Paul Russell

Project specs are 96kHz, 24-bit.

takes a big rig to handle this. And you won't be able to get it out of a crowded USB buss.

Well, naturally, I'm a pimp like that, but hm.

YOur processor is about 4 years old so you are at the very minimum requirements for SONAR 8. I'd run my files at 48khz if I was you rather than the disc intensive 96khz.

How do you get 1.87GIG RAM? For true dual channel memory performance you need to have your memory modules in matched pairs.

Why do you have to export your tracks and import them? The whole idea of a multitrack recording DAW is so you odn't need to do that. Just freeze any softsynth track to free up memory and CPU cycles.

For the delay opening a new file - are you running AVG ?? More often than not I see a delay of up to 20 seconds when opening a file in Sonar 8 Producer [just doing a Ctrl+N to load the default template causes a delay].. I don't see this in Sonar 7 Studio or other applications [like Project 5].. Looking in Task Manager I see avgsx.exe using 100% CPU during this time. The avgsx process is the AVG resident scanner..

I have played around with a few things, adding exceptions to the AVG scanner, but nothing I added seemed to help...

I was thinking of talking to Tech Support on this, because its annoying to say the least. Its not like its machine or driver specific either. I see it on my crappy old laptop which I use for playing with Sonar - that machine is using the on-board audio with MME. My real DAW is a Dell P390 Q6600 machine with an Edirol UA-25. That shows a significant delay too, maybe 5-7 seconds...

I guess the solution is to disable the resident scanner, but that effectively removes any virus protection, so that solution is not on the top of my list !

i guess the 1.87gb ram is 2gb minus 128meg for onboard video - which is a bit pants.

you deffo need to lose the 96khz on that rig.