I'm a fairly new user of X1d (but have used ProAudio9 and SHS7 for years) and have been trying out effects, mainly reverb, to see what they do.  I start with a simple project with a 3-4 midi tracks routed to TTS-1 routed to a busA routed to the main output.  I put an effect into the effects bin of busA and then try various presets.  Then I'll delete the effect and try another one.  After doing this a few times X1d will invariably crash.  Since I'm just testing nothing is lost but under different circumstances something could be lost by the crash.  I'm using only plugins distributed along with X1d.

Is this just to be expected?  I don't recall SHS7 doing that.  And it was just about impossible to ever get PA9 to crash.

Curiously,
Larry

shouldn't be happening.  which FX are you using?  you said "reverb" but can you give us more specifics?  and does it crash every time you get to a certain number of changes or a certain FX plugin? 

and what exactly do you mean by "crash"?  crash means different things.  does sonar throw up an error message?  if so, what is it?  does it just lock up?  does it just "go away"?  how does it crash?

The FXs are Cakewalk Studioverb2 and Sonitus:fx Reverb.
I believe it has happened every time (at least 3 or 4 times) I have done a lot of testing of the reverb presets.  I don't know how long it takes since I haven't really done controlled testing.

By crash I mean I get the windows box that says something like "Sonar has experienced an error and will now exit - want to send info to Microsoft?".  I don't send info.  After dismissing the Windows error message Sonar says something about a proper shutdown hasn't happened and do I want Sonar to try and save stuff.  I don't since I'm just testing.   Then Sonar is gone.

Here's some entries from the Windows Event Log:

Faulting application sonarstd.exe, version 18.0.5.534, faulting module sonarstd.exe, version 18.0.5.534, fault address 0x0031c28f.


and

Faulting application sonarstd.exe, version 18.0.5.534, faulting module unknown, version 0.0.0.0, fault address 0x0c5d0508.


and

Faulting application sonarstd.exe, version 18.0.5.534, faulting module sonarstd.exe, version 18.0.5.534, fault address 0x0031c28f.


and

Faulting application sonarstd.exe, version 18.0.0.185, faulting module sonarstd.exe, version 18.0.0.185, fault address 0x007efcfc.


--Larry

ok, and I should have asked this before, but is this a win7 64bit machine?  if not, what is it?

Check out my signature - it's a Win XP SP3 32bit machine built in Oct 2009.
--Larry

sorry.  I looked thru your sig and missed the OS!!

at any time did you save settings in one of those FX?  you said you were testing out presets, so you may not have been changing parameters past presets.  but if you were, were you saving those settings?

I am not up on my Intel specs but does the Intel Core 2 Duo E7500 meet the minimum specs for X1? The SONAR X1 spec sheet recommends a minimum of an Intel Core 2 Duo E8200. Could this be a case of pushing the hardware too much?

edit: reformatted to see if FF 15 works properly....it doesn't

Beagle,  I have not specified any "new" presets using X1d however the Sonituf:fx Reverb has one saved preset which I had created under SHS7.  It was a small mod of a standard preset.  I was glad to see it show up under X1d since I have used it in many projects, most of which were created under SHS7 (as .cwp files).

In some of my testing I might have made some experimental changes to standard presets but did not save them.

scook,  relating performance and intel processor name is likely one of the mysteries of the universe.  The E7500 has processors running somewhat faster (2.93GHz) than the E8200 (2.66GHz).  But the E8200 has a larger L2 cache and faster FSB.  In any case, I don't have any problems running much more demanding projects than the one I'm testing with.  I often have multiple midi tracks (not much of a load) and 2-3 audio tracks with multiple effects and 2-3 soft synths.

--Larry

that's an odd one, then, Larry. 

the only other thing that I can think of would be the versions of those plugins.  are you using the latest version of those plugins or are you using the versions that came with HS7?

Hmmmmm.....   I wonder how'd I know?  The history is that I had PA9 and then installed SHS7 XL along side it and then much later installed X1d along side the other two.  So all three are installed and each one seems to work fine.  The C:\Program Files\Cakewalk folder has separate folders for each application.  PA9 seems to be pretty much self contained but SHS7 and X1d use the shared folders for DXi, MIDI Plugins, Plugins, VSTplugins and who knows what else.

Who knows the plugin versions associated with X1d vs. SHS7 ?

I did a complete install of X1d and presumably it updated any things that needed it.

I could go back to an old backup and retrieve the Shared Plugins folder and compare it to my current folder to see what, if anything is new?


--Larry