Help - Search - Members - Calendar
Full Version: P&m Plug-ins Bug Reports
Plugivery Forums > Official Manufacturers Forums > Plug & Mix
Pages: 1, 2, 3, 4, 5, 6, 7, 8
Nick
QUOTE (Carl Kolchak @ Mar 8 2015, 09:37 PM) *
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
QUOTE (Nick@DontCrack @ Mar 9 2015, 04:00 PM) *
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

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
QUOTE (4lyna @ Mar 25 2015, 07:04 PM) *
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. sad.gif 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
pc-eater
QUOTE (4lyna @ Mar 25 2015, 10:24 PM) *
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
eric
QUOTE (pc-eater @ Mar 26 2015, 04:26 PM) *
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


Yes, rescanning from the PREFS within the chainer is the way to go when such issues happen.

Thanks - Eric
eric
Oh and BTW

We have re-processed all Chainer orders with new serials. There was an issue with serials starting by "CHAINER" where they should have started by "PMCX"

All good now !

Thank you all for your understanding.

Kind Regards - Eric
pc-eater
QUOTE (eric @ Mar 26 2015, 05:23 PM) *
Yes, rescanning from the PREFS within the chainer is the way to go when such issues happen.

Thanks - Eric



Hi Eric,

the main issue (4lyna @ Mar 25 2015, 10:24 PM) stay's:

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

2. Mac OS X "Yosemite"

3. Cubase 8.0.10

4. P&M CHAINER 1.00

Thank you,
Peter
eric
QUOTE (pc-eater @ Mar 26 2015, 05:36 PM) *
Hi Eric,

the main issue (4lyna @ Mar 25 2015, 10:24 PM) stay's:

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

2. Mac OS X "Yosemite"

3. Cubase 8.0.10

4. P&M CHAINER 1.00

Thank you,
Peter



Ok no, there is a misunderstanding here. The Chainer is FREE to chain your authorised VIP plugins. In other words, if you have authorised your VIP plugins, these will automatically be available within the chainer. The Chainer is therefore a FREEWARE for P&M plugin owners.

Now to use VST effects or instruments, you'll need to unlock the Chainer for ONLY $49 ! We do need a little money for R&D right ?

Hope that answers your thoughts.

Kind Regards - Eric
denka
QUOTE (eric @ Mar 26 2015, 05:44 PM) *
Ok no, there is a misunderstanding here. The Chainer is FREE to chain your authorised VIP plugins. In other words, if you have authorised your VIP plugins, these will automatically be available within the chainer. The Chainer is therefore a FREEWARE for P&M plugin owners.

Now to use VST effects or instruments, you'll need to unlock the Chainer for ONLY $49 ! We do need a little money for R&D right ?

Hope that answers your thoughts.

Kind Regards - Eric

You'll get my money when you acknowledge a problem with installation on Yosemite 10.10.2 as you avoid to respond to previous poster. Otherwise, it's a waste of time and money. wink.gif
WorldStudios
Yeah. What's up with that? Several people have reported the same issue. The installer stops and throws an error. Then the plugins are not available in Chainer, probably because the installation failed... Vsts show up after a scan, but I am definitely not happy, since I need to pay to get those to work...
Carl Kolchak
QUOTE (Carl Kolchak @ Mar 8 2015, 08:37 PM) *
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




I just wanted to say a big thanks to you guys, as version 3.3 has fixed these issues.

