P&m Plug-ins Bug Reports, Please report bugs or any kind of problems using DC V.I.P. Plug-ins Options

[pottering]

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.

[Nick]

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.

Hello pottering,

That will be fixed in the next version as it has been seen by the developers.

The Chainer does allow VSTi, if it is not working, I suspect the authorisation failed, did you get a 'Authorisation Successful' message at the end of the install?

Best Regards,

Nick

[feherzog]

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

[Nick]

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

[feherzog]

Hello feherzog,

I have sent your message on to the developers.

Should have some news very quickly.

Best Regards,

Nick

Thanks, Nick!

[izwun]

Anyone else get the same weird plugin editor/window behavior when loading Meldaproductions vst fx?

I'm using Mtotalbundle version 9.00 beta 1, and so far every time I load one in the chainer, the fx's editor window will open at the very top and left portion of the screen. The chainer also won't automatically resize to fit the larger melda default GUIs, and I'm unable to reposition the window (because the window's title bar is unseen) until I manually resize the window (thus exposing the title bar). I have to do this each time I load, or close then reopen a melda plugin window in the chainer.

Haven't had this issue with any other brand of vst/i, within Chainer, and I don't have this issue with this Melda version outside of Chainer.

Using the 1.1 64 bit version of the P&M Chainer on Win 7 64.

[feherzog]

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)

[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.

http://www.plugandmix.com/support/downloads

It includes the following enhancements and bug fixes.

May 4, 2015
Enhancements
- VST, AU and AAX instrument version (VSTi) of PM-Chainer
- Standalone application of PM-Chainer.
- MIDI Activity indicator (at the right of the preset browser)
- "Load VST Plug-in" menu option which allow to load VST plug-ins directly from hard drive, loaded VSTs will be automatically added to the "VST Plug-Ins" manufacturers sub-menu.
- labels A1-A8, B1-B8, C1-C8, D1-D8 on the mixer window.

Bug fixes
- crash when saving presets from P&M internal plug-ins on Mac OSX.
- bug on VU meters of internal P&M plug-ins.
- compatibility issue with D16 group software.
- compatibility issue with Tone2 software.
- "Save Preset" dialog box not showing for PM Plugins on Windows.
- issue with finding correct CommonFiles path on Windows 7 64bit.
- MIDI issue with Air Music Technology plugins, there are no more stuck notes.
- an issue on Windows 7 x64 when we double click on knobs in 32bit plugins, the knobs might sometimes be not correctly redrawn.
- PM Scanner and added more VST, VSTi compatibility.
- Z3ta+ 2 now correctly recalls chunks when loading from Chainer's preset.
- Albino 3 instrument now positioned well on the screen on Windows.


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

Best Regards,

Nick

[feherzog]

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

[Nick]

Hi Nick,

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

Best
Felix

Hello Felix,

I have brought the fact that the Chainer doesn't like the SIR2 VST plugin to the attention of our developers.

I thought it might be fixed in time for the 1.2 release but it looks like it will take a bit longer.

Best Regards,

Nick

[Carl Kolchak]

I've noticed what I believe is a bug, whereby any track that has 2 or more Plug & Mix plug-ins inserted, will not null, when a printed down-mix is compared to real-time session playback.

This was with a full mix. I haven't tried it with individual tracks, but presumably it would be the same.

The material that is audible during a null test, modulates in volume, and flails wildly all over the stereo sound field.




1. PC

2. Windows 7 (Home Premium) service pack 1

3. Pro Tools 11.3.1 (with Plug & Mix VIP version 3.3)

4. External audio interface

5. No 3rd party software in use

6. Command 8 control surface in use

This post has been edited by Carl Kolchak: Jul 17 2015, 12:38 AM

[Carl Kolchak]

I've noticed what I believe is a bug, whereby any track that has 2 or more Plug & Mix plug-ins inserted, will not null, when a printed down-mix is compared to real-time session playback.

This was with a full mix. I haven't tried it with individual tracks, but presumably it would be the same.

The material that is audible during a null test, modulates in volume, and flails wildly all over the stereo sound field.




1. PC

2. Windows 7 (Home Premium) service pack 1

3. Pro Tools 11.3.1 (with Plug & Mix VIP version 3.3)

4. External audio interface

5. No 3rd party software in use

6. Command 8 control surface in use

I'm also too much of a luddite to figure out how to edit my previous post further (after having signed out), but point 6 should have mentioned that Offline Bounce had been used, so could possibly be a factor (though I've never had any previous issues between realtime, and offline bounces in Pro Tools 11).

