Current 4A bindings use the dynapi mechanism introduced in appfw binder after EE to create APIs and audio controls/streams dynamically.

At the same time, for FF, the binder now exposes APIv3 which has the same functionnlities than Dynapi, but not the same semantics.

The 4A stack has been integrated quite directly from EE to FF.rc1, without any change on dynapi calls. So as a workaround for FF.rc1, we introduced the option -DINCLUDE_LEGACY_BINDING_VDYN=ON in the binder recipe. But that should disappear.