I'm not sure if that fix was already in the pipeline, but if it was me that brought it to your attention, that's an incredibly fast addition to the fix list (I know 3.3 was already due to be released, before I'd even mentioned these problems).

Very impressed.


The only, very minor, problem (which was already there, but I stupidly forgot to mention it - my apologies) is that with Echoflex, if the synch switch is engaged from the control surface ; the switch graphic flips, but the outer ring does not change scale, and the knob continues to function in whichever mode it was previously in.

Again, my apologies for not bring this to your attention last time - thankfully it's a pretty minor issue.

Thanks again.
denka
QUOTE (WorldStudios @ Mar 26 2015, 08:06 PM) *
Yeah. What's up with that? Several people have reported the same issue. The installer stops and throws an error. Then the plugins are not available in Chainer, probably because the installation failed... Vsts show up after a scan, but I am definitely not happy, since I need to pay to get those to work...


I hope Nick will chime in here and tell us what's going on.

We still have great working Patchwork and the other wrappers and chainers, anyway. wink.gif
DaveC
AAX P&M plug ins dont show up in chainer (not sure they are showing up at all as I have RTAS installed too)

I am registered for P&M VIP bundle, and have activated the bundle and chainer.

Chainer has scanned and can see my VST plug ins, but the P&M list is empty

iMac Retina 5K 4GHz processor
P&M V3.3.0 AAX and RTAS
ProTools 10.3.10
OSX 10.10.2

Help appreciated!
Nick
QUOTE (denka @ Mar 26 2015, 08:21 PM) *
I hope Nick will chime in here and tell us what's going on.

We still have great working Patchwork and the other wrappers and chainers, anyway. wink.gif


Hello denka,

I have been busy handling all the inquiries that have been coming in to me directly, sorry about that.

About the Downloads.....

There was a huge surge of activity as soon as we announced the 3.3 version and the Chainer and the VIP Bundle on special.

The server has been running at overload levels for three days now.

It has been chugging out the files, but I have had reports of slowness, and even worse some people getting corrupted files.

Today it has calmed down a little bit and those people who had problems before are downloading correctly.

It should get easier from now on.

Try again and let me know if it still appears to be slow.

Best Regards,

Nick
Nick
QUOTE (pc-eater @ Mar 26 2015, 05:36 PM) *
Hi Eric,

the main issue (4lyna @ Mar 25 2015, 10:24 PM) stay's:

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

2. Mac OS X "Yosemite"

3. Cubase 8.0.10

4. P&M CHAINER 1.00

Thank you,
Peter


Hello pc-eater,

One little thing, it threw me off as well, the first time I installed was the fact that it said in the bottom righthand corner:

Version 1.0.0 VST demo mode

Which is OK and normal, because it means any VST and VSTi found will be available in 'demo' mode. Meaning they will fade out after 45 seconds.

BUT a cool thing thing is any chains you build and save will be remembered, so if and when you get the FULL version every chain you built with the VST will be right there ready to use.

The FREE version lets you do this and of course lets you build chains with all the Plug and Mix plug-ins you have installed in your computer.

NOW if you see the 'authorisation failed' alert at the end of the installation, it is not good news.

The Chainer will only function correctly when you get the 'Activation was Successful' alert at the end of the installation.

The Chainer is a pretty complex beast and my advice is to keep on re-installing until he is happy.

But don't let the 'Version 1.0.0 VST demo mode' throw you off as I said that is normal, it is the 'Activation was Successful' which is the key.

Best Regards,

Nick
denka
QUOTE (Nick@DontCrack @ Mar 27 2015, 02:21 PM) *
Hello denka,

I have been busy handling all the inquiries that have been coming in to me directly, sorry about that.

About the Downloads.....

There was a huge surge of activity as soon as we announced the 3.3 version and the Chainer and the VIP Bundle on special.

The server has been running at overload levels for three days now.

It has been chugging out the files, but I have had reports of slowness, and even worse some people getting corrupted files.

Today it has calmed down a little bit and those people who had problems before are downloading correctly.

It should get easier from now on.

Try again and let me know if it still appears to be slow.

Best Regards,

Nick


Nick,

Why do you avoid to respond on this:

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


You could be a politician, too much talking and avoiding to address maiin question several times. tongue.gif biggrin.gif

Best regards,

Denis

P.S I didn't ask about download and how slow it is, at all. biggrin.gif
dmsprojects
After updating to v3.3 i get an error in Pro tools. When I try to open plug in it says there been an "AAE Error -7054" Any reason this would happen? Really like these plugs but have been having a lot of issues recently. Any help would be appreciated it. Thanks.

Macbook Pro Late 2011
OS X Yosemite
Pro Tools 11 Native
Plug and Mix Bundle
denka
I can't edit my previous post to add this print screen, so, it's here:

4lyna
QUOTE (denka @ Mar 27 2015, 10:19 PM) *
I can't edit my previous post to add this print screen, so, it's here:



yep - and this happens really every time i (try to) install it. i made at least 4 to 5 attempts, but honestly, i am not willing to keep doing this on a trial and error basis until it may occasionally work some time - there is obviously a serious problem with the installer.

plus - sorry for repeating myself, but i didn't get an answer on this yet: the chainer only loads as an INSERT EFFECT in logic pro x, there is no way to insert it in an INSTRUMENT SLOT. does this only apply to the demo version? would the paid version show up as a virtual instrument? otherwise i'm not sure, what sense it would make for the chainer to load third party virtual instruments- an instrument in an effect slot cannot process any sound, at least not in logic AFAIK.

logic pro x (10.1.1. latest version)
mac os x yosemite (latest version as well)
WorldStudios
Why don't you answer our question about the installer not working?
airwavemusic
I've been through the very same stuff but it's working here, even when it says install failed, I installed p&m VIP bundle manually and it seems to work even though the message said, installation failed.
Now the list of glitches, bugs and problems I've come across while testing this one is just incredible. As usual with any plug-in from either P&M or Nomad Factory as they share some of the same code and technology, I've been through the same nightmare with a sensibly similar product called Magma. It never worked properly and I took them 8 or 9 updates to make it more or less usable. Still today I get regular glitches, plops, audio drop-outs with it all the time, on top its filters are responding too slowly to automation so they're unusable.

Here's a short list of what's going on in logic 10.1.1 on a mac os 10.9

1) The host automation is ETREMELY slow. E.G. I want to open the logic list on my track to select a parameter, and it gives me rainbow wheel for almost 30 secs EACH TIME I click on it. 2000 of parameters is maybe too much guys. It's a horrible coding mistake. 512 parameter slots as in reaktor or Guitar rig would have been enough.

