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
11:58am
Hi Monika,
"Inactive" state can cause unexpected results. There is nothing specifically in the module code to handle this state - it's handled at a higher level. This can result in the input buffer being passed to the output wire, or zeroes, or something else. If you wish to deactivate the module at run time to save CPU cycles, I recommend that you look at the ActivationMux and ActivationMute modules.
See:
ActivationMute - DSPC Dochub
ActivationMux - DSPC Dochub
Also see the example layouts which have more detailed info on how it works and how to use these modules.
"C:\DSP Concepts\AWE Designer 8.2025.3 Standard\Examples\Module_Usage\ActivationMuteExample1.awd"
"C:\DSP Concepts\AWE Designer 8.2025.3 Standard\Examples\Module_Usage\ActivationMuxExample1.awd"
Thanks,
Gary