When I enable Host Autmation into Omnisphere for example, the actual name, or at least a shortened version, shows up in the automation parameters into logic. The same goes for every single plugin, except for Chainer and... Magma MFX. The latter features 1000 host id's and is therefore a bit less glitchy. Logic has some issues handling too many automation parameters. Fact is, none of the other effects I have give me issues every single time I click on the automation sub-menu, not even magma, and that means most of the time that it's either a graphics issue or that it's having trouble handling those params (and I'd go for the latter, because when the plug-in window is closed, it does the same anyway). A rainbow wheel every 30 secs with a list of thousands of param 0XXX isn't very pleasing to work with if you see what I mean, and hopefully you do.

It looks like Spectrasonics (to some extent), Nomad Factory, and DC are using the same host ID system. The question is now, how can we make sure they work the same way?? In the case of Spectrasonics, it works flawlessly. In the case of magma and plug&mix Chainer, it looks like it's a bit different. Omnisphere and Trillian feature 256 automation slots for the host automation, and in most cases, it's more than enough! That's just my point here. Giving access to thousands of parameters in the automation isn't absolutely necessary in most cases, but that's an open debate.

Now to answer the issues where some of you encounter "Installation Failed", that is most likely a "Permission" issue where the installer is not able to create all folders in the library, specially the P&M plugin folder. The first thing to do is "Repair Permissions" relaunch and re-install the chainer.

Kind Regards - Eric

I got the same error message after installing P&M v3.3--AAE Error -7054. All v3.3 plug-ins won't load. Earlier version (pre-Chainer) worked flawlessly.

MB Pro Retina 2.7 GHz i7, 16GB Ram
Yosemite 10.10.2
PT 11.3.1

Tried repairing permissions, rebooting, reinstalling, etc., etc. to no avail.

Please help! Thank you!

Intel Duo Core
Windows 7 x64
Ableton Live 9 x32

Just loading an empty PM Chainer shoots the cpu usage to max.

Closed and restarted Live, same result.

Ended up uninstalling Chainer after that (my usage would be to chain a MIDI vst like Kirnu Cream, but seems Chainer is Audio only[?] ), so sorry I can't be more useful.

Hi there,

Pro Tools 11.3.1 crashes while scanning plugins upon first startup after insatlling P&M VIP Bundle 3.3.0 an a Mac Pro runnig OS 10.9.2. PT gets stuck while trying to initialize the Retro Compressor AAX plugin during the application startup procedure. Moving "PM-Retro Compressor.aaxplugin" out of "/Library/Application Support/Avid/Audio/Plug-Ins" resolves the issue. Pro Tools starts up properly, all P&M plugins (including chainer) work as they should except, of course, for the Retro Comp which is missing. I already experienced the same issue with an earlier P&M bulid using PT 10.3.10 on the same machine. VST and AU versions run fine in other hosts. I guess there must be some difference in "PM-Retro Compressor.aaxplugin" compared to all the other plugins, that prevent PT from loading it properly.

Help is greatly appreciated since I'd love to use the Retro Comp along to all the other great plugins!

Best
-Felix


Mac Pro
Mac OS 10.9.2
P&M VIP 3.3.0
Pro Tools 11.3.1

Hello feherzog,

I have sent your message on to the developers.

Should have some news very quickly.

Best Regards,

Nick

Here's another bug I discovered using the Chainer AAX plugin in Pro Tools 11 in combination with the SIR2 VST plugin (http://www.siraudiotools.com/). Within chainer the SIR2 plugin loads flawlessly and I can open and reopen the editor window after closing it. As soon as the session has been closed only once and opened again, clicking the editor button of the SIR2 instance in chainer to open the SIR2 editor window immediately crashes Pro Tools. If I avoid opening the editor audio is still flowing correcltly like before the session was closed for the first time. Of course the problem could also be related to the plugin, I will inform them, too.

I get this exact behaviour on my two different systems:

Mac Pro
Mac OS 10.9.2
P&M VIP 3.3.0
Chainer 1.1.0
SIR2 v.2.4.011z7
Pro Tools 11.3.1 (native)

MacBook Pro
Mac OS 10.10.3
P&M VIP 3.3.0
Chainer 1.1.0
SIR2 v.2.4.011z7
Pro Tools 11.3.1 (native)

Hello feherzog,

There is a new version 1.2 of the Chainer that has just been posted.

...

Try it out and see if it works better with the SIR2 VST plugin.

Best Regards,

Nick

Hi Nick,

I've tried out chainer v1.2 and the problem still exists like described in my previous post.

Best
Felix