2) The host automation doesn't show up the NAME of the parameter, you just see numbers in Logic, and each thine I have to open the plug-in window.
3) The displayed info is very slow, in fact it completely slows down my refresh rate on this computer, a Macbook Pro Retina 2013 with an Nvidia 750 chip (and it's running on that one). I mean everything slows down, logic, the plug-in and anything related to them.
4) Realtime Automation seems impossible to do properly as when turning knobs it keeps hanging. Remember when computers were too slow to play a specific game, the refresh rate slows down and makes your game unplayable? so I get scaled automation, which is not only what I want to avoid, but an absolute time-eater.
5) Opening any Plug&mix separately from the chainer afterwards to compare behavior, gives me the same problem, automation glitches, and I even have to restart my computer completely to get it working normally again.

My conclusion is that while I LOVE using the plug&mix effects in my productions, and I'm a huge clarisonix, limiter, echo flex, and talking tone addict, if anything from the same team is glitchy all the time, it doesn't surprise me that media don't talk about it. What a bad advertising for you guys, again and again.

In 2015 it's absolutely unacceptable to have plugins that give so many glitches and issues as yours when they get released. I'm sorry to say that, because every single production I've done in the last 2 years makes heavy use of your stuff and you deserve top rating and credit.

I contacted eric on Facebook, but he didn't seem to be active on there.

airwavemusic
After a few quick tests in Ableton Live 9 (32 bits) I can more or less say that only the Audiounit plugins are affected. Once I put the VST plugins instead, everything seems to be fine and running.
kevaquarian
QUOTE (airwavemusic @ Mar 28 2015, 09:38 AM) *
I've been through the very same stuff but it's working here, even when it says install failed, I installed p&m VIP bundle manually and it seems to work even though the message said, installation failed.
Now the list of glitches, bugs and problems I've come across while testing this one is just incredible. As usual with any plug-in from either P&M or Nomad Factory as they share some of the same code and technology, I've been through the same nightmare with a sensibly similar product called Magma. It never worked properly and I took them 8 or 9 updates to make it more or less usable. Still today I get regular glitches, plops, audio drop-outs with it all the time, on top its filters are responding too slowly to automation so they're unusable.

