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

[Nick]

I'm trying to install PlugAndMix_VIP1_win32_VST_v3.2.0.zip (SetupVST32.exe), and Norton AV is telling me that it has a low reputation score and deletes the file before I can run it (Here's the link with the reason for the file being flag: http://www.symantec.com/security_response/...-051308-1854-99)

Any confirmation that it isn't a issue and I can tell Norton AV to skip the check on that file would be much appreciated.

Thanks!

Hello SolarAxix,

There is no problem. You can tell Norton to skip the check and go ahead with your install.

Norton is just being a bit too sensitive in this case, there is nothing to worry about.

Best Regards,

Nick

[SolarAxix]

Thanks Nick!

I'll go ahead and tell Norton AV to skip it and install the plugins.

[Nick]

Thanks Nick!

I'll go ahead and tell Norton AV to skip it and install the plugins.

Hello SolarAxix,

That should do the trick and let you install.

Enjoy the plug-ins.

Best Regards,

Nick

[dmsprojects]

I'm having an issue in Pro Tools 11 with these plug ins. When I open a template with say the eq and compressor on most channels the cpu goes insanely high and my fans run at full speed. This is with no audio or anything just the tracks with the plug ins inserted. Pro tools doesn't read the high CPU in its own meters it but the activity monitor does. I tested the same thing with different brands of plug ins all on the various tracks and the only time i got the CPU overload was with the plug and mix plug ins. Any ideas or fixes on the way?

This post has been edited by dmsprojects: Mar 6 2015, 07:49 PM

[Carl Kolchak]

Hi,

I've noticed that there is a serious problem when version 3.2 AAX 64bit Plug and Mix plug-ins are used with the Digidesign / Avid Command 8 control surface.

Using the endless encoders, any control turned fully clockwise will disappear from the GUI, and exhibit values higher than 100%.

Likewise, rotating the encoders so that a control is turned fully anti-clockwise, will again cause the control to vanish from the GUI, but in the case of a "Mix" control will also either produce a loud digital buzzing noise, or cause Pro Tools to crash almost immediately.



I haven't had the time (or the inclination) to try this with the entire range of plug-ins comprising the VIP bundle, but it occurred with every one of them that I tested (Analoguer / Echoflex / Digital Reverb, among others).


To be clear, even if the Command 8 is being used, or has the plug-in focused, it is still possible to use the mouse to grab the GUI controls without causing any issue - it's only when a rotary encoder goes beyond the point which the plug-in deems to be maximum / minimum.



I tried further tests, using the RTAS version of the VIP bundle in Pro Tools 10, and everything worked correctly - although not only is that an entirely different plug-in format, operating in a 32bit environment, it was also a different version of the plug-ins (3.0.2 if I recall), so I'm not sure what, if anything, that proved.




Is this an issue with other Digidesign / Avid / Eucon control surfaces?

Is it an issue with Pro Tools 11?

Is it a known bug, that is due to be fixed?



Many thanks.




1. PC

2. Windows 7 (Home Premium) service pack 1

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

4. External audio interface

5. No 3rd party software in use

6. Command 8 control surface in use

[Nick]

Hi,

I've noticed that there is a serious problem when version 3.2 AAX 64bit Plug and Mix plug-ins are used with the Digidesign / Avid Command 8 control surface.

Using the endless encoders, any control turned fully clockwise will disappear from the GUI, and exhibit values higher than 100%.

Likewise, rotating the encoders so that a control is turned fully anti-clockwise, will again cause the control to vanish from the GUI, but in the case of a "Mix" control will also either produce a loud digital buzzing noise, or cause Pro Tools to crash almost immediately.



I haven't had the time (or the inclination) to try this with the entire range of plug-ins comprising the VIP bundle, but it occurred with every one of them that I tested (Analoguer / Echoflex / Digital Reverb, among others).


To be clear, even if the Command 8 is being used, or has the plug-in focused, it is still possible to use the mouse to grab the GUI controls without causing any issue - it's only when a rotary encoder goes beyond the point which the plug-in deems to be maximum / minimum.



I tried further tests, using the RTAS version of the VIP bundle in Pro Tools 10, and everything worked correctly - although not only is that an entirely different plug-in format, operating in a 32bit environment, it was also a different version of the plug-ins (3.0.2 if I recall), so I'm not sure what, if anything, that proved.




Is this an issue with other Digidesign / Avid / Eucon control surfaces?

Is it an issue with Pro Tools 11?

Is it a known bug, that is due to be fixed?



Many thanks.




1. PC

2. Windows 7 (Home Premium) service pack 1

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

4. External audio interface

5. No 3rd party software in use

6. Command 8 control surface in use

Hello Carl,

I have reported this to the developers.

I will let you know when I have some news.

Best Regards,

Nick

[Carl Kolchak]

Hello Carl,

I have reported this to the developers.

I will let you know when I have some news.

Best Regards,

Nick

Cheers Nick!

[4lyna]

hello,

really happy about the new plugin CHAINER, but unfortunately there are some serious issues concerning the au version, which make the plugin pretty much unusuable in logic pro x (latest version, 10.1)

- GUI doesn't load in logic pro x (though it does in the mini host "hosting au" - might have to do with the legacy graphics dev kits that aren't supported by apple any longer)
- CHAINER is only selectable as an INSERT EFFECT not as an virtual instrument. therefore the ability to load third party instruments in it is also pretty much useless, because an insert effect doesn't generate sound itself (at least not in logic)

