MFM2.5 preview (updated to revision 13207)

[40watt]

BTW Bypass button in Daw, does not bypass plugin.

It's a rather difficult task to get that Cubase bypass button working in our VST3 plugins due to their modularity (i.e. how they are built code-wise).

For the time being, if you need it, please use the VST2 version.

OK will do.

[Funkybot's Evil Twin]

I'm not sure if this is anything you guys can do anything about at this point, but I do wish the feedback was stronger. Would be great if there was a toggle button that could double the feedback intensity, or if the range was extended beyond the current max. You can get strong feedback with Soft Clip in the feedback path, but just would be nice to get more from the feedback knob.

Also, would be nice if there was a way to Link the Ratio parameter in each pair of inputs.

Just some suggestions from a new MFM user. Really great product!

[Urs]

You can supersize the feedback in the user matrix, but you need to specify two identical delays and feed both into themselves and each other, effectively doubling the feedback.

[Funkybot's Evil Twin]

You can supersize the feedback in the user matrix, but you need to specify two identical delays and feed both into themselves and each other, effectively doubling the feedback.

Thanks for the tip Urs! Still learning it and having dug deep into the User Matrix yet.

[Ploki]

seems to work fine M1 Native / Logic 10.7.2, Monterey 12.0.1!

I'm not sure if i need it tho

[tasmaniandevil]

I'm not sure if this is anything you guys can do anything about at this point, but I do wish the feedback was stronger.

The user matrix is definitely your best tool if you want more feedback.
Also experiment with proportional vs linear feedback.
Turning up the resonance of the filter in the feedback path can work wonders, too.

[midi_transmission]

I'm not sure if this is anything you guys can do anything about at this point, but I do wish the feedback was stronger. Would be great if there was a toggle button that could double the feedback intensity, or if the range was extended beyond the current max. You can get strong feedback with Soft Clip in the feedback path, but just would be nice to get more from the feedback knob.

That would indeed be great.

I quickly need max feedback when using short sounds as a start and let these ones flow in the delay network creating drone like sounds. Sometimes I would like to push it into strong build up fast and let it fall quickly after that to set an accent.

In this cases I wish I had more feedback range or a gain knob in the feedback path for fader riding.

[Freaqpeak]

Demoing right now. I noticed that the VST3 version doesn't have a Bypass button (Cubase) and can't be Bypassed inside Cubase either.

[Funkybot's Evil Twin]

Demoing right now. I noticed that the VST3 version doesn't have a Bypass button (Cubase) and can't be Bypassed inside Cubase either.

Known issue. See a few posts up. Use VST2 for now if you need the host bypass.

[tasmaniandevil]

Sounds beautiful, but not really stable.
Crashes sometimes - Cubase 11, Win 10 - VST3

Just a quick reminder, it would be great if you could send a mail to our support crew, so we can gather a few more details about this.
https://u-he.com/support/#contact

[Beamboom]

Wow - I'm here just for the new GUI!

Also really pleased to see your cooperation with Bitwig continue and even expand/grow. I applaud that!

[gennargiu]

Hi great new u-he. I testing new version mfm 2.5 on Bitwig studio 4.1.2 and reaper 6.42 64 bit on gnu linux mx linux (debian bullseye based). It work perfect. Best regards from Naples Italy

gennaro

[glokraw]

Looks, and sounds, and behaves great in latest AVLinux and linux Reaper 6.42. Really nice for guitars

(I started the vst3 first, and copied the beta-presets to the user folder,
re-browsed to find them...not listed. Restarted Reaper, copied beta folder to the main Presets/MFM2 folder, rebrowsed, and not there, browsed to user folder, still not there.

Restarted Reaper again, loading the vst2, and the beta folders were listed in both locations. Added a track with the vst3, and this time, the beta sounds were also in both locations.

Maybe daw re-starts and included scans are just the way things work.
I also think that with the path

'.u-he/MFM2/Presets/MFM2'

the user has no need for that second MFM2 folder, and allowing for moving all the presets up to the higher level would be nice. For those fortunate to have many U-he products, each little file browsing consolidation adds up.

Or a shorter default path of .u-he/MFM2/MFM2-Presets might be a good compromise?

Hope you all Have a great Christmas/New Years season!

(I foolishly opened Diva demo tracks to test this, and loaded the Planet Earth and Choir In The Clouds presets for a great layered pad...but Santa is done taking orders for 2021, and St Valentine hasn't started yet for 2022 ) Nobody to blame, but myself

[tasmaniandevil]

(I started the vst3 first, and copied the beta-presets to the user folder,
re-browsed to find them...not listed.

After you add new presets by using your Linux file system, you can do a manual rescan of the presets by right-clicking on the directory tree inside the plugin's preset browser, and choosing the "refresh" command.

'.u-he/MFM2/Presets/MFM2'
the user has no need for that second MFM2 folder

That's a framework convention we are using.
It might not strictly be necessary for MFM2, but we have plugins that contain more than just one plugin, e.g. Filterscape, Uhbik, Repro or Zebra.

In those cases there will be folders for each included plugin, like this:

.u-he/Zebra2/Presets/Zebra2
.u-he/Zebra2/Presets/Zebralette
.u-he/Zebra2/Presets/Zebrify

In case of Repro, the plugin started of with a single plugin, and only later got a second plugin added. Without that convention, we would have run into some trouble when trying to add preset folders for the second plugin.

[dune_rave]

MFM is crazy !!!
I mean superb : )