There was in fact no control surface present, when I discovered the above mentioned bug, not that would be a factor either way (although I have discovered a bug on at least one of the P&M EQ plug-ins, whereby the predetermined frequency bands on the gui : 60Hz / 75Hz / 100Hz etc appear on the control surface as 1 / 2 / 3 etc. When I have time to do a more detailed test, I will post about this issue separately).

Cheers!

This post has been edited by Carl Kolchak: Jul 17 2015, 12:16 PM

[Nick]

I'm also too much of a luddite to figure out how to edit my previous post further (after having signed out), but point 6 should have mentioned that Offline Bounce had been used, so could possibly be a factor (though I've never had any previous issues between realtime, and offline bounces in Pro Tools 11).

There was in fact no control surface present, when I discovered the above mentioned bug, not that would be a factor either way (although I have discovered a bug on at least one of the P&M EQ plug-ins, whereby the predetermined frequency bands on the gui : 60Hz / 75Hz / 100Hz etc appear on the control surface as 1 / 2 / 3 etc. When I have time to do a more detailed test, I will post about this issue separately).

Cheers!

Hello Carl,

Could you describe your method for doing the null test?

Do you create a new stereo track, pull in the bounced mix, invert the phase and then listen to the result?

Best Regards,

Nick

[Carl Kolchak]

Hello Carl,

Could you describe your method for doing the null test?

Do you create a new stereo track, pull in the bounced mix, invert the phase and then listen to the result?

Best Regards,

Nick

Hi Nick,


Yes.

The entire mix ends up routed through a mix bus, which outputs directly to the hardware outputs.

The hardware outputs are selected as the bounce source, in Pro Tools "bounce to disk" dialog, and the bounce is performed "Offline", i.e faster than realtime.

The bounced file is automatically imported to a new track, in sample accurate sync with the original, and is output directly to the hardware outputs (i.e. there is no accidental double bussing. It's not routing through the mix bus a second time).

Both the multi-mono Trim, and the multi-channel EQ III stock Avid plug-ins are used (independently of course) to invert the phase of the imported, bounced file.

The track levels, and panoramas, are not adjusted.




The tracks that I first noticed this on were :

Drum F/X channel, which comprised of P&M Digital Reverb > Analoger > Monster Boost

Bass Guitar, which used P&M Retro Compressor > American Tweed > Retro Equalizer


In some cases there were additional 3rd party plug-ins, between the various instances of P&M plug-ins, in others it was P&M only.

In either case, a single P&M plug-in did not exhibit any issues during null tests - it is only when two, or more P&M plug-ins are present on any given track, that it exhibits artefacts.


I doubt it's directly related, but I have observed that Monster Boost causes severe comb filtering / phase issues, when it is bypassed (I will flag this up as a separate issue).


Cheers!

[Carl Kolchak]

Some Plug & Mix EQ plug-ins are not reporting correct data to control surface with Pro Tools:



Retro Equalizer Frequency dials do not report frequency values, instead they display a control position value (Gain controls function correctly).


Liquid AIR-Q Low Frequency dial does not report frequency values, instead it displays a control position value (all other controls function correctly).


Retro Filter All Frequency dependent controls do not report frequency values, instead they display a control position value.



I've only tested this with a Digidesign Command | 8, so it may be unique to that particular Avid surface.


1. PC

2. Windows 7 (Home Premium) service pack 1

3. Pro Tools 11.3.1 (with Plug & Mix VIP version 3.3)

4. External audio interface

5. No 3rd party software in use

6. Command 8 control surface in use

This post has been edited by Carl Kolchak: Aug 3 2015, 12:44 PM