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

[Nick]

Sorry I should have made this clearer. This is the first thing the installer does, before I even get to pick any installation location.

Hello weezul,

Is there any way that your drive: W has priority over the drive that has the system and the correct ProTools folders?

What happens if you re-install and force the installer to place the files on the right drive?

Best Regards,

Nick

[whitealbum]

Thanks

any news about the click problem for chorus ensemble?

[runescapegold666]

We heard of that but weren't able to reproduce up to now... Actually, we have been able to reproduce it but only on Mac running Windows under Parrallel...
cheap fifa 14 coins
buy fifa 14 coins

[Nick]

We heard of that but weren't able to reproduce up to now... Actually, we have been able to reproduce it but only on Mac running Windows under Parrallel...
cheap fifa 14 coins
buy fifa 14 coins

Hello runescapegold666,

Don't really understand your comment here, could you explain it better?

Best Regards,

Nick

[Ry-Fi]

Hey Nick and gang,

I've got another one to report (OS X 10.8.4, Pro Tools HD 10.3.7, P&M 3.0.3r1 AAX). I'm not sure if it's accurate to call this a bug per se, but it's definitely non-standard behaviour:

When editing automation for a plug-in's parameter, the current value is supposed to be displayed the entire time you're adjusting an automation point, so if for example you're clicking and dragging a point around, or trimming a line or selection up or down, there's a reading that shows the current value as it's updated in real-time. Every plug-in I've ever used on PT implements this behaviour.

P&M plug-ins do not do this. They only update and show the current value once you've quite editing, ie. released the mouse button.

This is actually incredibly frustrating as fine-tuning a value involves several repeated edits due to the fact that you don't know what the current value is and you have to guess repeatedly until you hone in on the desired value.

I hope this can be remedied in the next release. I'm making solid use of a bunch of your plug-ins on a big album mix I'm doing, but their rough edges compared to the rest of the RTAS/AAX crowd are definitely making me wince. I hope your devs can really flesh out all these little problems and get the P&M bundle up to perfection. (As I software dev myself, I both understand and yet hold you to the highest standards )...

Ryan

[Nick]

Hey Nick and gang,

I've got another one to report (OS X 10.8.4, Pro Tools HD 10.3.7, P&M 3.0.3r1 AAX). I'm not sure if it's accurate to call this a bug per se, but it's definitely non-standard behaviour:

When editing automation for a plug-in's parameter, the current value is supposed to be displayed the entire time you're adjusting an automation point, so if for example you're clicking and dragging a point around, or trimming a line or selection up or down, there's a reading that shows the current value as it's updated in real-time. Every plug-in I've ever used on PT implements this behaviour.

P&M plug-ins do not do this. They only update and show the current value once you've quite editing, ie. released the mouse button.

This is actually incredibly frustrating as fine-tuning a value involves several repeated edits due to the fact that you don't know what the current value is and you have to guess repeatedly until you hone in on the desired value.

I hope this can be remedied in the next release. I'm making solid use of a bunch of your plug-ins on a big album mix I'm doing, but their rough edges compared to the rest of the RTAS/AAX crowd are definitely making me wince. I hope your devs can really flesh out all these little problems and get the P&M bundle up to perfection. (As I software dev myself, I both understand and yet hold you to the highest standards )...

Ryan

Hello Ryan,

I know what you are saying here.

I was playing with Ultramaxit the other day and doing the fine tuning on a mix.

And it was a bit of pain not seeing what the values were that I was adjusting.

But as I was listening very carefully, and to do that I closed my eyes.

Although I am in the business of defending plug-ins, the fact that it has become very "visual" I feel it is counter productive.

Quite often when adjusting a EQ for example, I do not look at it, I do it by ear.

