Reply to thread

Message: [QUOTE="Bombastus, post: 92319, member: 2178"] Flite V2 keeps existing presets and host-saved plug-in state backward compatible while migrating legacy oscillator, LFO, and filter mappings into the new modulation system. Wavea also says those migrations preserve the intended Macro and Modulator selections, which matters when an older patch depends on movement rather than a static oscillator setting. A major synth update can install perfectly and still damage a working project if saved state comes back differently. [B][URL='https://goldmidi.com/community/threads/wavea-brought-flite-v2-with-200-new-features.77655/']Flite V2's backward-compatible update[/URL][/B] matters because V2 changes modulation assignment, filters, oscillators, sequencing, effects, and other internal behavior without treating every V1 sound as disposable. Presets and DAW sessions are separate compatibility problems. A preset is a saved sound you deliberately load, while host-saved state is the plug-in condition stored inside a project by the DAW. Flite V2 addresses both, so compatibility is not limited to seeing old preset names in a browser. [HEADING=2]Backward compatibility means more than preset loading[/HEADING] Software can read an old file yet still behave differently after loading it. [B][URL='https://arxiv.org/abs/1503.07235']A formal model of backward-compatible software updates[/URL][/B] frames compatibility around preserving acceptable behavior when one side of a system changes, and the surrounding environment does not. Audio plug-ins face a practical version of the same problem because the DAW project, automation, saved parameters, and plug-in version all meet when a session reopens. For Flite, Wavea makes two separate promises. Existing presets remain backward compatible, and host-saved plug-in state does too. The second claim is particularly useful for unfinished songs because producers do not always save every customized instance as a named preset before closing a project. Host state can contain the exact condition of a sound at the moment the DAW saved it. Macro positions, parameter values, modulation assignments, loaded material, and other plug-in settings may be part of what the host recalls, depending on how the plug-in stores its state. Preset compatibility alone would not necessarily protect a heavily edited instance living only inside a song. Backward compatibility does not require V2 to expose every old control in the same place. New controls and interface changes can coexist with older saved data as long as the important musical behavior survives the move. For an existing production, recall matters more than whether the editor looks familiar. [HEADING=2]Legacy modulation mappings are migrated deliberately[/HEADING] The modulation overhaul makes migration harder than simply matching parameter names. Flite V2 introduces a bidirectional Macro and Modulator assignment workflow with visible ranges, while older sounds were created under the previous assignment system. Wavea says legacy oscillator, LFO, and filter mappings migrate without changing their intended Macro or Modulator selections. This detail is easy to miss in launch coverage, yet it is more important than a generic statement about preset support. A bass patch may rely on a macro opening a filter while an LFO moves oscillator pitch by a narrow amount. Loading the patch without preserving those relationships could leave all the right components present while the sound responds incorrectly. Visible assignment ranges should make those migrated relationships easier to inspect after opening an older sound. You can see where modulation is attached and how far it travels instead of assuming the migration worked. If a favorite patch matters to a release or live set, checking those ranges is faster than rebuilding the modulation from memory. Older mappings also meet new destination possibilities in V2. The update adds filter modes, expanded oscillator choices, evolving LFO behavior, deeper FM controls, and broader automation support, but backward compatibility does not mean old presets automatically adopt those additions. Existing sounds can remain intact while new controls stay available for deliberate edits. [HEADING=2]Host-saved state protects projects beyond the preset browser[/HEADING] A DAW session often contains versions of sounds that never became presets. You might load a factory patch, automate several controls, alter a macro range, change an effect, and save the song without ever naming the result. Backward-compatible host state is what gives that kind of instance a path into V2. Wavea also lists stability work around editor reopening, duplicate embedded samples, and assignment handling. Those fixes sit beside the compatibility changes rather than the headline synthesis features, but they matter when an older project contains several Flite instances and embedded material. Reliable recall is part of migration, not unrelated housekeeping. Do not update the only copy of an important session. Keep the original project version and render critical parts before changing a production machine, especially when client work or an unfinished mix depends on exact recall. A saved audio reference gives you something concrete to compare if a patch sounds different after reopening. Once V2 is installed, reopen representative older projects before converting an entire archive. Check patches with heavy macro movement, LFO assignments, filter modulation, automation, and embedded samples first because those stress more of the migration path than a static preset. A clean recall there tells you more than scrolling through the factory browser and hearing familiar names. [/QUOTE]

Name