Sonar 5 crash on launch

[Mr. Slater's Parrot]

Sonar 5 was crashing on me on startup when I first installed it. This is on the same machine that ran Sonar 4,3,2,1 perfectly using the same devices. I have MidiOx installed and I have an Evolution controller. For some reason, when no midi input and no midi output was selected -- which was the default after I installed Sonar 5 -- Sonar 5 would crash. When I changed the midi input and output to be the Evolution controller, it started up perfectly and ran without any problems. I haven't taken the time to track this down, further. Don't know if that's helpful or not.

[pitchdrifter]

I did select a midi device during startup (it asked me to chose one), after i did that it crashed.. and I crashed the same when I chose 'no midi input/output for now' (to that effect). So I it supposedly can't be that particular problem.
I also tried with audio drivers.. makes no difference which it is it starts with.. crashes either way.

thanks for the input btw, highly apreciated in tracking down this glitch (next step will be bugging the fog out of cakewalk to fix it)

best

Markus

[pitchdrifter]

it's an antipiracy thingy maybe?

you are saying what, exactly?

[flex42]

have you tried changing the sample rate in your asio setup?

[Guckli]

If you're using a pc (as opposed to a laptop) see if you can move your card to a different slot...I believe I have heard that sometimes a soundcard right above or below a video card causes issues..I have no idea why but I've seen it work before...

Amen to that, and quite frankly the first pci slot from the agp should be filled with epoxy as soon as the motherboard is unpacked, since it shares the irq with the agp

[Stairsteps]

Ok I tried all of these things, renaming vstplugins folder, disabling all vst plugins in the vst adapter (project 5 installed this one so I wanted to make sure) etc. none of which helped.
Then I loaded an example project.. and Sonar actually loads fine, REALLY fast (compared to SX).. and works, too.

This is... weird.. to say the least

Ive been using Sonar for ever and know alot about its quirks and what not , Ive been thru every concevible situation that can ruin a session or cause a blue screen or as in your case not even load up except with an example project, yes Ive been there and Ive figured it out each and every time what the problem was.

Sonar 5's mandatory Vst scanner and adapter while functional is not as good as mabey the Fxpansion one is or even DirectXiser, thats what your problem is and its not a easy one to get around as I just bought Sonar 5 last week and didnt run into that exact problem but I suspect your problem to keep comeing back no matter how many clean installs you do or even if you remove your vsti folder!!

Its a .dll file that exists in your system somewhere mabey in your system32 folder that is a trace of a Vsti that you prob have installed thats probly causing your problem.

Ill repeat the Vst native support is a joke and is not implemented as well as third party adapters such as FXpansion V4.0 , however what I recomend is that you try this----->

Reinstall Sonar5, Make sure you erase all traces try using clean uninstall which is a program that you can try for free for 30 days, get it from download.com, next thing you want to do is i hope you have a seperate wrapper such as DirectXiser or FxPansion which is way better, ok now once you have Sonar 5 installed DONT OPEN IT YET , open your wrapper first and have it rescan all your plugins, which should be in your vst folder ok now the hard part, you will have to find a way to disable the Vsti scanner in Sonar5, I think it can be found in the WinCake folder im not sure how to disable it yet till I investagate it. However once you have it disabled and let a outside source scan you Vsti instead your problem should go away forever.

[pitchdrifter]

The wrapper actually did a fresh scan right after the sonar install. Also, there are no vstfx/i remnants anywhere.
And you can prevent the wrapper from adding/scanning vsti's by removing all vst folders from the wrapper's list of vst folders, then it has nothing to scan. I did that, too. Yet Sonar crashes when launched directly, but starts fine when I doubleclick a project.

Guckli, I don't have an agp slot. Thanks for the hint, though.


Markus

[Hink]

The wrapper actually did a fresh scan right after the sonar install. Also, there are no vstfx/i remnants anywhere.
And you can prevent the wrapper from adding/scanning vsti's by removing all vst folders from the wrapper's list of vst folders, then it has nothing to scan. I did that, too. Yet Sonar crashes when launched directly, but starts fine when I doubleclick a project.

Guckli, I don't have an agp slot. Thanks for the hint, though.


Markus

is your defuat pc soundcard the same as you are using it Sonar? Try disabling the default audio device

[sluggo]

I'm not sure, but it sounds like your computer doesn't like the default Sonar5 template. Open up a project, create a new blank project to your liking and save it as the template or startup, or whatever it's called. Now try and start up Sonar5 the "normal" way.

s.

[audiolife]

If you are using winxp, try turning off xp's Data Execution Prevention (DEP, read here

http://www.cakewalk.com/support/kb/kb2004216.asp

[pitchdrifter]

Tried excluding it from DEP, didn't fix the crash. Same for saving a new template over normal.cwt. When I launch Sonar the normal way it still crashes. Default audio device is disabled, windows has no way of producing system sounds.

thanks for the effort everyone. would be great if you could throw any other ideas you might have at me


Markus

[Hink]

any luck yet?

[pitchdrifter]

Same thing as usual... launches fine when I doubleclick a project file and crashes when I start it with the shortcut. Not a clue why.

[RapRogue]

If on XP, try starting up in safe mode.

[etherdesign]

How is safe mode going to help?