MFM2.5 preview (updated to revision 13207)

[gondii]

What a nice surprise. So far really enjoying it as a sound mangler.

[krans]

On Linux, I cannot use the up and down button to switch between presets in Mixbus 32C (and then probably Ardour also).

Actually just tried it with the VST2 and VST3 in Ardour 6.6 with Ubuntu Studio 21.04 (KDE Plasma), and the up/down arrows to switch presets work just fine.

Can you share some more information about your system, which Linux version, which desktop environment, which version of Mixbus? And can you try it in Ardour to check if it works there?

Even though this isn't something I think you should spend time on figuring out, I just thought I should inform that (I only found out today) this issue isn't really about the up/down buttons, it's about window focus.
So up/down buttons don't work in Mixbus 32C because MFM doesn't take/get window focus.
I don't know why. It's the only u-he plugin that doesn't.

[tasmaniandevil]

So up/down buttons don't work in Mixbus 32C because MFM doesn't take/get window focus.
I don't know why. It's the only u-he plugin that doesn't.

I installed the Mixbus 7.2 demo and checked it again.

Using the VST3 version, there is no problem.
You can use the keyboard up/down buttons to switch through presets.

Using the VST2 version, it will work right after loading the plugin.
But as soon as you either close and then reopen the plugin GUI, or use a dialog window (like the preset search), it stops working.

You then have to activate the little keyboard icon at the top right above the plugin GUI to make it work in VST2.

I tested some older plugin versions (rev. 10721 and 8256), and it seems this has always been like that, at least with that version of Ardour and Mixbus I have installed over here. Seems to be the case for all our plugins.

Not sure if it's a bug in Ardour/Mixbus, or in the plugins (up/down buttons are working fine in Bitwig), but I'll create a ticket in our database for it.
Can't say when Alex will have time to check this, as he's currently quite busy with other things.

Thanks for making us aware of the issue.

[krans]

So up/down buttons don't work in Mixbus 32C because MFM doesn't take/get window focus.
I don't know why. It's the only u-he plugin that doesn't.

I installed the Mixbus 7.2 demo and checked it again.

Using the VST3 version, there is no problem.
You can use the keyboard up/down buttons to switch through presets.

Using the VST2 version, it will work right after loading the plugin.
But as soon as you either close and then reopen the plugin GUI, or use a dialog window (like the preset search), it stops working.

You then have to activate the little keyboard icon at the top right above the plugin GUI to make it work in VST2.

I tested some older plugin versions (rev. 10721 and 8256), and it seems this has always been like that, at least with that version of Ardour and Mixbus I have installed over here. Seems to be the case for all our plugins.

Not sure if it's a bug in Ardour/Mixbus, or in the plugins (up/down buttons are working fine in Bitwig), but I'll create a ticket in our database for it.
Can't say when Alex will have time to check this, as he's currently quite busy with other things.

Thanks for making us aware of the issue.

I'm very much a fan of Mixbus 32C, but it is indeed picky when it comes to plugins.
And yes, older builds of u-he plugins have had the same behaviour.
So I'm really happy that newer builds behave as intended. Don't know what makes MFM different.

[exmatproton]

great update. Although, i am missing 1 thing; a skew option. So that, when the option is turned down all the way, the delay won't pitchshift the signal, but only (!) moves the buffer. Great for glitch-stuff

[SALT_34]

I had been demoing it and I pulled the trigger on it today. Love it. I didn't read this whole thread to see if anyone else had seen, but, I found a bug, I think. Right clicking anywhere or clicking on anything in the plugin that pulls up a menu, like to change the interface size or the LFO sync rate freezes all the animations in the plugin, like the VU meters, and the LFOs. I'm using the VST3 version in Bitwig. I'll happily delete if I'm being redundant, just wanting to be helpful.

[tasmaniandevil]

Right clicking anywhere or clicking on anything in the plugin that pulls up a menu, like to change the interface size or the LFO sync rate freezes all the animations in the plugin

It's not a bug, just the way our framework works.

[SALT_34]

Ah, my bad then. Tremendous work as usual, I’m putting MFM on everything. I’m such a sucker for glitchy delays and granular effects and this really scratches that itch.

[jue]

It crashes every Daw on OSX 10.13.6 here.
It loads fine but when the editor is opened CRASH.
Last version loaded today

[Urs]

That sounds like an installation issue or something, please contact support at u-he dot com for quick help

[Dostoyevsky]

Hi Urs,
any word on the release?

[Urs]

There'll be another beta shortly (maybe in two weeks) and then we'll hopefully release shortly thereafter.

[krans]

This wish/feature request comes a bit late, however I'd like to propose it:

After using this MFM2 beta/public preview for some months now, I'm very much in love with it.
However, I'd really wish for a way to bundle dry and wet to a one knob-solution where dry goes down as wet goes up and vice versa. Ideally in a "auto makeup" kind of way, as Presswerk and Satin have.

It's the kind of effect where you need dry and wet seperately to get the sound right. When they are set, however, it'd be great to lock them and have a way of turning one knob instead of two.
Especially in sound design and other fields where automation is essential, the ability to automate one parameter instead of two really makes a difference.

[jue]

It crashes every Daw on OSX 10.13.6 here.
It loads fine but when the editor is opened CRASH.
Last version loaded today

Three weeks later all the same or no new version?

[Funkybot's Evil Twin]

It crashes every Daw on OSX 10.13.6 here.
It loads fine but when the editor is opened CRASH.
Last version loaded today

Three weeks later all the same or no new version?

That sounds like an installation issue with the .data folder. Uninstall and reinstall.