Cannot Open Live Set

[Danb1]

Hi there.

I have lost the ability to open a particular Set on Live 8.0.4.

During the session I saved and had a dialogue box saying there was an error (sorry, I cannot remember the actual content of the error message) relating to Voxengo Chorus VST plugin. Unfortunately I did not try to undo and re-save. But once I finished the session and closed the set, I have not been able to open it again. The set loads up the various instruments, but at the end of each load "Live has to close immediately".
I have tried loading the set with the Voxengo plug-in removed and restoring the system to an earlier time, to no avail.

Is there anything I can do. I've never lost a song in my entire production career, so this is a worry.

I use a Dual core XP with 4 gig ram on a 3gb switch.

thanks in advance.
Dan

[jok]

Hi Dan,

try this:
- open preferences/ FILE/FOLDER.
- deactivate your custom VST folder
- load the set
- remove the problematic plug-in
- save the set
- reactivate VST plug-ins
- reload the set

Best,
Jörg

[Danb1]

Yipee!
That worked. Many thanks for the tip.
d

[Danb1]

OK I spoke to soon and this is getting weirder by the minute.

When I run the diactivate VST's and then remove the plug-in, as described above.... reactivate and open the track... everything seems ok. At that point I re-save the Set under a new name. When I close the set and open it again the same "Error Live must close immediately" window comes up at the end of loading.
I've repeated the process twice now and it's very confusing.
The original offending Voxengo Plug-in is long gone.

Any ideas. Happened to anybody before?

[Danb1]

Just to clarify Jorg, your process works, but the problem returns when I save, close and re-open the set.

d

[jok]

Hi Danb1,

sounds like the culprit might be another plug-in in the set, did you try to remove other/all 3rd party plug-ins to narrow down the problem? Also: how big is the .als file?

Best,
Jörg

[Danb1]

The als file is 2997kb.

I deactivated the VST folder as you suggested, but it's hard to tell which of the many plugins it might be. The original warning (that I foolishly ignored) was for the Voxengo Chorus, which is now gone.
Strange that it all loads fine after the re-scan, but then won't open after closing. If it was one of the VST's how come they all work ok in the first instance?

[jok]

Hi Dan1,

the fact that the set opens up fine when the VST folder is deactivated suggests that there´s still a conflict with one or more plug-ins in use. If you´re not sure, please send the set to [email protected]

Best,
Jörg

[Danb1]

Jorg, The set opens fine AFTER the VST's re-activated. But not after close and re-open.
I'll send the set on and see if they can identify the rogue plug-in.

Thanks