KVR Audio

pitchdrifter · Post by **pitchdrifter** » Thu Oct 06, 2005 2:24 pm

Has anyone had this?
Sonar launches, displays the tip of the day, then after that it crashes with a 'SONARPDR.EXE has encountered a problem and needs to close' message. Every time.

any ideas?

Markus

Hink · Post by **Hink** » Thu Oct 06, 2005 2:26 pm

Not happened to me, but often crashes like that are hardware related...

pitchdrifter · Post by **pitchdrifter** » Thu Oct 06, 2005 2:28 pm

Like what? Sonar having an aversion against a sound card or dsp card?

Hink · Post by **Hink** » Thu Oct 06, 2005 2:33 pm

xRAVENx wrote:Like what? Sonar having an aversion against a sound card or dsp card?

could be, I had problems with midiman usb interfaces giving me bsod, it was until I got a new computer that shoed me it was the midiman...I also had troubles with my PCR50 getting lost, turned out it in that case the PCR50 liked to be powered with it's own power supply and not the usb port.

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...

pitchdrifter · Post by **pitchdrifter** » Thu Oct 06, 2005 2:40 pm

card to a different slot - no. thanks for the advice though.
And the issues aren't system problems, maybe they are system related like sonar not supporting particular hardware (although poco and fireface should be very common :S). System itself runs like a charm, though. Nothing shared, no conflicts, even SX runs without crashes (except when I install something pace, then the machine reboots about 10-15 times a day).
Also the midisport 8x8 midi interface I used to use is currently on the road to be RMA-ed by m-audio.. so it can't be that either (and there is no driver for it installed either).

Any other ideas how to get sonar to work other than by waiting for a patch?

thanks

Markus

Stupid American Pig · Post by **Stupid American Pig** » Thu Oct 06, 2005 2:46 pm

Have you ever been able to run the app? have you installed any new Vsts since it ran last?

pitchdrifter · Post by **pitchdrifter** » Thu Oct 06, 2005 3:03 pm

It scanned for vstis on the first launch, then brought up the authorisation screen, I authorized it, then the tip of the day shows up, I click ok, then it shows just the Sonar gui for a split second and crashes.
From then on, each time I launch Sonar it crashes after the tip of the day like it did the very first time. The sonar midi i/o icon in the taskbar is stuck after each crash. If I try re-launching Sonar without rebooting first, it crashes before the tip of the day appears. If I do reboot first (because theres no traces of sonar left in the taskmanager which could be shut down to kill that icon) it shows the tip of the day on being launched, and crashes after I clicked ok.. putting the midi i/o icon into the taskbar again.

edit:
Oh and right before the crash the 2 lamps on that icon light up once each, goes pretty fast.
The midi i/o device selected on the first sonar launch was the fireface midi i/o (which works in SX, eXT, Project 5)

RapRogue · Post by **RapRogue** » Thu Oct 06, 2005 3:16 pm

If you got the time and the clone software, make an
image of current setup and then start from scratch.
Then install the application right after OS updates
GFX drivers and SOUND drivers.

If it works here then just add any software in
Increments, I had a problem in XT which was due to
SFP having certain registry malfunctions; which all
other hosts ignored.

This is not a Sonar specific solution, as it works
overall, nor is it quick solution either.

pitchdrifter · Post by **pitchdrifter** » Thu Oct 06, 2005 3:21 pm

Thanks but I'm not going for a 'format and reinstall' type of solution. The setup is fresh, 2 weeks old in fact, and works very well, no flakyness, no crashes. Also it's a dedicated DAW, which is being used for nothing else.

Thanks for the effort though, I do appreciate it.

best

Markus
P.S. I renamed TTSSEQ.INI so it'd not know what midi device to use - launching sonar after that asks me to chose a midi device again, I went with 'go with no midi device for now', after which sonar still crashed at the same point. So it can't be the fireface midi driver either.

bluemuser · Post by **bluemuser** » Thu Oct 06, 2005 3:27 pm

I had a similiar sounding problem. Sonar 5 would crash if I opened SONARPDR.EXE directly.
What I did that worked around it was to open up a previously saved Sonar 4 project.
If you don't have one then try directly opening up a demo project or a template.
This works for me.

RapRogue · Post by **RapRogue** » Thu Oct 06, 2005 3:31 pm

Np, its not the first solution, but it can tell you if it will even work on your system within 30 minutes.

Spyda KB · Post by **Spyda KB** » Thu Oct 06, 2005 3:38 pm

I had this same problem before a long time ago with Cakewalk Pro Audio 9...turned out to be bad memory. All other apps were fine, but only CPA 9 was crashing the same way you described. Getting new and better quality RAM fixed the problem.

A last year Sonar 4 was crashing on me and I was getting BSOD. Turned out my Akai MPD-16 driver was not installed properly.

So you may either want to completly uninstall and reinstall your midi drivers or check for defective RAM.

Otherwise....

Have your tried deleting your AUD.INI file?

Have you tried starting Sonar's plugin manager and disabling all VSTs and then start Sonar?

Have you tried an unistall and reinstall of Sonar?

- KB

jplanet · Post by **jplanet** » Thu Oct 06, 2005 3:38 pm

Crashes on startup also tend to be VST plugin conflicts. try renaming your VST plugs folder, startup, and see what happens.

pitchdrifter · Post by **pitchdrifter** » Thu Oct 06, 2005 4:08 pm

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

snooky · Post by **snooky** » Thu Oct 06, 2005 4:32 pm

it's an antipiracy thingy maybe?

Sonar 5 crash on launch