Thanks mate, I did exactly the way you do.
It works correctly on any parameter belonging to the wrapped plugin but it just doesn’t on the MP wet/dry control.

I dont own Metaplugin yet but it looks like I will be needing it to run a few plugins soon.

Can someone please confirm that level overs between plugins within metaplugin are passed without clipping?

In other words, overs leaving one plugin inside Metaplugin can be perfectly restored using the following plugin.

Just need to be sure before buying. Thanks

I can set up a test if you like and check for you.. (not sure exactly how). But probably best is to try with the fully functional demo by yourself as there could be some problems depending on your host.. (for ableton the au and vst3 don’t work as intended but vst2 runs flawlessly)

Cheers

Thanks, you're right, I will just take the time to demo. I need plugins that have occasional overs to pass signal without clipping. Im almost positive Metaplugin does this using 64 bit processing, but need to confirm before critical use. Cheers

Just throwing it out there to anyone from DDMF who may be reading this. Take the oversampling piece of code and make that it's own standalone plug. One where the input/output nodes don't need to be setup, and the space bar works while manipulating plugins from within the wrapper. You would make money hand over fist from all of us aliasing jerks out there

I agree. I mostly use Metaplugin for the oversampling, and wouldn't mind a more streamlined "OS Only" version, without the complex routing setup.

According to a developer who responded on KVR, the admin on plugin compatibility in such a utility would make in unfeasible. They suggested an opensource, community-driven type project with lots of testers.

I feel like there's a huge gap in the market right now for this function.

Reaper just recently updated with built-in mixer channel oversampling options, by the way... Ultimately that is the best solution: Native to the DAW itself.

I think it will be alright as it is 64Bit as you mentioned.. let us know what you think about the os!

There should be a new product thread for this, but DDMF released Metaplugin 4 today and it wraps VST2 and VST3 Intel to Native Silicon!

Hi All

Does anyone here understand how to set a custom PDC in Metaplugin ?

I'm running the last version and I try the feature for the first time, but I can't make it work. Each time I set a custom PDC, it comes back to zero (or whatever PDC is reported by the plugin chain I use).

I need the feature so I can bypass the Guitar Rig 6 issue with invisible latency not reported to the host...

EDIT : strange. After some more trying, it works. But the first attempts were not successful. I don't understand what happened.
Maybe the feature could be enhanced so the user understand better what happens...

New to metaplugin here.
Seen a few of the posts about the lacking ease of use. I concur!
Disappointed to find out that the pop up level knobs have been replaced by a manually inserted knob. Which means having to unplug everything and re attach with the knob in between all the lines? What am I missing here? That's a nightmare!
And the logo in the middle of it all. Edit: it ain't even a logo just a crap font getting in the way. Please!

Since i am reaper user and reaper added oversampling option i gave up on metaplugin altogether and now use reaper's oversampling.

9 months ago I bought Metaplugin. It never really worked for me, constantly hanging and preventing logic projects from opening.

I assumed this was because I was using an old OS and didn't kick up a stink about it. I knew I'd be updating soon so I just waited until I did, expecting it to work properly when eventually that happened.

I recently got a new computer and a current OS, installed Metaplugin but after scanning my plugins most of them do not appear in the library within Metaplugin.

I've written to support many many times over the course of 2 months or so and received basically no help whatsoever, I'm just being ignored.

I feel absolutely robbed. They've taken my money and provided a product that has never worked and never will and they think that's acceptable.

Can you give more details? Are they VST, VST3, AU, etc. Is yo9ur computer an M1? Can you share a sample of detected and undetected plugins?

BC Patchwork stores the plug in window positions with the patch.
Also, it simply opens and closes the plug in windows when the Patchwork gui is selected.
This is a much better workflow than Metaplugin where all the windows open up in a random place every time a patch is loaded, forcing one to re arrange them all, and going to the menu to open and close all plugin windows.

Why Can't Metaplugin do this?

Edit: both plugins need a way to grab all plug in gui's simultaneously.

Metaplugin was a waster of money i am gonna stay away from the other plugins and i believed in these guys but they seem to not be interested in improving their plugins.

Following the update in Summer 2022, how are people getting along with this? Does anyone here use AudioGridder instead?

I've been looking for a plugin that could host multiple sidechain inputs in Pro Tools (PT only allows one mono sidechain input) and use them on differing sides' plugin chains. Metaplugin is the only one I found that works as intended, and it seems to work very well there, hosting up to 128 different sidechain inputs (though I've only tried 3 on one track: Left, Right, and Middle).


But I see some of you have complaints with the current version of Metaplugin. So far in my trial, I've gained some: No always-displayed Toggle Bypass (have to open menu), the Mix control doesn't show a percentage, no option to "apply to all" when cancelling scanning certain plugins that take too long....... And I'm just now seeing that all of my settings didn't recall when reopening PT (I knew presets didn't save in Trial, but not this)


So with that, how easy do you find it to work with Metaplugin regularly? Are there are real concerns when it comes to the sound or the functionality of the plugin? I see some complaints about freezing your DAW, but I haven't had that with the Trial eut. VERY close to buying this

Only 5 days and a ton of bugs in Metaplugin. The current main bug is that the PDC (delay compensation) is totally unreliable and changes randomly. And if I set it to a manual amount, it shows the amount I set up until I press Play and it automatically switches to a different amount.

It is NOT my manual amount + the real amount as someone has suggested elsewhere. It shows me 2371, and on a few other tracks with the exact same settings it is more or less the same. So I set them all to 2400 so that they're aligned. But every time I press play each track's PDC is set to a new number, and none of those numbers are the same.

I also get various routing, oversampling, plugin loading, settings recall, and latency bugs. I am this close to demanding a refund.

Hi guys I haven't used any plugin wrappers before and I'm intrigued. Can Metaplugin wrap ancient 32bit TC Powercore plugins? Will it be stable and usable?

Hi! I can see peeps are already dissing PDC, but what I wonder is if I build a setup and make myself a dry-wet routing inside the plugin, whether it'll delay the output of the dry signal to match the delay added by whatever is being processed.

I've not seen any sample delays as optional modules, so it leaves me thinking about what happens whenever anything is routed in parallel inside the structure.

Just an update, running Metaplugin 4.4.0 running in Logic 11.1, Mac OS Sonoma, PDC is solid. Both internally and across tracks, the explanation on the manual does hold true (as long as you're using only one stereo out, you're fine).

Was a bit interested in Metaplugin but I don't need to consider it anymore since they use Fastspring for payments and that payment service won't let me pay. No idea why, I've paid for some 10 or so plugins from various countries the last few days but with Fastpring I went to a full stop.

Sorry if this was addressed in the thread, I didnt have the opportunity to read through it.

When using Metaplugin in Pro Tools does it the report latency as well as compression and eq curve of the wrapped AAX plugins to Pro Tools ?

I do want to use this for oversampling purposes but if it doesn't report latency that's gonna be a issue.

I don't know about ProTools, but it actually reports latency in Ableton Live.

Thats awesome thanks for the report.

After reading the manual I discovered that it handles delay compensation internally so I guess its a non-issue after all. Still curious if it reports info to pro tools meters though.