Floe 2 vs. Floe 1

LMCS

I'm excited to hear about the upgrade to Floe; thank you for that.

I do have a question, though. Does it install as a separate instance if one already has Floe installed? Here's my concern:
-My workflow is, from within Ableton Live, to call up Floe, typically load a preset but then work on it until it's customized into something else.
-Upon recording with the resultant sound design, Abelton Live from that point on will always pull up whatever my customized Floe patch is, when that project is called up.

And this leads to me wondering, if (well, when) I upgrade to 2.0, will those established connections be broken?

I tried to be brief in explaining my question, but can give more detail if need be.

And thank you for all your efforts, they're much appreciated!

Sam FrozenPlain

Thank you for your comments - I'm very pleased you like it.

Floe v2 overwrites v1 - but its fully backwards compatible. Everything you can do in v1 works in v2 and everything sounds identical. You just have more features in v2. All your old Ableton projects will load up the same.

This is a key goal of Floe - backwards-compatibility. You can assume this will always be the case.

Something to mention though is our 'legacy parameters' system which you might encounter if you load up an old DAW project. This page describes it in full: https://floe.audio/docs/reference/legacy-parameters