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!

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!

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

Monster Boost causes severe comb filtering / phase cancellation when bypassed in Pro Tools.

If the plug-in is made innactive, there is no problem. Likewise if it is removed, but bypassing causes a severe phase misalignment.




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

Getting this error in PT11.3.0 after upgrading to V3.3.0 from 3.1.0 of the VIP bundle.

"the following plug-ins were made inactive because of insufficient system resources". Then it lists all the plugins from the VIP bundle that I'm using in the session.

After opening the session, those plug-ins are deactivated, and when I try to reactivate, I get this error. aae error -7054

I really like these plug-ins, but have had so many issues with them...buggy. I don't see a way to go back to an older version, but I was just finishing up some mixes, and not really looking forward to the idea of having to redo them minus the P&M plugins that I used.

Hello sgaudio,

Thanks for your interest in DontCrack and Plug&Mix.

Some ProTools 11 owners have had problems linked to how OS 10 handles preferences and the overwriting of the older files.

It seems the old files have stayed in place and are blocking the new 3.3 files from being read by ProTools.

One client got it working by trashing his ProTools Preferences.

Try going to my App Support/Avid/Plug-ins folder and manually trashing the older PM plugins. The error caused by the fact that
both old version as separate PM-xxxxxx.aaxplugin and a new Plug and Mix folder that are conflicting.

Trash the Plug and Mix preferences as well.

Repair permissions using the Disk Utility app.

I looked up the AAE error -7054 and it has to do with ProTools seeing multiple folders of a manufacturer's plug-ins.

Try it and tell me if it gets you up and running again.

Best Regards,

Nick

Hi Nick,

I have been noticing crashes on some mixing sessions in PT 12 lately during the loading process of the sessions. After troubleshooting these mixes trough the process of elimination I noticed that when a session has 2 instances of the VIP bundle Tilt plug-in the session crashes once PT is at the point of creating the session overview. Also when starting a sessions in safe mode with all plug-ins inactive the session crashes once I enable the 2 tracks that has the Tilt plug-in on them. So I'm wondering if there are still any planned updates coming out for the VIP bundle? Thx

Hi Notes,

Can you kindly list us your full system specs; inc. PT revision and session settings. This will help us try to repro.

Do you have an open support ticket logged with our technical support team, and are you able to reproduce this in a stripped session with just Deluxe Tilt instantiated?

Best regards,

The problem I am having is when I insert one of the plug and mix plugs on a channel and adjust the parameters as needed and go to another channel the plugin (regardless of which plug & mix plug I use) resets itself to it's default mode. When I try to move the "knobs" again the just go back to zero. The last download I did of the plugin was on 12-16-15.


I am running Pro Tools 12.4 on a PC:

Windows 7 Home premium SP1
10g Ram
64 bit
AMD FX 6120 6 Core Processor 3.5ghz

Thank you,

Bret Ferguson

Hi Bret,

Please kindly log any support queries via our support portal - SUPPORT, following the presecirbed format (below). It is unclear from the post of your steps.




Kind regards,

Hey all,

Just got done installing the latest 3.3 VIP Bundle on my studio Mac Pro.

Everything runs great except for offline bouncing in Pro Tools HD 12.5.2 and 12.6.0. I have narrowed it down to being all the Plug and Mix plugins that I use on the sessions.

Removing all instances and then selecting offline bounce works as it should. Add any of the plugins back in, and it instantly crashes on offline bounce. They seem to work fine during realtime bounces, which is okay for smaller length things, but when working on something long it is really workflow hindering.

System:

Mac Pro 5,1
Mac Os 10.9.5
2x2.66 Ghz 6 core intel
Pro Tools HD 12.5.2, 12.6.0
AAX 64Bit

Hi,

Thanks for the post! We received this in our support mailbox too and have requested further information to assist our developers with diagnostics.

Under the sampling rate 176,400Hz or more,
VIP bundle Amp simulators don't work correctly.
Tested under some computers and platform.

Yudaidhun