Here's a short list of what's going on in logic 10.1.1 on a mac os 10.9

1) The host automation is ETREMELY slow. E.G. I want to open the logic list on my track to select a parameter, and it gives me rainbow wheel for almost 30 secs EACH TIME I click on it. 2000 of parameters is maybe too much guys. It's a horrible coding mistake. 512 parameter slots as in reaktor or Guitar rig would have been enough.

2) The host automation doesn't show up the NAME of the parameter, you just see numbers in Logic, and each thine I have to open the plug-in window.
3) The displayed info is very slow, in fact it completely slows down my refresh rate on this computer, a Macbook Pro Retina 2013 with an Nvidia 750 chip (and it's running on that one). I mean everything slows down, logic, the plug-in and anything related to them.
4) Realtime Automation seems impossible to do properly as when turning knobs it keeps hanging. Remember when computers were too slow to play a specific game, the refresh rate slows down and makes your game unplayable? so I get scaled automation, which is not only what I want to avoid, but an absolute time-eater.
5) Opening any Plug&mix separately from the chainer afterwards to compare behavior, gives me the same problem, automation glitches, and I even have to restart my computer completely to get it working normally again.

My conclusion is that while I LOVE using the plug&mix effects in my productions, and I'm a huge clarisonix, limiter, echo flex, and talking tone addict, if anything from the same team is glitchy all the time, it doesn't surprise me that media don't talk about it. What a bad advertising for you guys, again and again.

In 2015 it's absolutely unacceptable to have plugins that give so many glitches and issues as yours when they get released. I'm sorry to say that, because every single production I've done in the last 2 years makes heavy use of your stuff and you deserve top rating and credit.

I contacted eric on Facebook, but he didn't seem to be active on there.


Hmmmm.... I didn't know that the code for the PnM plugz had some crossover with Nomad Factory code. This does not surprise me though. I had a total NIGHTMARE with hours and hours of lost studio time trying to "troubleshoot" what was basically flaky code in the NF Integral Pack. I was told I was "the only person with problems". I personally knew of 5 other composers who had the same problems I did and the internet fiorums revealed many more than that. All my posts got mysteriously "removed" for the NF forum - I wonder why?.....

It took years overall and still I can't trust the plugins to behave 100% reliably in my professional projects. I tested Magma a few times with different updates, and that was flaky too - crashes and hangs etc. I will not be buying it, even though I would use it if it was stable.

I do hope that the PnM stuff will recover from the bugs etc - I like some of the plugins a lot and really want to use them in projects. However, I cannot risk down time on deadline studio projects for commissions, so I'm wary.....

I also have Automation sluggishness/accuracy issues - with Degradiator - just discovered today.

I have the PnM collection installed and I'm using it with care and attention to fragility issues. I've not installed Chainer, and won't do so until I see updates that address the problems being reported here.




masterj
vsti's (in protools" are not working properly, i mean they load, but try laying down stuff on the piano roll editor, it gives out no signal
airwavemusic
okay after a second bunch of tests and a complete clean of my caches with onyx, a perm repair, etc...

What I did:

Compare P&M chainer fx automation behavior vs fx behavior in Logic, Live
Compare P&M Chainer fx auto behavior vs Magma fx auto behavior in Logic
Compare P&M effects (without chainer then) VST vs AU automation behavior.
Compare Chainer mouse automation (by dragging knobs on the screen) vs CC automation via Smart Controls and a Dedicated midi cc

To sum it up a bit:

