Skip to content

Milestone FOA ported to use AmbiX instead of FuMa

Jump to bottom
Trond Lossius edited this page Nov 3, 2021 · 25 revisions

Content

 

 

Naming conventions

As plugins are updated, their names need to change so that old and new versions are not mixed up in Reaper projects. The approach to this will be similar to how Blue Ripple did the same transition:

  • Old version has names starting with ATK FOA (something)
  • New version has names starting with ATK O1A (something)

 

 

Code refactoring

Make all atk library code use namespace pseudo-objects as outlined here, similar to how this is done in the cookdsp library

 

 

State that plugin uses AmbiX

For plugins with GUIs this can be part of the GUI.

For plugins without GUIs I need to consider how best to do this. Maybe all plugins should have GUIs, even if they are not really used for anything? Combined with the below point, there are strong arguments for always providing GUIs.

Is this to behave differently when the GUI window is large or small (small as when embedded in Track or Mixer Panels?)

 

Clone this wiki locally