When I updated the VIP bundle with the new version it broke Clarisonix (at least, I didn't check all plugs). I also had Liquid Air EQ and Electro Optical in the session, which worked great. The 5 new plugins weren't available for me to use even though I saw they were installed in the plugin folder on the hard drive.

Mac OS 10.8.4
PT HD Native 10 and 11, latest versions

Hy,

I have the VIP Bundle and an full Licence of Chainer. The last Update for VIP Bundle brings 5 new Plugins but the Update (13th January 2017) for Chainer is the same Installer from year 2015 and contain only the 45 Plugins. i have download it direct from
Plug & Mix Website an from Plugivery, Its all the same.

Has anybody an Idea why or how to bring the 5 new Plugins into my chainer PM List (I know, it work with the vst wrapper function of chainer an i can use the new plugins, but the integration has any small features the not present in the VST Wrapper)

Best regards

Michael

I posted this in a new thread where I saw other users have same problem: after the new update Reaper always crashes whenever it reach basspeg plugin during new VSTs scan. Still didn't tested all other plugins but they were scanned without problems.

Here's the link of the related thread on this forum http://forums.plugivery.com/index.php?showtopic=142910

thanks for you support!

Yeah, why is the latest version the same number (3.3.0) as the previous version?

I just installed P+M 3.3.0 AAX. I get the following errors:


Clarisonix and Distorted are not valid 64 bit AAX plugins

Yeah same here!

I'm running Pro Tools 12.7.0 with 10.10.5 on a MacBook Pro.

Liking the new plugins very much BTW

Stephen

Also Protools 12.7 on Win 7 64bit. The installation falls over when it reaches the basspeg plugin.

Cheers

Clive

I just sorted this problem by deleting the old P&M plugins and reinstalling the bundle.

AAX64 on Pro tools 12.7 on a win 7 64 bit PC. Just downloaded the latest installer 18 th jan (why is it still 3.3.0 ?) and it still falls over at the basspeg plugin. Moved basspeg to the unused plugin folder and then everything loads. Alas Basspeg was the most interesting of the new plugins ! Oh well.

Clive

Hi everyone,

Ali here, marketing for Plugivery.

Thanks for contacting our support team recently and raising issue with regards to the new 5 P&M plug-ins and Chainer. Our developers have been made aware and have fixed the following issues. New builds are now available on our download site HERE

For AAX, please delete the InstalledAAXPlugIns file in the following paths to force Pro Tools to rescan at launch...

Mac: Users/<your name>/Library/Preferences/Avid/Pro Tools

PC: C:\Users\UserName\AppData\Roaming\Avid\Pro Tools

--------------------

Fixed:

• [Mac] No new plug-ins available in Chainer.

• [Windows] Basspeg causes crashes in DAWs.

• Clarisonix and Distorted not validated as 64-bit AAX plug-ins.


Known Issues:

• [RTAS] Avid have depreciated support for the RTAS format however we will look to make the bundle available as many of you have requested if we can.


Note: Our support for this format may discontinue also in the near future as we usher those to update to Pro Tools 10.3.7 or above to stay compatible with moving and growing technologies as we expand.

Hope this helps, let us know if you're having any other issues!

Basspeg aax still causes protools 12.7 to crash with loading Win 7 64.

Cheers

Clive

Is this a third release of v3.3.0?
Please set specific version number every time the update is available,
or I cannot check or report what version I am using.

Ok. The New Installer Version from 17th January 2017 for Chainer add the 5 new P&M Plugins to Chainers PM-List, but there is a little bug. When you choice PM Gatevador in the PM-Plugin List into Chainer, it load PM Retro Limiter. It´s in the Standalone App (32/64-Bit) and also the same in the Plugin Versions (32/64-bit). All other 4 new Plugins are loaded correctly.

Tested on Mac OSX 10.9.5

Hey, Ali--

Haven't seem another post from support so I just want to make sure you're getting feedback. First of all, it was a great surprise to get five new plugins. Thank you!

However, it does appear that, despite the recent fix you mentioned, Basspeg still will not register in most Windows 64-bit DAWs. I'm very happy with the package and I'm looking forward to working with Basspeg when the bug is fixed.

Hi

I installed the VIP pack with the new plug ins and now Protools 12.4 crashes every time on Basspeg when starting up PT.
Please help

Just tested the 3.31 Plug and Mix in a Windows 64-bit DAW (Sonar Platinum), Basspeg still crashes on scan.

Hi everyone,

We've taken note of all the feedback and forwarded it to the development team. They are working as fast as they can to fix all the issues. We will get back to you as soon as we have any updates. Sorry for the inconvenience, it will all be resolved very soon.

Thanks for the continuous support guys,
Hope everyone has a great day!

Thanks for your support Ali, Plug&Mix plugins are mostrly my go-to plugins, keep up the good work!

Hi again everyone, Ali from Plugivery here.

We just wanted to update you that all remaining issues re P&M and the new 5 plug-ins should now be resolved. The developers have fixed validation, crashes with Basspeg on Windows systems…
Also, the version number for the VIP Bundle and the Chainer have been updated.

Important Note: users will need to rescan plug-ins in their DAW and clear any blacklist files on their systems. This means for Logic, deleting the AU Cache file in…

/Users/<your name>/Library/Caches/AudioUnitCache

and Pro Tools the InstalledAAXPlugIns file in these paths…

*Mac*: Users/<your name>/Library/Preferences/Avid/Pro Tools

*PC*: C:\Users\UserName\AppData\Roaming\Avid\Pro Tools

Hope this helps, please let us know if you are still having some issues.

Thanks!

Note for Mac AU users:

Go ahead and delete the cache if you wish to have to re-validate ALL your 3rd party plugins. As far as I know you can simply go to the Plugin Manager inside Logic, select all the PnM plugz and then "rescan selection"? This way, it's not necessary to re-validate every single one of your plugz. If you've got 100s of plugz like me, then this might be preferable. The choice is yours of course ;-)

