An X1 Crash...

Hello all,

Just wondering if anyone else has experienced an X1 crash in the following way:

I have the track inspector on the left side of my screen and the browser on the right. All I was trying to do was click & drag a reverb plugin (Redline Reverb) across the screen into the FX bin of an audio track. I got about 3/4 the way across the screen when my finger slipped off the mouse and caused me to un-click the mouse in the blue area beside the FX bin. Immediatly I got the Windows "Sonar.exe has stopped working and needs to close" prompt. I rebooted, loaded up X1, and did it again. (on purpose this time)

I'm pretty suprised that something so simple can cause a crash, though I must admit this is the only problem X1 has given me so far.

Is anyone else able to cause a crash doing this? If so, it might be a good fix to add to X1b.

Probably should add a few system specs: Windows XP SP3, AMD Phenom quad core, M-Audio Profire 610, Sonar 8.5.3 and X1 32 bit installed.  

All the best,
Ryan

Yes.

It happens every time I try it. Though I've only tried the Redline reverb plugin and the Tracks classic compressor plugin. I suppose I could go through a bunch more plugins and see what others are affected, but I can't say it excites me to repeatedly crash my system on purpose....

Ryan

Thanks for the input. Must be something weird on my system then... However, you are using the 64 bit version on Windows 7. I wonder if anyone using 32 bit X1 on Windows XP SP3 can duplicate the crash? 

Just a thought.

RYan

I've got X1a on Windows XP Pro SP3 - all 32 bit.

No crashes when I try - however I don't have the plugs you are using. I just tried some Sonitus, and a few others.

ryannadon


Crap....
I was really hoping it wasn't just my rig, and that the fix would be easy. I don't really think it warrants a call to tech support, but it makes me wonder what else is going to cause a crash.
This is crazy considering I've been running 8.5.3 pretty much since it came out without a single crash. I have this sinking feeling that being an X1 "early adopter" may have been a mistake....

In any case, thanks for the input.

Ryan

Seems you are making too much out of this. You said yourself this was the "only" thing in X1 that gave you a problem, and that this wasn't part of a daily routine, you accidentally dropped it in the wrong spot! This should not affect your work flow at all! It's a minor bug - if it is a bug at all.

Experiencing the same issue here, what this ever resolved for you?
 
thanks
Rick

Running X1d here, I will verify if this is a plugin specific or across the board issue with different plugin manufacturers. Very frustrating.
 
 

(...)