Hi,
So currently from previous posts you can't yet save a subsystem separately and use it in another design:
https://dspconcepts.com/forums/audio-weaver-general/631-managing-subsystems
i.e. you have open the old design and copy and paste that subsystem in your new design.
I was also wondering can you combine a subsystem made from say, just modules from the AWE standard pack with a custom module and put that in it's own separate subsystem ? Do you need the Pro version of AWE to be able to do this ?
Thanks.
9:32am
Hello David,
Just so I understand you correctly, you have 1 subsystem containing Standard Modules and a Custom Module, and you want to know if you can take that 1 subsystem and nest that in another subsystem? This is possible. You need Audio Weaver Pro to create the Custom Module, but you do not need it to use the Custom Module. As long as your machine has the Custom Module on it, you will be able to use it. Hope that helps.
Thanks,
Kevin
9:56am
Yeah, that's sort of what I mean.
Subsystem 1 = made up of several standard modules
Subsystem 2 = Subsystem 1 + custom module.
And is it still the case that I can't currently save Subsystem 2 as separate module to be used in other projects (unless I copy from current design into a new design) ?
10:11am
Hi David,
Yes that is possible. You can theoretically nest infinitely many Subsystems. Subsystems are actually a graphical tool, and they themselves don't add any extra overhead to your design. It may not be necessary, but I've emailed you a .pdf with some more information about Subsystems.
Unfortunately you still cannot save a Subsystem as a module to be used in other projects by default (copy and paste does work). There is a way to compile your Subsystem into a module though, which would allow what you are describing. This involves more work and probably a higher level discussion between us. If you're interested we can schedule something.
Thanks,
Kevin
2:10pm
ok thanks for that update. Also, regarding custom modules in section 4.2 of the Module Developers Guide you examine the class structure of the biquad_module.m and show the (I assume) auto-generated C code in ModBiquad.c. Unfortunately, I can't see inside the biquad_module.m as it's been matlab encrypted to a .p file. Is there any chance you have examples of what's in the biquad_module.m and also the Inner files for this module, and/or maybe even the fir_module.
I realise there are examples in the AWEModules\Source\Examples folder, but maybe some more examples which do a bit more "math" would help my understanding when writing my own. Thanks.
1:56pm
Hi David,
Since the biquad_module.m and fir_module.m contain our processing functions, unfortunately we will not be able to share any further examples of inner module workings.
Thanks,
Kevin