MFM2 and PT11

[samplaire]

Hi,
Recently I changed from PT 9 to the 10/11 duo. I've got all of my U-he stuff updated to the latest beta versions (all the freeware and my MFM2 and Zebra2). Everything works ok in PT10 while in PT11 I get 'no MFM2 installed' message oppening a 9/10 saved session and the plugin is greyed out where it is supposed to be (in a particular track insert rack). But when I go to open a new plugin instance I have MFM2 in the arsenal and I can use it but as if it was a different plugin.I guess Pro Tools just doesn't recognize it's the same plugin.I'm sorry if it is covered somewhere here...

[Urs]

Go here and install MFM2 "Latest builds" with AAX support:

http://www.kvraudio.com/forum/viewtopic ... 1&t=411649

The official version will be released in a few weeks

- Urs

[samplaire]

Thank you Urs,
I installed the updates before my post and it's like I wrote - the plugin itself is available and works (AAX 64bit) in PT11. The problem is when you open a PT9/10 session in PT 11 containing MFM2 and the mentioned 'no MFM2 installed' message apears as if I tried to open completly different plugin.

[#rob]

Does PT11 automatically replace RTAS instances with AAXes? Sounds reasonable, and could be the explanation.

PT9 and PT10 don't originally support AAX (only the late 10.x versions), so it might be that your former PT9/10 installations used the RTAS plugin. We've discontinued the RTAS format and -in contrast to AAX- don't install the RTAS plugin by default any more.

To see if that's the reason, install MFM2 once again, and in the installer keep an eye out for a list of checkboxes right after agreeing to the EULA.
In that list of checkboxes, select to install the RTAS legacy version and continue through the wizard.

[samplaire]

Ok, I'll try to do this in the evening and report it here! I personally don't like such comparisons but this is the only situation where it's applicable: other plugins do restore normaly in PT11. Of course those which have AAX 64bit incarnations... Thank you for your fast response

[samplaire]

Here are my observations after things I did:

- I manually removed the MFM2 plugin from the digidesign plugin folder.
- Now I installed the beta versions from the link you provided (to make sure I compared the unarchived files with the ones I downloaded recently) - the RTAS was unticked by default and I didn't change it.
- After the installation I checked the RTAS folder to see there is still no MFM2 rtas plugin (no instance)
- I opened PT10 (latest version), opened the mentioned PT9 created session containing MFM2 - the session warned me about the absence of the MFM2 plugin in the plugins folder.
- I opened PT11 (latest version), opened the same session to see the same warning.

I have to add that earlier, with the MFM2 RTAS version present, PT10 didn't warn me. SO I decided to check one more scenario: I installed the legacy RTAS version from the beta MFM2 installer. Now PT10 had no questions, the plugin appeared in the session. After opening the session in PT11 I saw the warning...

To sum things up, there is something wrong I guess - as I said, plugins by other vendors have no such problems (please don't feel offended with it, this is not a talk like a-customer-is-always-right, it's rather an observation, I don't compose in PT because I prefer Logic for that kind of task (so I don't know if your great synths behave the same way); I use PT for sounddesign and MFM2 is a crucial part of my creative work )

[Urs]

Ok, hmmm… dunno what's wrong, but we'll look into it

(I didn't ven know that there was something one could do to transition from RTAS to AAX - I'd think that the preset format is fundamentally different, but maybe i'm wrong)

[samplaire]

Thank you for your understanding!

One of the well transited plugins is Cosmos by Nomad Factory. Perhaps you can contact the vendor to solve the puzzle?

[edit]
I've checked the version numbers shown in the 'get info' contextual menu item:
- both the official MFM 2.2 installer and the beta installer show 2.1x0 for the RTAS plugin (both files are of exactly the same size so I suspect they are the same files but one is dated 3.12.2012 and the other 22.04.2014). The AAX version shows V2.2 (15.05.2014)


Oh, I forgot to mention the system I'm on:
MacPro, OSX 10.8.5

[Fomin]

Hi,
exactly the same thing happening with Uhbik (at least Uhbik A, which i use in every project). So there's definitely something wrong ...
Dear u-he team - please fix it

P.S. I'm on Mac 10.8.5 , latest versions of Pro Tools HD 10 & 11