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

[Howie62]

Hello Howie,

A couple of questions for me to understand the problem more clearly.

1/ You are recording onto a track that has on of the amp sims as an insert in order to have the "sound" you desire as you monitor the recording, right?

2/ Other tracks in the session have distortion on them, although they don't have an amp sims or any plug-in whatsoever on them right? When you solo one of these tracks is the distortion still present?

Best Regards,

Nick

Hi Nick, thanks for your reply.

I first encountered the problem when trying to use one of the P&M amp sims to replace the amp sim on a previously recorded guitar track, after disabling the previous amp sim and inserting, in this case, Magic Queen, I then experienced a horrible granular distortion on the track, this disappeared once I disabled Magic Queen and used the original plugin.I tried this on other previously recorded tracks, and using other P&M amp sims with the same result.
I haven't experienced any problems using the sims on anything begun from scratch.
However I decided to add a new guitar track to an idea which pre dated me using P&M amp sims.This consisted of a guitar, bass and drum track.I inserted a new track, inserted a P&M amp sim, and the original guitar track, which had no P&M plugins at all, then began exhibiting the same awful distortion, the bass and drum track were unaffected.What's more, disabling the amp sim on the new track didn't stop the distortion on the original track, neither did deleting the new track entirely, so I had to scrap what I'd done and open it all again.To double check, I went through the same procedure, with the same result.
So as it stands right now I can only use the P&M amp sims on something completely new, which is a shame as I liked particularly, Magic Queen, enough to replace what I'd originally used, on some remixes.

We're not talking slight distortion either, it's high gain horror, nasty digital and grainy..so there's obviously a pretty serious bug going on, especially if it can affect guitar parts on other tracks, not even using any P&M plugins!As previously stated, I've tried reinstalling, to no avail.

Thanks for your help

Howie

Thanks for your help

[Nick]

Hi Nick, thanks for your reply.

I first encountered the problem when trying to use one of the P&M amp sims to replace the amp sim on a previously recorded guitar track, after disabling the previous amp sim and inserting, in this case, Magic Queen, I then experienced a horrible granular distortion on the track, this disappeared once I disabled Magic Queen and used the original plugin.I tried this on other previously recorded tracks, and using other P&M amp sims with the same result.
I haven't experienced any problems using the sims on anything begun from scratch.
However I decided to add a new guitar track to an idea which pre dated me using P&M amp sims.This consisted of a guitar, bass and drum track.I inserted a new track, inserted a P&M amp sim, and the original guitar track, which had no P&M plugins at all, then began exhibiting the same awful distortion, the bass and drum track were unaffected.What's more, disabling the amp sim on the new track didn't stop the distortion on the original track, neither did deleting the new track entirely, so I had to scrap what I'd done and open it all again.To double check, I went through the same procedure, with the same result.
So as it stands right now I can only use the P&M amp sims on something completely new, which is a shame as I liked particularly, Magic Queen, enough to replace what I'd originally used, on some remixes.

We're not talking slight distortion either, it's high gain horror, nasty digital and grainy..so there's obviously a pretty serious bug going on, especially if it can affect guitar parts on other tracks, not even using any P&M plugins!As previously stated, I've tried reinstalling, to no avail.

Thanks for your help

Howie

Thanks for your help

Hello Howie,

Now I need some info on your setup, what computer, which OS, DAW, with all the version info possible so I can see what is causing this problem. We have a huge number of people working peacefully especially now after the "Group Buy" in situations very similar to yours, but there is definitively something that is preventing the amps from working correctly.

To get to the bottom of this, we need to figure out what is causing this, we have had some conflicts reported between our plug-ins and older versions of other manufacturer plug-ins, so a list or screen shot of what you have would be useful as well.

Best Regards,

Nick

[Howie62]

Hello Howie,

Now I need some info on your setup, what computer, which OS, DAW, with all the version info possible so I can see what is causing this problem. We have a huge number of people working peacefully especially now after the "Group Buy" in situations very similar to yours, but there is definitively something that is preventing the amps from working correctly.

To get to the bottom of this, we need to figure out what is causing this, we have had some conflicts reported between our plug-ins and older versions of other manufacturer plug-ins, so a list or screen shot of what you have would be useful as well.

Best Regards,

Nick

Hi Nick, thanks for your reply.

