DDMF Plugindoctor

[Greybox Audio]

it'd be great, if there was a way to either store multiple snapshots, or to be able to instantly switch between multiple plugins without having to close and reload them.

I don't have plugindoctor yet and someone will correct me if i am wrong but i swear i saw at gearslutz someone posting how he is able to do just that! Store snapshot from one plugin then recreate EQ curve with another plugin within Plugindoctor. Kinda like he had layered pictures one bellow another all inside plugin doctor. That way he was able to clone plugin curves and compare different plugins. Apparently there is a snapshot feature it's just not obvious.

Again don't take me for real maybe i got wrong info but that was impression i was getting.


edit: yeah it's here if that is what you are looking for:

https://www.gearslutz.com/board/showpos ... tcount=182

Thanks for the link. I've been using plugindoctor to compare and 'copy' EQ curves with snapshots, too. By 'multiple snapshots' I meant 'more than one' . As a workaround I've been using metaplugin and minihost (from Image Line) to switch between multiple plugins on the fly.

[kmonkey]

Thanks for the link. I've been using plugindoctor to compare and 'copy' EQ curves with snapshots, too. By 'multiple snapshots' I meant 'more than one' . As a workaround I've been using metaplugin and minihost (from Image Line) to switch between multiple plugins on the fly.

No problem. Btw I have metaplugin. Could you describe procedure a bit more. I might try it in the future.

Cheers

[mcbpete]

Having issues using v1.0.8 to test PluginAlliance/Vertigo VSM-3 ( https://www.plugin-alliance.com/en/prod ... vsm-3.html ) - As soon as I click Load Plugin and select that VST (Windows x64, VST2) the program closes. There's no error message or any hanging, just an instant close. Anyone else able to repeat this test ?

[Niowiad]

Some plugins seem to have some sort of incompatibility with PluginDoctor right as they're loaded.

In my case, AudioAssault's HeadCrusher makes it crash sistematically.
My other plugins from AudioAssault have no problem with PluginDoctor, and the same goes for 99% of my plugins, as far as I've been able to see.

Extremely satisfied with PluginDoctor, overall...

[teacue]

Having issues using v1.0.8 to test PluginAlliance/Vertigo VSM-3 ( https://www.plugin-alliance.com/en/prod ... vsm-3.html ) - As soon as I click Load Plugin and select that VST (Windows x64, VST2) the program closes. There's no error message or any hanging, just an instant close. Anyone else able to repeat this test ?

Just tried with version 1.0.8 to load Vertigo VSM-3.
Both version VST3 and VST2 64-bit load correctly.
I use Windows 10

[mcbpete]

How strange - Thanks for testing though, I wonder what's causing mine to instantly bomb out ?! (I'm on Win10 as well)

EDIT: Just trying it out this evening and pretty much every PluginAlliance plugin causes it to instantly close - Tried about 20 of them and the only 3 that were successful in loading were Dent, Fault & Sandman

[Greybox Audio]

Love the new update The new 1.0.6 Version of kush Omega N also doesn't crash anymore, when I try to load it in PluginDoctor.

[Greybox Audio]

Why does every new Waves plugin crash PluginDoctor? (For the record: I'm blaming Waves!)
On a positive note: really like the new option to disable automatic plugin loading on startup

[jbarish]

Why does every new Waves plugin crash PluginDoctor? (For the record: I'm blaming Waves!)
On a positive note: really like the new option to disable automatic plugin loading on startup

I didn't think it was possible to test Waves plugs in Plugin Doc because they're not individual plugins??
How do you do it??

Thanks,
jb

[KVrigf]

Using Blue Cats Patchwork is a good workaround for plugins that would otherwise crash PluginDoctor.

I have to use that to look at any IK T-racks plug ins.

It is nice being able to load a handful of plugins and quickly a\b eq, saturation, attack/release curves and stuff.

[lfm]

Why does every new Waves plugin crash PluginDoctor? (For the record: I'm blaming Waves!)
On a positive note: really like the new option to disable automatic plugin loading on startup

Is it because it does not support Waves at all, or?

Metaplugin from DDMF never supported Waves. You could get away with loading some, but later create issues.

[Greybox Audio]

Why does every new Waves plugin crash PluginDoctor? (For the record: I'm blaming Waves!)
On a positive note: really like the new option to disable automatic plugin loading on startup

Is it because it does not support Waves at all, or?

Metaplugin from DDMF never supported Waves. You could get away with loading some, but later create issues.

Been using PluginDoctor since release and it loads Waves plugins just fine. You load the WavesShell and then it lets you choose from your installed plugins. Sure, there's a crash here and there but it's surprisingly stable MetaPlugin seems to work also pretty well with Waves. I use it if I want to compare multiple Waves plugins in PluginDoctor.

[jbarish]

Why does every new Waves plugin crash PluginDoctor? (For the record: I'm blaming Waves!)
On a positive note: really like the new option to disable automatic plugin loading on startup

Is it because it does not support Waves at all, or?

Metaplugin from DDMF never supported Waves. You could get away with loading some, but later create issues.

Been using PluginDoctor since release and it loads Waves plugins just fine. You load the WavesShell and then it lets you choose from your installed plugins. Sure, there's a crash here and there but it's surprisingly stable MetaPlugin seems to work also pretty well with Waves. I use it if I want to compare multiple Waves plugins in PluginDoctor.

Thanks for the tips!

[lfm]

Why does every new Waves plugin crash PluginDoctor? (For the record: I'm blaming Waves!)
On a positive note: really like the new option to disable automatic plugin loading on startup

Is it because it does not support Waves at all, or?

Metaplugin from DDMF never supported Waves. You could get away with loading some, but later create issues.

Been using PluginDoctor since release and it loads Waves plugins just fine. You load the WavesShell and then it lets you choose from your installed plugins. Sure, there's a crash here and there but it's surprisingly stable MetaPlugin seems to work also pretty well with Waves. I use it if I want to compare multiple Waves plugins in PluginDoctor.

Yes, that is what we want - instability.

As you said, despite what manual said about Metaplugin in my case(not supported says manual), it loaded and built a menu and stuff for use next time. All seemed dandy.

Then extreme loading times(which might depend on how many products from Waves you have) and sometimes just freeze daw loading a project.

New update of Metaplugin, and old presets froze daw. Not quite compatible it seems.

Just to load and compare stuff, sure, but as regular part of project I would not risk it. There are so many other ways to do that.

Note, I have not used PluginDoctor, this is all my experience with metaplugin. I use Patchwork with no such flaws at all.

[bbaasszz]

... but 3) the Arturia had much aliasing than the Slate. In fact, all three Arturia preamps had very interesting things in terms of their frequency response and above average aliasing performance. So I ended up buying them, and I'm using the Slate plugins less.

Hi, did you mean to say "much less aliasing for Arturia?" Given it seems like you prefer Arturia rather than Slate in this case.