Hi Team,
I’m working on a custom Audio Weaver module where the input is stereo (2 channels) and the output is configured as 6 channels. The active processing and bypass modes are working as expected, and mute also behaves correctly.
However, when I change the module runtime state to inactive, the output sometimes contains unexpected or garbage values/zero. I noticed that unlike process, bypass, and mute, there doesn’t appear to be a specific inactive function hook in the module structure.
Could you please clarify how the inactive state is expected to behave for custom modules? Should the framework automatically handle the output buffer, or is it recommended for the module developer to explicitly clear or manage the output buffer when inactive?
Thanks in advance for your guidance.
Best regards,
Monika V