And when I see where the levels and curves have ended up, it is a bit a of shock, (yes I have to peek from time to time to make sure I'm on the right parameter).

All this is not to defend an oversight on our part, I have already passed on the info to our developers, it is just to say there was a day when all those buttons didn't mean a thing, it was just whether it made it sound better (or worse) ;-)

Best Regards,

Nick

[Ry-Fi]

Hello Ryan,

I know what you are saying here.

I was playing with Ultramaxit the other day and doing the fine tuning on a mix.

And it was a bit of pain not seeing what the values were that I was adjusting.

But as I was listening very carefully, and to do that I closed my eyes.

Although I am in the business of defending plug-ins, the fact that it has become very "visual" I feel it is counter productive.

Quite often when adjusting a EQ for example, I do not look at it, I do it by ear.

And when I see where the levels and curves have ended up, it is a bit a of shock, (yes I have to peek from time to time to make sure I'm on the right parameter).

All this is not to defend an oversight on our part, I have already passed on the info to our developers, it is just to say there was a day when all those buttons didn't mean a thing, it was just whether it made it sound better (or worse) ;-)

Best Regards,

Nick

I appreciate what you're saying, and believe me, my ears are always the final say in every single mix decision and microscopic tweak I make. Still, as you acknowledge, this doesn't absolve your plugins from needing to behave consistently to all the other plugins with the correct behaviour.

And part of it's an OCD thing too. My sessions are incredibly and meticulously structured and I try to adhere to consistent best practices. When I draw automation and I want a section to maintain a steady value, I want to be sure the endpoints have the same value -- I can't stand a slightly uneven line with a slow value creep - it drives me nuts! Having said that, I know that there are key commands for adding an automation point with the same value as the one prior or after... but the point I'm trying to make is that I consider the visual, organizational, informative aspect of a huge complex mix to be an important factor. Numerical value displays are a part of this and I expect them to be accurate and behave properly.

I realize my feelings might be a bit extreme on the issue, but others with the same level of OCD-like behaviour are surely nodding in agreement right now.

Thanks for addressing the issue, of course!

[weezul]

Hey guys,
Just to mention, I recently migrated from a PC install of Pro Tools to a Hackintosh install. Everything works great, apart from now when I open old sessions, they claim any PM plugins are missing. However, they are there in the list if I replace them. However, this isn't really any use as I loose all the plugin settings!!!

I was using 32bit AAX on windows on these sessions, and now i've installed RTAS and AAX on the MAC and I still get sessions that I open, where the PM plugins are called 'missing'. Is there some sort of naming convention that is not the same between PC and MAC builds of PM plug ins?

Thanks

Also, in response to my previous post about not being able to install due to mapped network drives, I fixed that with a registry tweak. Damned if i can find it now though!!! Loving Hackintosh too much right now

[Nick]

Hey guys,
Just to mention, I recently migrated from a PC install of Pro Tools to a Hackintosh install. Everything works great, apart from now when I open old sessions, they claim any PM plugins are missing. However, they are there in the list if I replace them. However, this isn't really any use as I loose all the plugin settings!!!

I was using 32bit AAX on windows on these sessions, and now i've installed RTAS and AAX on the MAC and I still get sessions that I open, where the PM plugins are called 'missing'. Is there some sort of naming convention that is not the same between PC and MAC builds of PM plug ins?

Thanks

Also, in response to my previous post about not being able to install due to mapped network drives, I fixed that with a registry tweak. Damned if i can find it now though!!! Loving Hackintosh too much right now

Hello weezul,

This is perhaps not a Hackintosh problem, but a ProTools not finding the info coming across from the Windows sessions.

Try this (excuse me if you know this already)

When you save the Windows ProTools session do a "save copy in" and make sure to include the "session plug-in setting folder" and "root plug-in setting folder" from that session.

Then ProTools will have some info to retrieve that should help the Plug and Mix to find the settings that were used on the Windows sessions.

Hopefully this will help you out.

If it doesn't there might be a "permissions" problem that occasionally manifests itself on Macintosh.

Best Regards,

Nick

[weezul]

Hello weezul,

This is perhaps not a Hackintosh problem, but a ProTools not finding the info coming across from the Windows sessions.

Try this (excuse me if you know this already)

When you save the Windows ProTools session do a "save copy in" and make sure to include the "session plug-in setting folder" and "root plug-in setting folder" from that session.

Then ProTools will have some info to retrieve that should help the Plug and Mix to find the settings that were used on the Windows sessions.

Hopefully this will help you out.

If it doesn't there might be a "permissions" problem that occasionally manifests itself on Macintosh.

Best Regards,

Nick

Thanks for the tips! Repair permissions diddn't seem to help.

I don't have my original Win7 boot any more, and there's only one session which I really needed them for. That band were threatening to come back with a fiddle player for some revisions, but it seems like they've got new material now. Recall works fine on sessions that started on the mac. If I ever get round to sorting out my Win7 partition I will let you know if it works.
Thanks again for the reply

[Nick]

Thanks for the tips! Repair permissions diddn't seem to help.

I don't have my original Win7 boot any more, and there's only one session which I really needed them for. That band were threatening to come back with a fiddle player for some revisions, but it seems like they've got new material now. Recall works fine on sessions that started on the mac. If I ever get round to sorting out my Win7 partition I will let you know if it works.
Thanks again for the reply

Hello weezul,

In the olden days, when this stuff happened a lot, I always "winged" it by saying I had found a way to "improve" the sound by re-doing the effects settings it they had got bunged up or lost for some strange reason. Usually worked

Best Regards,

Nick

[weezul]

Hello weezul,

In the olden days, when this stuff happened a lot, I always "winged" it by saying I had found a way to "improve" the sound by re-doing the effects settings it they had got bunged up or lost for some strange reason. Usually worked

Best Regards,

Nick

classic!

[Nick]

classic!

Yes, it is like the effect that the clients ask for that you never heard of, you put in an obscure plug-in, put in bypass, push it the fader so the track is a bit louder, and they tell you "that's is exactly what was needed".

Best Regards,

Nick

[deepho]

The Chorus Ensemble and Cubase bug (click-spike) are still not solved!

Cubase 7 and 7.5 64bit both on Windows 7 64bit.
When we can expect an update?

Cheers

[Nick]

The Chorus Ensemble and Cubase bug (click-spike) are still not solved!

Cubase 7 and 7.5 64bit both on Windows 7 64bit.
When we can expect an update?

Cheers

Hello deepho,

I talked about this again to the developers and they asked me for a bit more information about your set-up as there has been some other cases they have solved by investigating the configuration.

Here are some details that would be helpful to track this down.

1/ Is your PC an i5 or i7 processor?

2/ How much ram do you have?

3/ What is the buffer size you are using in your Cubase?

4/ What audio interface are you using? And how does it connect to the PC? USB? directly to an audio card? which audio card?

Please send us along these details so we can really get a clear picture of what the problem could be.

Best Regards,

Nick