Cabinet Devices in MGuitarArchitect vs MXXX
-
- KVRist
- 61 posts since 11 Jan, 2020
In MGuitarArchitect I can see Devices (i.e. the stuff with the nice custom GUI) when adding the "Cabinet" plugin to the signal chain.
However when I load "Cabinet" in MXXX, I can't see the Devices, but only the Edit mode.
I'm wondering, is that a design decision or an inadvertent oversight?
p.s. I have licenses for all of the Melda Products, so I assume that's not a differentiating factor.
I'm using version 16.10 on Win10 22H2
However when I load "Cabinet" in MXXX, I can't see the Devices, but only the Edit mode.
I'm wondering, is that a design decision or an inadvertent oversight?
p.s. I have licenses for all of the Melda Products, so I assume that's not a differentiating factor.
I'm using version 16.10 on Win10 22H2
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
That's intentional - MGA contains the "extended" versions, these are more powerful and CPU/memory heavy. MXXX is designed for making complex stuff efficiently, so for these there are the "Ex" versions (MDynamics and MDynamicsEx). I suppose there is no MCabinetEx, that could be added I assume.
-
- KVRist
- Topic Starter
- 61 posts since 11 Jan, 2020
Ahh - thanks for clarifying that!
A CabinetEx would pair nicely with the already existing TurboAmpEx to make it a bit easier to work in MXXX.
Obviously this isn't strictly required to build a combo-amp or more in MXXX (with potential custom Device GUI), it might just be a nice-to-have, since the Cabinet Devices offer such a friendly starting point to learning the Cabinet internals, analogous to TurboAmpEx existing along with TurboAmp.
A CabinetEx would pair nicely with the already existing TurboAmpEx to make it a bit easier to work in MXXX.
Obviously this isn't strictly required to build a combo-amp or more in MXXX (with potential custom Device GUI), it might just be a nice-to-have, since the Cabinet Devices offer such a friendly starting point to learning the Cabinet internals, analogous to TurboAmpEx existing along with TurboAmp.
-
- KVRist
- 79 posts since 29 May, 2005
Yeah? Well whilst you're at it, how about a MDynamicEqEx just to start with?? Even better , a little switch on every MXXX plugin enabling the Ex functionality as the user sees fit, not the management..
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
No systemk changes, sorry. But I'll think about the dynamiceq
-
- KVRist
- 79 posts since 29 May, 2005
Thanks for giving it consideration.
Also, will we see a MStompbox ?
As far as I know I need to wrap it in MXXX or MGuitarArchitect if I want to use it.
I assume that comes with a substantial increase in CPU/Memory usage, is this correct?
Thanks.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
It should eb there in the next version.
About MStompBox - no I'm afraid. We eventually decidede to keep it just for MGA. But no relevant increase in CPU/mem usage is expected.
About MStompBox - no I'm afraid. We eventually decidede to keep it just for MGA. But no relevant increase in CPU/mem usage is expected.
