Plug-in Doctor Alternative For Pro Tools

[Roulette Records]

Originally Posted by Bob L

It doesn't.

Option 1a: Save a preset on the VST/AU version and hope the AAX version allows an import.

Option 1b: Take notes of the settings and enter them manually into AAX.

Option 2: Load the VST/AU version into DDMF MetaPlugin or the like and use that. Note that VST/AU metadata used for Delay Compensation is not read when you do this, you'll want to be eagle-eyed (-"eared"?).

All of this begs the question - why would you be running a diagnostic application (Plug-in Doctor) as a plugin in the first place? If the reason is to see EQ curves, surely there are plenty of alternatives that show those natively. What is your use case?

Ok, thanks, yea I will try those methods.

And I mainly want to view Compression lines and EQ curves. I looked around for alternatives in the AAX field. And there are none except Bertom Audio's free plugin. But it doesn't quite do exactly what PID does.

I'd love to find out I missed a option out there if you know of one. Basically a AAX version of PID that works normally/natively properly.

Or its possible that PID updates to do it as Bertom Audio does, where it uses a loophole to get around "loading" a AAX plugin, yet still accomplishes same thing. I am sure it can be figured out.

[Bob L]

Originally Posted by Roulette Records

<snip>
And I mainly want to view Compression lines and EQ curves. I looked around for alternatives in the AAX field. And there are none except Bertom Audio's free plugin. But it doesn't quite do exactly what PID does.

<snip>

Compression -
The stock compressor does exactly what you need for visual feedback. You already have it.

FabFilter's compressor also does what you're asking for. It isn't free. It is comprehensive. There are many, many others.

If you require the visual feedback thing, just go with those.

EQ -
The stock EQ does exactly what you need for visual feedback. You already have it.

FabFilter ProQ (any version) also does what you're asking for. It isn't free. It is comprehensive. There are many, many others.

If you require the visual feedback thing, just go with those.

Ultimately, I don't see the point (see what I did there?) of flogging yourself over a separate display plugin when so many have an integrated display. I can see why a PID-like app is useful (I have it myself) as a training aid or diagnostic tool, but the juice is just not worth the squeeze in your use case IMO.

[Roulette Records]

Originally Posted by Bob L

Compression -
The stock compressor does exactly what you need for visual feedback. You already have it.

FabFilter's compressor also does what you're asking for. It isn't free. It is comprehensive. There are many, many others.

If you require the visual feedback thing, just go with those.

EQ -
The stock EQ does exactly what you need for visual feedback. You already have it.

FabFilter ProQ (any version) also does what you're asking for. It isn't free. It is comprehensive. There are many, many others.

If you require the visual feedback thing, just go with those.

Ultimately, I don't see the point (see what I did there?) of flogging yourself over a separate display plugin when so many have an integrated display. I can see why a PID-like app is useful (I have it myself) as a training aid or diagnostic tool, but the juice is just not worth the squeeze in your use case IMO.

This reply will apply to both compression and eq:

You are right, but I guess you are not understanding what I am doing. I do own Fabfilter btw and love them ! I appreciate you chiming in on this matter, but I think you are assuming you know what my usage/desire is.

I want to analyze various plugins and their curves/characteristics that do not have that visual feedback, this way I can see exactly what they are doing and dial that in with another plugin. Mimic character in other words. (the reasons for this are waaaay to long to discuss here, but trust me I got good reasons)

I also want to analyze certain compressors to see if the ones I love which mimic some hardware, which therefore do not have the visual lines are doing what I need them to do in *certain* instances that are more critical surgically. So I know what I need to see, not hear in this rare case. Its rare to say that as I work the other way really.. hear, not see. lol

Basically I am experimenting in areas that will take way too long to describe here in text. lol PID is more for that for me than simply wanting to see lines. Its for fun and diagnosis to then help with actual things later.

Another big reason is to discover what *exactly* the "insert switch name here" does on "insert plugin name here". (like the Air Switch, which is obviously some EQ curve). This way I can mimic that with another plug when I want what the switch does and not the whole plugin and the plugin insists on doing other things as well or I got my hands tied due to circumstance (wanting half as much air switch but all the other stuff in that plug or something like that). Etc.. there are tons of examples I could give.

I also heard you can analyze hardware ? That sounds ridiculously fun (and helpful), but not sure how I set it up to do that yet. I seen it done in a video though.

Is it necessary for my existence ? No. Do I want to do it to help me later ? Yes. Have I tried to ignore this, yet still get reminded every so often that I eventually need to do this to help with this or that approach/workflow ? Yes. So enough is enough, I gotta try it.

And the biggest reason for my post was simply to talk about how ridiculous it was to come up with a AAX version that doesn't really help me as a AAX user. NOT whether I should use it or not or if I know what I am doing or not.

[Bob L]

Fair enough.