I actually included most of the info you're asking for in my initial post, but here goes again.
Windows 7 64 bit fully up to date, i7 3.50Ghz, 32gb ram, The PC is a purpose built machine, and not a home build, or general use shop bought machine.I'm using an RME Fireface UFX which has the latest drivers and firmware.
DAW-Presonus Studio One 2.5.1 64 bit (latest version).

I do have a fair few plugins installed, although I'm very diligent about latest versions, and am certain nothing is out of date.I'm also using very few bridged 32 bit plugins, as I identified these as the root of CPU spikes when I first started using Studio One.It may be easier for you to tell me some of the ones you've had conflicts with, as I've experienced this problem on different projects/pieces not all using the same plugins, and you may just list one that I use a lot.There are certain UAD-2 plugins I use on most projects, I have the latest version v7 of the UAD plugs.Those aside, the plugins I use on a project can vary considerably from piece to piece.I mainly use Amplitube CS for my guitar parts, and I disabled it, rather than removed it when trying the P&M plugins as alternatives, I have the latest version of ACS, it tends to be there in my guitar chain disabled or enabled as the case may be.It's there on the new 'from scratch' pieces, and I've had no problems with those, this problem is only affecting already recorded guitar parts.I did try removing other plugins in some of the projects to see if there was a conflict but nothing I took out changed the situation.I thought I was going nuts when the distortion appeared on a different, non P&M guitar track, so there must be something very strange going on!
Let me know if you need any more info, and thanks again

Howie

[Nick]

Hi Nick, thanks for your reply.

I actually included most of the info you're asking for in my initial post, but here goes again.
Windows 7 64 bit fully up to date, i7 3.50Ghz, 32gb ram, The PC is a purpose built machine, and not a home build, or general use shop bought machine.I'm using an RME Fireface UFX which has the latest drivers and firmware.
DAW-Presonus Studio One 2.5.1 64 bit (latest version).

I do have a fair few plugins installed, although I'm very diligent about latest versions, and am certain nothing is out of date.I'm also using very few bridged 32 bit plugins, as I identified these as the root of CPU spikes when I first started using Studio One.It may be easier for you to tell me some of the ones you've had conflicts with, as I've experienced this problem on different projects/pieces not all using the same plugins, and you may just list one that I use a lot.There are certain UAD-2 plugins I use on most projects, I have the latest version v7 of the UAD plugs.Those aside, the plugins I use on a project can vary considerably from piece to piece.I mainly use Amplitube CS for my guitar parts, and I disabled it, rather than removed it when trying the P&M plugins as alternatives, I have the latest version of ACS, it tends to be there in my guitar chain disabled or enabled as the case may be.It's there on the new 'from scratch' pieces, and I've had no problems with those, this problem is only affecting already recorded guitar parts.I did try removing other plugins in some of the projects to see if there was a conflict but nothing I took out changed the situation.I thought I was going nuts when the distortion appeared on a different, non P&M guitar track, so there must be something very strange going on!
Let me know if you need any more info, and thanks again

Howie

Hello Howie,

We have had a couple of reports of strange behaviour with P&M plug-ins with Presonus Studio One.

