I would like to make a custom module that is an awe_subsystem. Is there an example of how to compile a subsystem into a custom module that can be used by designer?
I've attached an example of a subsystem that implements a LookAHeadLimiter - there is a .m and .c file included here. You can also find the full example in the installations of the AWE 6 Designers in the Modules/Examples folder (6.18.02 for example: https://dspconcepts.com/legacy-downloads).
While in Design Mode, if you right-click your subsystem module on the Audio Weaver Designer canvas, at the bottom of the drop down menu you will see "Permissions". If you hover your mouse over "Permissions", you will see an option to "Allow Navigation". An unlocked subsystem will have the "Allow Navigation" parameter checked, and subsystems are by default, unlocked. If you left-click/un-check "Allow Navigation", a 'Lock Subsystem' window will pop up, where you can enter and re-enter a password for the corresponding subsystem.
Once you've locked your subsystem, the subsystem module will be shaded yellow as indication, and no one will not be able to double click to view the inner contents of the subsystem without entering the set password.
To unlock the subsystem, follow the same steps listed above, by right-clicking and navigating to "Permissions" > "Allow Navigation". An 'Unlock Subsystem' window will pop up, prompting you to enter the password to unlock the subsystem.
If you have any other questions, please feel free to ask.
Thanks for the detailed information. I could able to set the password for the Default subsystem which is already available, but I have created a custom subsystem for which I couldn't able to Navigate In as well set the password for Inspector.
Is there any MATLAB commands to add this Navigate In option to the custom modules?
Is there any possibility to set password for Tuning panel(Inspector) itself(Not the Navigation window)?
Sorry, currently there is no way to add this option in custom modules, nor set a password for the inspector. A viable work around could be placing your custom module inside of a standard subsystem, and then locking that subsystem. I know it's not a perfect solution but it will work for what you are describing.
Thanks for the clarification. I have one more query
By using the standard subsystem, If I create a signal flow which contains different audio blocks like Volume control, Equalizers, Look up tables..etc. , How can I have different/seperate control Inputs for all these blocks Outside the subsystem such that I can control them without Navigate In?
You could control your audio modules inside of a subsystem "remotely" or from outside of the subsystem, by using a module called ParamSet (ParamGet also). ParamSet will turn any module into a "Controllable" module. It will write directly into another module's instance variable. You specify the module and variable you want to control in the ParamSet Argument Properties (Mod.Var).
3:43pm
Hi Darrel,
I've attached an example of a subsystem that implements a LookAHeadLimiter - there is a .m and .c file included here. You can also find the full example in the installations of the AWE 6 Designers in the Modules/Examples folder (6.18.02 for example: https://dspconcepts.com/legacy-downloads).
Let us know if you have any specific questions about how the custom subsystems work.
-Axel
1:26pm
How can we lock the Inspector(Tuning window) of a Custom Subsystem with a password?
4:32pm
Hello Prabhakar,
While in Design Mode, if you right-click your subsystem module on the Audio Weaver Designer canvas, at the bottom of the drop down menu you will see "Permissions". If you hover your mouse over "Permissions", you will see an option to "Allow Navigation". An unlocked subsystem will have the "Allow Navigation" parameter checked, and subsystems are by default, unlocked. If you left-click/un-check "Allow Navigation", a 'Lock Subsystem' window will pop up, where you can enter and re-enter a password for the corresponding subsystem.
Once you've locked your subsystem, the subsystem module will be shaded yellow as indication, and no one will not be able to double click to view the inner contents of the subsystem without entering the set password.
To unlock the subsystem, follow the same steps listed above, by right-clicking and navigating to "Permissions" > "Allow Navigation". An 'Unlock Subsystem' window will pop up, prompting you to enter the password to unlock the subsystem.
If you have any other questions, please feel free to ask.
Thanks,
Kevin
1:05am
Hello Kevin,
Thanks for the detailed information. I could able to set the password for the Default subsystem which is already available, but I have created a custom subsystem for which I couldn't able to Navigate In as well set the password for Inspector.
Is there any MATLAB commands to add this Navigate In option to the custom modules?
Is there any possibility to set password for Tuning panel(Inspector) itself(Not the Navigation window)?
Thanks & BR,
Prabhakar.D
7:15pm
Hi Prabhakar,
Sorry, currently there is no way to add this option in custom modules, nor set a password for the inspector. A viable work around could be placing your custom module inside of a standard subsystem, and then locking that subsystem. I know it's not a perfect solution but it will work for what you are describing.
Thanks,
Kevin
9:51am
Hello Kevin,
Thanks for the clarification. I have one more query
By using the standard subsystem, If I create a signal flow which contains different audio blocks like Volume control, Equalizers, Look up tables..etc. , How can I have different/seperate control Inputs for all these blocks Outside the subsystem such that I can control them without Navigate In?
Thanks & BR,
Prabhakar.D
3:00pm
Hi Prabhakar,
You could control your audio modules inside of a subsystem "remotely" or from outside of the subsystem, by using a module called ParamSet (ParamGet also). ParamSet will turn any module into a "Controllable" module. It will write directly into another module's instance variable. You specify the module and variable you want to control in the ParamSet Argument Properties (Mod.Var).
For additional information, you can refer to pages 92 and 104 of the Audio Weaver Module User Guide: https://dspconcepts.com/sites/default/files/audio-weaver-module-users-guide.pdf
Thanks,
Kevin