MSF: MP weirdness, or…? Part 2

Official support for: meldaproduction.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Any idea why loading a saved FX grid preset into a Modular would change all the previous MP assignments for the modules in the preset?

Here's what I did:

Arranged a bunch of FX modules in the grid, and assigned a bunch of MPs to them. Looked like this:

Image

Later in the same GPreset, decided to put that arrangement into a Modular so I could combine it with the Main Template FX. To do that, I saved the original grid arrangement as an FX Grid Preset, then loaded the MainT FX, which I'd previously saved as another such Preset. I added a new Modular above the Modular that had created, and loaded the original grid's Preset into that.

When I checked the mapping, I could see that as a result, all the existing MPs for the modules now inside the new Modular, while still there in the Manage list, had now been changed to have other targets, none of which were correct, iow, not just the list labels were different, they were pointed at different things:

Image

I eventually fixed this by going back to the previous GPreset and copying the list items when they hadn't yet been moved, then pasting these into the new list in the same slots, after the move, and resetting all of the ones that had been changed.

But WHY should they have been changed in the first place? This wasn't yet a device, had no DPresets… Where'd those other targets come from? They were for parameters that AFAICTell didn't even exist in the GPreset I was building, such as Flanger parameters where there had been Convolver files, but no Flanger in the grid. The extra step of copying the original list items isn't that horrible to do, now that I know it's needed, but it seems like a glitch in the system that it IS needed…

Post

If you save a grid and load it into a modular, the loaded modules have different "path names". The MP loader cannot find the old assignments (because they now effectively have new names), so it picks a new target (and usually doens't guess very well as to what it should be).

Post

Thanks!

I'd love to hear more, well, EVERYthing!, about how the Manager works, esp. now that it has two new buttons—DEEP ones! Is this covered (REALLY covered, not just ?-popup-info covered…) anywhere, or just to be picked up along the way however that happens?

Post

But where are the Distortion and Flanger plug-ins (MP97 and 98)?

Perhaps, when a Grid preset is loaded, any MPs that target any of its plug-ins parameters should be rebuilt (to create the correct path). The same would happen when a plug-in is copied and then pasted into another Grid.

Also, the MP Manager is pretty new and the 2 buttons are very new. So you may well know as much as we do. :)
DarkStar, ... Interesting, if true
Inspired by ...

Post

DarkStar wrote: Mon May 27, 2019 9:32 pm But where are the Distortion and Flanger plug-ins (MP97 and 98)?

Perhaps, when a Grid preset is loaded, any MPs that target any of its plug-ins parameters should be rebuilt (to create the correct path). The same would happen when a plug-in is copied and then pasted into another Grid.
Ah, thanks for the reminder to try the copy/paste functions more often! It finally occurred to me just this AM to open a second instance of MSF when copying from the Manager…
Also, the MP Manager is pretty new and the 2 buttons are very new. So you may well know as much as we do. :)
Uh-oh! :)

Post

Always remember that MPs are sort of associated to whatever modules you have loaded. When you kill modules, the parameters are dead. If the new set of modules have the same set, all good, if not, MPs will get remapped to something else. If you know this will happen, reset the MPs before.
Vojtech
MeldaProduction MSoundFactory MDrummer MCompleteBundle The best plugins in the world :D

Post Reply

Return to “MeldaProduction”