given that it's a brand new v1.0 release, i'm not that upset, but it would be great if those issues could be addressed soon, because as i said... as of now, i cannot use it at all.

[4lyna]

EDIT:

it seems that the installer on OS X doesn't work properly either... shortly before finishing the authorization screen would appear (even after "authorizing" it several times manually) and the installer screen displays that there was a failure and something went wrong.

plus - correct me if i'm wrong, but chainer is included in the vip bundle, so i purchased the bundle a while ago, i should be eligible to get the full version, right? i'm asking because the plugin keeps displaying "vst demo mode" in the lower right corner, even after doing several authorizations as i said.

any idea what could be wrong or what i might be doing wrong here?

thanks for your help!



1. Macbook Pro (late 2012)

2. Mac OS X "Yosemite"

3. Logic Pro X (10.1.1)

4. P&M CHAINER 1.00



This post has been edited by 4lyna: Mar 25 2015, 10:31 PM

[corsi617]

I'm having the same issue with Chainer not working in Logic X as well. It takes a long time for the plug-in to load, then only shows Logic control parameters, not the GUI. Even after that shows up, I get the perpetual spinning beach ball and Logic freezes up, forcing me to quit. I'm running in Mavericks too.

The funny thing is, I got the GUI to load initially, but there was no drop-down list appearing to load any plug-ins. I realized I did not have the most recent version of the plug-ins when I checked my version number, so I thought that might have been the issue. But, I thought Chainer was already packaged with the most recent plug-in versions? Obviously they did not install. So I downloaded the most recent VIP installer and it made things worse with Chainer.

Just a side note, I did see the Nomad Factory credit at the bottom of the GUI. I've always have a problem with their plug-ins crashing in Logic as well, which is why I stayed away from them. Maybe the cause is some of the shared framework too.

[eric]

Hello friends,

Thanks for the comments. We surely will investigate the issues you guys encounter with Logic. We tested as much as we could but hmmmm Audio Units are so very tricky and Apple OS, a real pain for compatibility.

When launched for the first time, the Chainer will try to scan any VSTs installed on your disk and that is why it takes sometime to launch. If issues persist, please try to rescan plugins from the "PREFS" tab on the chainer. Rescanning plugins on Logic often solves weird issues...

Please note that the Plug-ins included with the Chainer are proprietary (.pmplugin). Downloading VSTs or any other format won't change anything when using the Native plug-ins within the Chainer. You may nevertheless download the latest VST V.I.P. version (3.3) and load them as external VSTs...

We'll keep in touch.

Thanks - Eric

[kevaquarian]

hello,

really happy about the new plugin CHAINER, but unfortunately there are some serious issues concerning the au version, which make the plugin pretty much unusuable in logic pro x (latest version, 10.1)

- GUI doesn't load in logic pro x (though it does in the mini host "hosting au" - might have to do with the legacy graphics dev kits that aren't supported by apple any longer)
- CHAINER is only selectable as an INSERT EFFECT not as an virtual instrument. therefore the ability to load third party instruments in it is also pretty much useless, because an insert effect doesn't generate sound itself (at least not in logic)

given that it's a brand new v1.0 release, i'm not that upset, but it would be great if those issues could be addressed soon, because as i said... as of now, i cannot use it at all.

Thanks to all the people who posted about Chainer not working with Logic. You've saved me wasting my time installing it and testing it out.

Seems like it could be a great tool once it's ironed out though - I look forward to the de-bugged version. Thanks to P n M for creating it.

[WorldStudios]

I am on OS X 10.10 Yosemite and rocking ProTools HDX 11.3.1. I get "installation failed" every time with the Chainer. The plugin launches and works - but there are no P&M plugins availiable. I can get VSTs to work, but only in demo mode. Then ProTools crashes on quit with the Chainer window/s still visible. All in all, this was really not ready for prime time. One hour spent for nothing. Someone call me when this is actually working.

[mike110492]

Hey guys. I'm having an issue with the new Chainer plugin. I can't seem to load any plugins into it. When I click the arrow and hover over "P&M Plugins" no drop down menu appears. I'm running Pro Tools 11.3.0 on OS X 10.10.1

This post has been edited by mike110492: Mar 26 2015, 03:28 PM

[pc-eater]

EDIT:

it seems that the installer on OS X doesn't work properly either... shortly before finishing the authorization screen would appear (even after "authorizing" it several times manually) and the installer screen displays that there was a failure and something went wrong.

plus - correct me if i'm wrong, but chainer is included in the vip bundle, so i purchased the bundle a while ago, i should be eligible to get the full version, right? i'm asking because the plugin keeps displaying "vst demo mode" in the lower right corner, even after doing several authorizations as i said.

any idea what could be wrong or what i might be doing wrong here?

thanks for your help!



1. Macbook Pro (late 2012)

2. Mac OS X "Yosemite"

3. Logic Pro X (10.1.1)

4. P&M CHAINER 1.00

The same story here!
Thanks anyway!!!

PS: Loading vst plugins or instruments you have to do a full scan for your plugins in the PM-Chainer plug. That works here

This post has been edited by pc-eater: Mar 26 2015, 04:32 PM