1) VST doesn't seem to eat as much resource as AU does (and it only applies to Nomad Factory and P&M plugins), once closed the graphics go back to normal framerate
2) The AU chainer seems not to deal in time with the data sent to it by using a mouse which means an awful scale effect in the resulting automation when recording auto with a mouse, while other AU plugins give much better resolution, and logic's have max resolution.
3) The AU chainer responds efficiently when using midi CC, as if I was using logic effects, and this is the most surprising thing, it looks like the p&m and nomad factory software is too heavy for my graphics card.
4) The Chainer parameters remain definitely impersonal (param 0, param 1) which is quite unpractical,
5) The Chainer parameter list for automation is way too long and might freeze logic completely.
6) The AU and VST plugins contained in the Chainer installer will NOT install and the installer will give an error message. To solve the issue, P&M users can download both VST and AU 3.3 versions of the VIP bundle on the plugandmix.com website. Once installed, depending on the AU or VST version, plug-ins should show up into the Chainer.
DontCrack
Hello folks,

Ok we've been investigating the issues listed above. It comes out that very little issues could be reproduced. We therefore need very precise information when reporting issues :

Machine model
OS system
DAW version(s)
Which VST plug-ins crash
Etc.

But most of all, send precise information so that we can systematically reproduce the bug. Like which VST crashes. We have tested tones of them but...

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.

It also looks like you may ignore the message. Simply launch the chainer from your DAW and Re-Scan the plugins from the PREFS menu on the Chainer Gui... That should do it as well but repairing permissions is always the best option when installers fail to create folders on the system!

Those who encounter issues using controller hardware with infinite rotating buttons such as Avid command 8 should download the latest P&M plugins version 3.3.

We are actively working on reproducing issues on Logic and pro tools as reported but things work fine here... Automation can be tricky but that is an other story and we are monitoring your feedback to solve particular issues ASAP.

At last, please note that our servers have been heating up these past days with hundreds of downloads per hour. So if you encounter download issues, please be a little patient, things will shortly calm down.

Thank you all for your time reporting things. We are working hard to fix things when we can reproduce them.

Kind Regards - Eric
DontCrack
Just an other comment concerning the "Installation Failed" issue.

Again repairing the "Permissions" from the disk utility should do it but...

You may also have a look at :

Disk/Library/Application Support/Plug and Mix/PM Chainer/PM Plug-Ins

If the last folder "PM Plug-Ins" doesn't exist, it is a Script problem likely due to Permissions "write" limitations.

You may manually create the folder named exactly "PM Plug-Ins" and relaunch the installer.

All 45 P&M proprietary plugins (.pmplugins) should reside in that folder.

Hope this helps - Eric
DontCrack
QUOTE (airwavemusic @ Mar 28 2015, 10:38 AM) *
I've been through the very same stuff but it's working here, even when it says install failed, I installed p&m VIP bundle manually and it seems to work even though the message said, installation failed.
Now the list of glitches, bugs and problems I've come across while testing this one is just incredible. As usual with any plug-in from either P&M or Nomad Factory as they share some of the same code and technology, I've been through the same nightmare with a sensibly similar product called Magma. It never worked properly and I took them 8 or 9 updates to make it more or less usable. Still today I get regular glitches, plops, audio drop-outs with it all the time, on top its filters are responding too slowly to automation so they're unusable.

Here's a short list of what's going on in logic 10.1.1 on a mac os 10.9

1) The host automation is ETREMELY slow. E.G. I want to open the logic list on my track to select a parameter, and it gives me rainbow wheel for almost 30 secs EACH TIME I click on it. 2000 of parameters is maybe too much guys. It's a horrible coding mistake. 512 parameter slots as in reaktor or Guitar rig would have been enough.

2) The host automation doesn't show up the NAME of the parameter, you just see numbers in Logic, and each thine I have to open the plug-in window.
3) The displayed info is very slow, in fact it completely slows down my refresh rate on this computer, a Macbook Pro Retina 2013 with an Nvidia 750 chip (and it's running on that one). I mean everything slows down, logic, the plug-in and anything related to them.
4) Realtime Automation seems impossible to do properly as when turning knobs it keeps hanging. Remember when computers were too slow to play a specific game, the refresh rate slows down and makes your game unplayable? so I get scaled automation, which is not only what I want to avoid, but an absolute time-eater.
5) Opening any Plug&mix separately from the chainer afterwards to compare behavior, gives me the same problem, automation glitches, and I even have to restart my computer completely to get it working normally again.

