Problem using MXXX within MSF

[craggvalehouse]

wrong info!

[craggvalehouse]

Wrong info..

[David]

"Houston…"

[muntuns]

I received another email from Luke when I asked for clarification.

"You can use plugin modules inside of MSoundFactory because they are included there and used for the specific instrument purposes.
But you can not use the MXXX as a standalone plugin out of MSF if you do not own it.
But if you own the MXXX, you can use it as a specific effect, specific fx plugin, in your plugin's chain, which includes modules almost all of our plugins.
But it is still a plugin. You can not use these modules as standalone/individual plugins as separate plugins."

I can't help but feel there's a small amount of a language barrier. I'm not sure what point he is making exactly, and I was very clear about MXXX being used inside MSF, never as a standalone plugin.

[muntuns]

But for now I am satisfied that I can seemingly use MXXX1 with no issues. All I really want from it is to mess around with the myriad of presets to warp my instruments in strange ways. It was just convenient that MXXX had a bunch of presets for complex FX whereas MSF did not have as many.

[WasteLand]

But for now I am satisfied that I can seemingly use MXXX1 with no issues. All I really want from it is to mess around with the myriad of presets to warp my instruments in strange ways. It was just convenient that MXXX had a bunch of presets for complex FX whereas MSF did not have as many.

it must work, me thinks, it worked before, so is it a bug? i didn't do a de-install, perhaps it is related if you also own MXXXCore. so my: question do own MXXXCore?

and MXXX1 works, without problems.

if i remember correctly; 14.05 was the first version that showed what modules you didn't own, in the list of MXXXCore. perhaps that backfired?

[David]

BUMP! I think we need some "official" explanation of why MXXX is STILL showing error messages about not owning FX so they'll be run in demo mode and with noise bursts when MXXX is used inside MSF.

MXXX 1 is NOT showing similar messages, so we can still access it, but WHY the difference? I'm now having to go back into old devices and replace MXXX with MXXX 1, and not always able to get similar results because of settings I changed in MXXX, and now can't save for use in MXXX 1.

[GuiB]

Hi, just wanted to know as well... actually I tested MSoundFactory and everything worked and was active when I tested it. I found MSoundFactory as a very great instrument for sound design with all the effects and having MXXX inside, so I went for it and bought a licence. However, now after activating it, I don't have access to all effects inside MXXX so this is a little let down after purchasing it since I wanted to use it to create some custom "sub-modules" that could be added easily into different MSoundFactory presets and was under the impression that everything is freely accessible from inside MSoundFactory since anything could be used to build customs presets/instruments that could be sold by a third party and used by any MSoundFactory versions. So does this mean that third parties can't use MXXX inside MSoundFactory or that they need to list the used effects so a customer can verify that he has bought all the effects?

At least MXXX1 also works on my side (trial version and also from my activated version), so I hope MXXX is simply a bug that will be fixed on the next release!

[David]

Since posting above, it occurred to me that if the MXXX in MSF (as opposed to MXXX 1) is in fact Multi-Band, while MXXX 1 is not (as someone suggested earlier), then maybe this is an intentional way to allow those who own the full version to use it in MSF, while also allowing those that don't own it, to at least have all the same processing modules and access to presets, just without the MB aspect…?

But enough with the guessing; let's PLEASE have some official explanation, may we not?

[GuiB]

Since posting above, it occurred to me that if the MXXX in MSF (as opposed to MXXX 1) is in fact Multi-Band, while MXXX 1 is not (as someone suggested earlier), then maybe this is an intentional way to allow those who own the full version to use it in MSF, while also allowing those that don't own it, to at least have all the same processing modules and access to presets, just without the MB aspect…?

But enough with the guessing; let's PLEASE have some official explanation, may we not?

I thought about it as well, but why not allowing the multiband version of MXXX but allowing it for every other modules (ex: Dynamics->DynamicsMB; Comb->CombMB; Autopan->AutopanMB; Chorus->ChorusMB...) ?

So, I'm also waiting for an official explanation (@MeldaProduction)

[Smapti]

MXXX1 contains a band splitter that is the same as the MXXX band splitter, and if you put it on the input you get essentially the same result as MXXX. Also, MXXX1 contains MXXX as a module -- has anyone tried using that? Although these are workarounds, they could be sufficient for most purposes. I own MXXX, but because I like using the band splitter, I actually use MXXX1 more frequently than MXXX.

[David]

Also, MXXX1 contains MXXX as a module -- has anyone tried using that?

MXXX inside MXXX 1 doesn't enable not-purchased FX either.

[MeldaProduction]

Hey folks, ok, so please update to the new beta. I tried with it a few combinations of licences and all seems working here. But there are so many changes, and licencing system became like supercomplex since MXXXCore (I so regret I ever made this... grrr...), so I'm not really sure something has changed. But I remember something regarding licences was fixed indeed, so, well, hopefully it is this

[David]

Thanks for the reply, sounds like this'll get sorted sooner or later—which is great!—thanks for that, too:) And in the meantime, MXXX 1 isn't too shabby:)
But, FYI, here's what I see in the latest beta, 14.08d: