Warbler update problem

[thedeadsea]

Hi,

I've finally gotten round to updating my AU of Warbler from 1.0.0 to 1.1.1 and now find that Ableton Live won't recognise it in old sessions where I've used Warbler 1.0.0 (which is basically every project I've ever worked on!). Has anyone come across this problem and/or a remedy to make Live see the new version as being the same plugin as the old one?
I'm on a mac running 10.6.6 and Live 8.2

Cheers.

[os]

This was caused by Warbler 1.1.0 becoming a 'MIDI controlled effect' rather than a plain 'effect' which curiously are distinct types of plug-ins in the world of AUs.

There's no way around that that I can think of, other than saving the presets with Warbler v1 loaded and then loading the presets back on to Warbler v1.1.1.

[thedeadsea]

Thanks for the reply but dang... that's a bummer.

Is there a way of having them both running at the same time- I only ask because I'm talking about 50 different projects where I've used unique settings for warbler!

This was caused by Warbler 1.1.0 becoming a 'MIDI controlled effect' rather than a plain 'effect' which curiously are distinct types of plug-ins in the world of AUs.

There's no way around that that I can think of, other than saving the presets with Warbler v1 loaded and then loading the presets back on to Warbler v1.1.1.

[os]

You could try renaming one of the plug-ins. In theory, the actual file name (xxx.component) doesn't affect the plug-in's identity.

[thedeadsea]

Cool, cheers I'll give it a whirl!

You could try renaming one of the plug-ins. In theory, the actual file name (xxx.component) doesn't affect the plug-in's identity.