X2 + Alloy 2 crash

Does it also happen on New projects or just the project you describe above? Might want to try using it in a new project created in X2a just to see if the crashes still occur.

Also, did you do the reset and re-scan vst's as described in the readme or install notes?

No guarantees but at least it would be another data point.

Kind regards,
Rick

It happened on new X2 project admittedly before X2a.
Yes I did reset and re-scan the VST's.

The crashes occur in the 32bit version of Sonar as well - does this still use Bitbridge? 

Off memory when installing Alloy 2 it asked for two VST folders i.e. one for 32bit and one for 64bit Vsts. I can see the Alloy DLL's in both:
- C:\Program Files\Cakewalk\Vstplugins
- C:\Program Files (x86)\Cakewalk\Vstplugins

I could try disabling/enabling the DirectX/Vst versions of Alloy 2.


Any other ideas?

tonydude - have you notified iZotope as well?  Do you have another machine or DAW (software) you can test with - just to see if it might be system related?  I assume you are loading Alloy from the vstplugins sub-menu rather than the Directx version via Audio FX -> iZotope -> Alloy 2 - correct?  

I created a simple 1 stereo track project with Alloy 2 (2.01) in the FX bin and I can re-launch and re-open the project without problems.  I cloned the track several times and repeated the process - no issues.

I created the original project in X2 then I upgraded to X2a, opened the project and cloned one of the tracks with Alloy; saved, then re-launched and re-opened again without an issue.  I tried the test with Alloy open (minimized) and that didn't make a difference.  I used some Pro Channel modules on tracks and the Master bus - then I really got dangerous and loaded iZotope Trash 2 in a track FX bin that has Alloy 2 in it, and that too was uneventful.  My last stab at messing things up was to put Guitar Rig 5 in the Master bus, and a 32-bit Voxengo plug on one of the tracks - still no issues.  Sorry, I don't have Ozone on this machine - surely that would have done it.  The project is 44.1/24-bit - if that matters.

I did this test on my laptop; an Intel i3 M 370 based machine with 8GB of RAM, Win 7 64-bit Home Premium, and an Echo Audio Indigio IOx audio interface.  I haven't installed X2 on my main DAW yet - I'm not quite ready to take that leap of faith.

It's being loaded via Audio FX -> iZotope -> Alloy 2 on each track and didn't use Clone Track.

It's the same physical PC albeit I have performed a clean install of Windows 8 (previously was Win7).

There is another PC downstairs, it's the girlfriends Win7 Media Centre box... so will have to wait until Coronation Street isn't on(!)


I've created a 'test crash' project, so far:
- created 4x empty tracks added a fresh instance of Alloy 2 to each
Test Crash Project re-opened OK - puzzling so far!

What about the settings of my Quad Capture? I have Audio Buffer set to 5 and a Buffer Size of 128 samples. Am recording in 44.4 KHz and 24bit.

Haven't raise a support ticket with iZotope yet (I will) - but Alloy 2 has sent them crash information.

Hope I can get some more information together - dump files are a lot of information to trawl through and time consuming for support. 

Alloy 2 gets some amazing results... until I close and re-open the project. :-( I've been creating templates to try and retain my work.

Cheers for the help.

It might be hardware... Windows is now failing to boot on that drive.
Doing another re-install of all my music apps, will see how it goes. Thank god for the holiday period(!)

I think it was hardware.

Different hard drive for the O/S,  same Sonar project (with 4x track instances of Alloy)... no crash. 

Tried half a dozen times and all fine.