My conclusion is that while I LOVE using the plug&mix effects in my productions, and I'm a huge clarisonix, limiter, echo flex, and talking tone addict, if anything from the same team is glitchy all the time, it doesn't surprise me that media don't talk about it. What a bad advertising for you guys, again and again.

In 2015 it's absolutely unacceptable to have plugins that give so many glitches and issues as yours when they get released. I'm sorry to say that, because every single production I've done in the last 2 years makes heavy use of your stuff and you deserve top rating and credit.

I contacted eric on Facebook, but he didn't seem to be active on there.


Hello airwavemusic,

Thanks for your post

Here is a capture of the automation parameters that we loaded on a slot that contains a Fabfilter plugin. Many manufacturers have way more than 500 automation controls :/

Now the automation shows the parameter names has expected.
Logic Automation

As mentioned above, we are investigating all reports but it sure isn't easy if we don't have the exact same configuration as users...

Thank you - Eric





airwavemusic
hi eric, I'm glad you are responding quickly on that one, and I'd be glad to help.

Thanks for clarifying the permissions issue, it's indeed quite common but it's a well known OSX bug, until 10.10.3 at least. At least it works that way too. I did repair my permissions earlier today, and we should all try again then.

You're absolutely right, the parameters show up correctly and as expected inside Chainer. But not into Logic pro. 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.

Anyway, if you need screenshots, or even better, video capture of what happens, It's not a problem for me to show you. Keep me updated.

Quick Update: The Installer works as expected after a repair disk, repair permissions, and an audio unit cache cleanup courtesy of onyx.
4lyna
QUOTE (airwavemusic @ Mar 28 2015, 08:21 PM) *
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.


as a workaround for too many automation parameters in logic you could try the "latch" function. pretty convenient i use it most of the time because i'm also always tired of endless lists showing up for only one plugin. BUT, i have to admit that i haven't tried latch with chainer myself yet, because the plugin itself just wouldn't work at all for me in the current version.

mac os x yosemite (latest version)
logic pro x (10.1.X - latest version)
no interface
denka
QUOTE (DontCrack @ Mar 28 2015, 06:15 PM) *
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


Do you really think we are rookies and don't know this basic "support things for dummies 2001"?

Sorry, it failed on 3 of my Mac, 4 OSX testers partitions, etc, on all instalation failed. period.
DaveC
Problem: no P&M plug ins are in the Chainer menu

iMac Retina 4GHz i7
OSX Yosemite 10.10.2
ProTools 10.3.10
I own VIP Bundle and therefore Chainer.

Installs appear to work fine.
After reading other suggestions, I checked in library/application support... - the subfolder PM Plug-Ins was already there and contained 45 plug in files. All looked correct.
Authorisation for Chainer accepts the serial and says active on this computer. (I have activated after the install, and via the plugin Prefs menu, numerous times, closed restarted the plug in, closed, restarted the host)
The bottom of Chainer still says 'VST Demo'

I also cleaned permissions ran scripts etc with Onyx and reinstalled chainer, and reauthorised again many times, no difference.

After scanning, VST effects and instruments re there and appear to work fine, but there is no submenu for 'PM Plug-Ins' so I cannot add or chain any.

Help appreciated as I don't know what else to try
rockguit
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!
thesamrohdeshow
QUOTE (rockguit @ Mar 30 2015, 06:08 AM) *
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!


Exact same outcome for me running same Mac , OS and PT versions.
Help would be awesome.
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
QUOTE (pottering @ Mar 29 2015, 10:31 PM) *
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
QUOTE (feherzog @ Apr 16 2015, 03:06 PM) *
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
QUOTE (Nick@DontCrack @ Apr 17 2015, 11:52 AM) *
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
QUOTE (feherzog @ Apr 29 2015, 06:51 PM) *
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
QUOTE (Nick@DontCrack @ May 5 2015, 01:13 PM) *
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
QUOTE (feherzog @ May 9 2015, 06:35 PM) *
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
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2024 Invision Power Services, Inc.