Please correct me if I'm wrong about this. Ta ;-)

Thanks guys,

For Reaper, open the reaper-vstplugins.ini file. Will be in different places depending on OS, but search for the file.

Open with notepad or text editor. Basspeg will be one of the last entries. To clear the blacklist, delete the whole Basspeg line and save the file.

Install the new revidions and open Reaper. If Basspeg fixed, it will now work.

Cheers,
John

Unfortunately Basspeg still crashing Reaper even with 3.3.1.

Haven't tried Pitch Me yet but noted the same dll size so likely not fixed yet either.

John

Hey all,

Ashley here, QA for P&M. Apologies sincerely for the issues most have been facing here with our new plug-ins, unfortunately these hit us as we left for NAMM and support has been staggered the past days. I've been pushing our developers with everyone's comments to get fixes up and all having been told have been fixed in relation to validation, crashes etc reported through our forums, others and support portal.

I'd urge everyone to follow detail for deleting the plug-ins currently installed, clearing blacklist files, cache file for AU and InstalledAAXPlugIns file for Pro Tools to force a rescan on launch. And, rescan in your DAW of choice via preferences if an option... for example in Ableton Live, hold ALT and click rescan button in Preferences > File Folder to force a rescan of all plug-ins...

The latest version 3.3.1 of the VIP Bundle and 1.2.1 of Chainer are the latest with all fixes. pLease see the change log for details.

If any other issues are present please do not hesitate to contact us via our support portal as this the best method/forum for all support quieries.

Kind regards,

Thanks for your reply Ashley.

I did a blacklist cleanup in Reaper but the crash remains with Basspeg. I didn't however do an uninstall of all plugs before cleaning the blacklist. Only deleted the Basspeg dll and cleaned the Reaper ini file imposing the quarantine, which I thought would be enough.

Will do a complete uninstall of the suite, clean the ini entry, reinstall 3.3.1 and see if that works.

Report back coming.

John

Well, that was quick.

Uninstalled everything. Cleaned the Reaper blacklist. Reinstalled the 3.3.1 suite. Started Reaper and still crashed on Basspeg.

The other plugs scan successfully although I suspect that Pitch Me is a bit on the fragile edge. Crash logs were created if they will help.

John

Hey John,

Thanks for getting back. Can you kindly write us at our support portal - help.plugandmix.com. Note your full system specs, Reaper version etc and attach crash logs/mini dump files. I'll have our guys check it out... and, I wanted to add a futher apology for absense whilst at NAMM again to push this and ensure issues fixed as I know you guys really want to check these awesome new plugs out.

I'm here to support and will be back in situ/office on the 30th, but floating and keeping check on this.

Ashley,

Will get the logs together and submit.

Realize almost how much work this entails and how life gets in the way. Know you guys are doing your best to fix the finest plugin suite available on this planet.

Best,
John

Thanks John, appreciate it much!

Ashley,

I have the mini dump files but have had no luck using the online contact method. Unexpected errors returned over a couple weeks trying to use the online form.

Is there an email that can take attachments that I can send the crash logs to?

Thanks,
John

Found an email address for Nick and sent the crash logs for Basspeg.

Hope it was the right Nick and that he is still with you. Otherwise, someone else got a weird email.

Noisy process, but will force a Pitch Me crash and send those logs as well.

John

Basspeg still crashing Cubase 9.01 windows. Removing it from the blacklist/rescan causes instant crash.

Pitch me also crashes Cubase after just turning the knobs for about 10 seconds.

Hello, I encounter the same problem with the Basspeg since yesterday. v3.3.1
Crash in Cubase Pro 9 and Wavelab Element 9
This problem follows the activation ... the demo mode works.
As soon as the plug is activated it crashes my Daw
Configuration:
PC Windows 7 64 bits
Cubase Pro 9
Quad core 2.8ghz
8 GB of ram

Verified in Reaper that the demo mode works, but not the authorized version.

Strange, but possibly useful info for the devs.

As much as I hate to admit anything working better in a Mac environment, seems like the Mac users are having no problem. For us windows diehards, need to find out what crashes the plug in the authorization process. May be harder to find out what is causing Pitch Me to go south, but needs to be addressed as well to get it stable.

John

Hi

Just installed the P&M 3.3.1 update. Basspeg still crashes ProTools 12.4