"Solved" Need More Help /I'm having a problem with one song crashing Sonar exe.

Update:

I got it working.....
What I ended up doing was:

I had two vocal tracks that I suspected to be the problem, so I exported the two tracks
out of Sonar, saved them in another location. Then I opened them in a new song file to make
sure that they worked ok.

Then I deleted the two vocal tracks from the song I was having a problem with.
Saved the song as a new file without the vocals,
then I imported them back into the song. The problem went away........:) :)

After posting this here on the forum, Cakewalk e-mailed me about the problem and offered
to take a look at the file, which I thought was good of them.

But as for now....I believe I have it fixed.

So........Thanks again everyone.

Michael



ORIGINAL POST

Edit:

I was out of town when I posted this question. I'm at home now and I can add a little bit more to the error.

Ok here's the error message:
Maybe someone can direct me to a fix for this.

Error - Unhandled Exception
A fatal error has occurred.

Module C:\Program Files\Cakewalk\Shared DXi\VVocal\Cronus.dll
Exception code:c00000005
Address: 27FAAC91:2CA9FAD4:2CA9FB28

As a result of this error SONAR is about to exit abnormally.
Should SONAR attempt to save a recovery copy of your work?
Yes or No

At this point I click yes. Then I get :

SONARPDR.exe has encountered a problem.....bla bla bla.

Any ideas would be greatly appreciated.


un edit:


I'm having a problem with one song crashing Sonar exe.

The song has quite a few tracks audio/midi. FWIW.

As soon as I open the song, Sonar crashes. I get the "will try to save prompt" I click yes
then I get Sonar exe. "has had a executable ...somethin or other thing??' LOL..but then the song still plays/works??

I'm able to mix /add tracks even after I get the crash.

How can I find the culprit?

Thank,
Michael

ORIGINAL: papa2004

Try opening it in "Safe" mode (hold down the Shift key while clicking on the "Open" button)...

I'll give it a try.....thanks..... "somethin' new" :)

Whats cronus?? Delete it and see if it helps. If not, start deleteing everything not native with sonar. start ruling things out..... 3rd party plugs that you get for free are mostly the main cause of these kinds of circumstances.
Cj
edit. If that doesnt help, well then do this..... .... .... ,,,....... ,,,,, ''';;;;';;;;;;;

Whats cronus??

cronus.dll is V-Vocal. The OP probably has a corrupt V-Vocal clip. The fix is to bring the project up in safe mode, then delete and recreate any V-Vocal clips. This is another argument for the standard advice with V-Vocal: create the clip, do your editing and then bounce; don't leave VV clips in your project.

You can always save it as a new project, leaving the old project intact. This is always the safest approach. Once you get the problem resolved you can delete the old project.

I'd like add one more question:

With this song I have numerous v-vocal clips. Just small areas. I always copy the original track/archive,
then work with the copy.
So deleting the v-vocal tracks shouldn't be a problem......but I also used v-vocal on a number of guitar parts
and I don't recall where the sections are.

So the question:
Is there a way to turn off all instances of V-Vocal from one place?? or dis-engage it somehow?

or would starting in the safe mode and not starting V-Vocal/Cronus.dll (dah) be enough?

thanks,
Michael

I don't know of any way to remove or disable all V-Vocal clips at once. You just have to find them one at a time, right-click and select V-Vocal -> Remove.

VV clips are a very heavy load on your CPU. Strange things can happen when you have a whole bunch of them. I discovered early on that the best strategy with VV is to work with no more than three at a time, make the edits and bounce, then move on to the next section of the song.

I don't even like to close a project that has VV clips in it. I always finish up the editing and bounce them before shutting down the project. In the 2+ years since I've been following that procedure, I haven't had any problems at all with VV crashing a project.

You may be reluctant to bounce a VV clip because you want to keep the option open of doing a little more tweaking later. Note that there does not seem to be noticeable degradation if you bounce a VV clip and then create another VV clip from that bounced clip. I used to avoid doing that (using VV more than once on a single clip) on the assumption that any artifacts left by VV would be cumulative. Maybe they are, but if you're careful with VV it's possible to to edit a clip multiple times without ruining the clip.

By the way, it isn't necessary to make a copy of the track/clip before working on it with VV. SONAR will do that automatically. It overlays the VV clip on top of the original and just mutes the original, so even after bouncing the VV clip you can still backtrack and start over if something goes horribly wrong. Just delete the new clip and un-mute the original.

I got it working.....see my first post.

Thanks,
Michael