Some MSF Help, Please

[dmbaer]

I was just finalizing an MSF device and was ready to create some presets. I discovered that none of my FX was working. All my other devices work as expected in this regard. The FX tab is enabled, all the grids start and end in column 1, and nothing else looks out of place.

Could somebody please load the attached preset and confirm that you're seeing the same thing. If you happen to spot my error, that's a big bonus (although I'm probably going to be profoundly embarrassed at making some inane error).

Before I bother Vojtech with this as a bug report, I'd like a quick sanity check before asking him to waste his valuable time.

I'm attaching the file, since it's too big to insert as code.

Many thanks in advance.

[jmg8]

Which FX do you mean? If you mean the reverb and delay etc, then it is because they are all in a modular that is not enabled.
Does this solve it, or is there something else?

[David]

Hmm…how to turn a .txt file into an MSF device?

[jmg8]

Hehe, just copy all the text and then click on paste in MSF.

[David]

Thank you, Jason:)

[dmbaer]

Which FX do you mean? If you mean the reverb and delay etc, then it is because they are all in a modular that is not enabled.
Does this solve it, or is there something else?

Thank you!!! Sometimes it takes a fresh pair of eyes to identify the obvious. I had forgotten about the FX nesting and the outer grid was collapsed, so I was just not seeing the cause of my problem.

I still have no idea how that Modular module got put out of service, though.

[dmbaer]

Hmm…how to turn a .txt file into an MSF device?

In case Jason's reply wasn't clear, I'll elaborate. You don't turn a .txt file into a device without first doing a (Melda-style) Copy operation from an existing device/preset. The Copy and Paste buttons at the device level are in the right-hand tool bar. After copying into the clipboard, paste the clipboard contents into an editor and save it to disk - naming it with a .txt extension helps to open it again in your default text editor but the name is not important. To load, bring up the .txt file in and editor, select all and copy the contents to the clipboard. Finally, do a (Melda-style) Paste into the plug-in.

Of course, if you're just doing a local copy of a device from one instance of a plug-in to another, you can skip the .txt file business completely.

[jmg8]

Actually I was surprised you made it into text. I prefer to hold CTRL and click copy this creates a .msettings file. It's faster than the text option.
As for the collapsed modular, I have done it myself in the past, it's hard to notice the panel down the left. Easy to miss, hehe

[David]

Helpful, thanks guys—Melda-speak is NOT my native tongue:)

Speaking of which, in a recent email exchange Vojtech referred to 'the "active" file', thus:

…
Next, all we’ll need is an Easy Screen for MCCG, and all we extremists can make our own MIDI FX!

Haha, sorry, that's a no . But you can actually hack it by creating the "active" file .

I asked him what that meant, but along with a few other questions, and he didn't reply about this "active" thing. Either of you know what he meant, by any chance?

Any way to "host" MCCGen inside MSF or MXXX or …?

[dmbaer]

I prefer to hold CTRL and click copy this creates a .msettings file. It's faster than the text option.

Well, now I prefer it as well ... having just learned this feature exists.