Some people adjusted the device block size under song setup to 256 samples (bumped it up from 128 and this seemed to have addressed the issue. Turned out to be a buffering issue.

You might try posting on the Presonus Studio One forum and see if anyone has had the same very weird "ghost" distortion on tracks where the plug-in isn't even active.

Best Regards,

Nick

[Howie62]

Hello Howie,

We have had a couple of reports of strange behaviour with P&M plug-ins with Presonus Studio One.

Some people adjusted the device block size under song setup to 256 samples (bumped it up from 128 and this seemed to have addressed the issue. Turned out to be a buffering issue.

You might try posting on the Presonus Studio One forum and see if anyone has had the same very weird "ghost" distortion on tracks where the plug-in isn't even active.

Best Regards,

Nick

Hi Nick, thanks for your reply, I'll try the block size increase, and see if there's any similar bugs with Studio One.

Cheers

Howie

[whitealbum]

Hello Nick,
about parallel actions:
It was only an example, if only Cubase is open, clicks appears as well.
Actually, i have nothing in the background (win indexer is closed) only Avast antivirus is in the back.
But i don't believe that there is a correlation, because in this project there are a lot of other plugins like Waves, Abbey Road Plugs, IKM Plugs, Fabfilter, cubase internal and Voxengo plugs.
No other plug makes a problem.
Amount of CPU is possible via priority in the task Manager. Cubase got the priority "high" which is fine.
avast and other stuff have got "normal" priority.
In this project RAM isn't a problem, i have 12 gb RAM, 5,57GB is used RAM, so there should be no problem.

I'm checking now deactivating avast anti-virus in the background.

bye

same problem, deactivating anti virus makes no difference...

[Nick]

same problem, deactivating anti virus makes no difference...

Hello whitealbum,

One bit of info that could help is whether you have the whole bundle or just the chorus plug-in.

If you do have the whole bundle I imagine that the other P&M plug-ins are not sending out clicks.

Second thing I must check is if the version number is listed in the top left corner of the plug-in. Is it the case?

Best Regards,

Nick

[whitealbum]

Hello whitealbum,

One bit of info that could help is whether you have the whole bundle or just the chorus plug-in.

If you do have the whole bundle I imagine that the other P&M plug-ins are not sending out clicks.

Second thing I must check is if the version number is listed in the top left corner of the plug-in. Is it the case?

Best Regards,

Nick

I have the whole bundle. I can check if the other plugs are sending out clicks.
Yes, version number in top left corner is 3.0.2

[whitealbum]

I have the whole bundle. I can check if the other plugs are sending out clicks.
Yes, version number in top left corner is 3.0.2

I've tested Cool vibe, this plug are NOT sending out clicks, while Chrous/Ensemble sending out many clicks.
Mmh, special Chrous&Ensemble problem?

[Nick]

I've tested Cool vibe, this plug are NOT sending out clicks, while Chrous/Ensemble sending out many clicks.
Mmh, special Chrous&Ensemble problem?

Hello whitealbum,

Only the Chorus/Ensemble sending out clicks still.

Could I suggest that you try installing version 3.03 it has some bug fixes and improvement that just might sort out this problem.

It is here:

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

Tell me if it helps you out.

Best Regards,

Nick

[whitealbum]

Hi Nick,
i had made some mixing projects, so i'm a little bit late here
So, i'm gonna try it, and let you know...

[thesamrohdeshow]

Hey all,

Just discovered something. Forgive me if it has been mentioned, haven't read through all the other posts yet.

Running Pro Tools 11.0.1 on MBP Retina Laptop. Just upgraded 3.0.3r1 plug ins and gave them a test drive.

Mono Echoflex didn't work first time I put it on a track. So then I put a stereo Echoflex on the same track and it works but when I bypass the plugin, audio freezes on the right side and a constant annoying digital sound is audible whilst rest of track plays.

I tried the mono Echoflex again and it worked second around time, including bypass.

I have since tried the Echoflex Stereo plugin again and same problem, it works but bypass causes the freeze issues.

Thought you should know and see if anyone else has the same issue on the 64 Bit AAX platform.

Cheers,

Sam

[whitealbum]

Hello whitealbum,

Only the Chorus/Ensemble sending out clicks still.

Could I suggest that you try installing version 3.03 it has some bug fixes and improvement that just might sort out this problem.

It is here:

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

Tell me if it helps you out.

Best Regards,

Nick

Sadly, it doesn't help, same problem...

[thesamrohdeshow]

Further information to help you guys out (just read the front page!)

1- Platform (Mac or PC) - MAC
2- Exact computer OS version - Mountain Lion 10.8.4 - MacBook Pro Retina Laptop - 2.6 GHz Intel Core i7, 8 GB 1600 MHz DDR3
3- DAW sequencer with exact version - Pro Tools 11.0.1
4- Which audio interface are you using (internal sound card or external audio interface) - Internal (Built in Output)
5- Are you using third party software such as VST rappers ? Nothing third party
6- Anything else that can help our team reproduce the problems you encounter. - See above post

Thanks

[Nick]

Hey all,

Just discovered something. Forgive me if it has been mentioned, haven't read through all the other posts yet.

Running Pro Tools 11.0.1 on MBP Retina Laptop. Just upgraded 3.0.3r1 plug ins and gave them a test drive.

Mono Echoflex didn't work first time I put it on a track. So then I put a stereo Echoflex on the same track and it works but when I bypass the plugin, audio freezes on the right side and a constant annoying digital sound is audible whilst rest of track plays.

I tried the mono Echoflex again and it worked second around time, including bypass.

I have since tried the Echoflex Stereo plugin again and same problem, it works but bypass causes the freeze issues.

Thought you should know and see if anyone else has the same issue on the 64 Bit AAX platform.

Cheers,

Sam

Hello Sam,

Thanks for reporting this and doing the follow-up listing the configuration you are using.

I will pass it on to our developers so they can check it out.

Best Regards,

Nick