As the title says. If i pick a preset and/or tweak it, save the project and then load it again, the plugin is back default.

(rob papens blade seems to suffer from this too, but not rp-delay - all other plugins i have loads correctly in projects)

Interesting - that suggests Maschine is doing something different to NI Kore 2 because they store their state fine in Kore 2 (although they don't report the preset name and you can't import presets except for Shimmer)

Do all the values go back to their default settings, or just the preset name?

Unfortunately, I have no way of testing this. Products that require a hardware interface tend not to have any demo/NFR versions, and even the lightest version of Maschine looks like a considerable investment.

Sean Costello

Ok, bear with me...
In Maschine you can't save fxb or fxp. Instead you have Maschine's own format, called *.mxrp or something. If you want to browse patches from the hardware, that is what you have to do, save each and every patch into Maschine's format. You can switch to midicontroller mode and send standard midi to change patch, but not all synth's can handle that .. and it's only for synths, not effects.
There's four slots for each sound (16 sounds per group, 8 groups per master).
The first slot can be either Input (for other sounds or groups to send to - it becomes a bus), a synth or an effect.


If i load a new project and insert Ubermod in slot two and select a random patch and then save/quit/start/load project, it will revert to default patch

If i insert Ubermod on slot two and without changing the default patch but just modify it, it WILL stay edited when i reload.

Alright, i think i nailed it. Maschine doesn't receive information from ubermod/room when changing patch. However, when moving a knob around, it does get that info. So to make a combination of the above: Load a patch, change a knob and then save/quit/start/load project. You will now have the default patch BUT with the changes you made resulting in total chaos

The knobs will follow this as well - If i move a knob and save, it will still be "moved". If i load a patch resulting the knob having another value and it will be defaulted.

Another weird maybe unrelated thing i've found has to do with the preset button and the < and > buttons.
When i open Ubermod/verb either by loading a project with the plugin in already or if i insert the plugin, the patch will not change if i press the next (>). If i press it five times (with no change to patch) i will have to press it back (<) five times to reach default. If i press back once again, it will go to the patch at the bottom of the list, in my case "MovingInStereo". Actually, the default patch is at the bottom of the list. If i press back a few times or select a random preset and then press next until i reach default again, the same procedure takes place. If i press next three times i will have to press back three times to reach "MovingInStereo".

I really hope i've been clear. It's not easy to explain this when you can't see what im doing

The solution for now, for me, is to save in Maschine's patch format as that saves the settings. This solution however sort of ruin the advantage you gain by using Maschine. It removes the fun and simple as well as the "hardware control only". Maybe it's Maschine being lazy, but other vst's like the free Phazor keeps the settings if loaded, change patch, savequitstartload.

I'd be very happy if you found a solution to this! Maybe if it's trouble in Maschine, it could be trouble elsewhere, just that it hasn't been noticed yet (or in future patch of another DAW etc).

OK, that is some good info to go on. I will look into this. No timetable on if and when I can fix this in ÜberMod, as I am deeply mired in finishing up the next plugin. However, I will look into this behavior in the next plugin's preset code, and see if I can make changes that I can eventually fold back into ÜberMod.

Odds are good that the release of Mountain Lion will prompt me to go back and revisit all of my plugins. So my Apple-related pain will end up being to your gain, as these forced updates are a good time to fold in bug fixes.

From my perspective, it sounds like the preset changes from the Valhalla GUI will change the internal parameter values and slider display values, but these are NOT going through the host, so the host may not register these changes.

Sean Costello