New bifurcated realtime and render oversampling modes, and expansion of oversampling multiples from the previous universal 8x to now realtime up to 16x, and render up to 64x!





Available right now in version 3.8 of DDMF Metaplugin!!!!

https://ddmf.eu/metaplugin-chainer-v...s-aax-wrapper/

These changes were brought to us from a request I made to DDMF because of the “Testing Aliasing of Plugins (measurements)” GS thread, and I am very appreciative for it!

Testing Aliasing of Plugins (measurements)

Please support this dev if you haven’t yet!

So as I wrote in that other thread, I will need to get confirmation, but I believe the oversampling multiples are still based on our project sample rate, so that can require some care when using realtime oversampling at higher project sampling rates.

Just keep in mind, if we have a crash when oversampling, it’s because we are probably pushing the plugin we are trying to oversample too hard for its design.

For example, if the plugin already has some type pf internal oversampling that we don’t already know about, it will likely croak or crash when pushed maybe even as low as 4x.

So with this great expansion of this tool, we also bear some responsibility to not blame this dev for these types of crashes, which are essentially the laws of computed physics biting us if we push them too hard.

.. not only that, I don't think many plugins officially support more than 384kHz sample rates.. many of them not even past 192kHz, and in the case of Acustica Audio, I suspect 96kHz is the max (may be wrong here though, the internal resampler may allow higher rates).

So yeah, while this is a welcome addition, it will probably lead to a lot of issues and confusion.

A quick graph load (graph browser - like plugin browser to the left) would be a MASSIVE improvement.




.

In terms of user interface / UI, this thing could be a LOT better. I've been hoping for a few years that it'd be completely overhauled and actually take usability into account but nothing of the sort has happened, unfortunately.

I wish we could hide/toggle off the virtual cable volume popups. They frequently get in the way. I wish there was simple click+drag way of copying modules/plugins. Etc.etc. It could be vastly improved in every aspect but unfortunately I don't think this plugin seems to be a top priority which I can understand. I suspect only enthusiasts purchase it, probably mainly for the oversampling.

Maybe version 4 will finally be the complete UI/usability overhaul that it needs? Would love to use this as my main modular design/experimentation thing but it's simply too frustrating and simplistic in terms of UI and usability to be that.

I’m not sure what “official support” really means.

If it means aliasing, then it means a different result at different “supported” project sample rates, every time.

My testing has proven this “sample rate support” to be baseless in most cases.

It means that some plugins can have internal coding / components in such a way that they do not perform optimally, or not at all correctly, at any samplerates that are higher than what they state as supported.

For instance, older versions of various Guitar Amp emulation software that included impulse responses sometimes failed to correctly internally resample the impulses and would thus sound completely different depending on the users sampling rate.

Thus lets take an example; A Guitar Amp software says that max supported sample rate is 192kHz. Now what happens if you do 16x oversampling within that kind of software and it doesn't resample the internal impulse response? You get a "mickey mouse" effect.. just like with any sampler. Basically the impulse is played through extremely fast and thus the cabinet emulation of such software would sound completely wrong.

This is just one example. There are many more internal issues that could arise in plugins when you go past their intended sample rates.

Luckily, this is usually not the case for most simple things like EQs, compressors etc. but with more complex things like VST instruments and anything containing samples and impulse responses, you may run into trouble.

I do only use this for oversampling. In fact I wouldn’t mind if that was all this did.

But this program is constantly being updated as far as I can tell from the fact that there is always a new version whenever I check each month, and I literally made this request less than a week ago, and here it is, so it seems to me that Christian is very open to polite requests from my experience.

I've had Metaplugin since version 2 came out. Yes, while small improvements can sometimes be made, Christian has not implemented any of my usability suggestions, not even the seemingly basic ones (like "box select" of modules so that you can move them all at once) over the years.

He did mention, like over a year ago, that the next major version would concentrate on usability and try to use more modern UI.

So… using our ears to make the distinction whether it works or not?

Can we not humbly request that of the users of this plugin?

Yeah, some synths will sound whack with oversampling, but if they are aliasing, and thus having different results at different “supported” project sample rates, how are they not considered as sounding whack already?

Well I am hoping for the best for you, but I don’t really think it deserves to be dragged since it isn’t exactly what you want just yet. I do hope Christian takes some notes on your requests.

But, this oversampling capability is killer right now.

I don’t know of anything that comes close for the number of plugins this can greatly improve (especially saturators) other than the global oversampling options in Melda plugins.

And I should not leave out that the quality of this oversampling is a step above what is used within some plugins, usually older and/or relying on OS options in crusty development frameworks.

.. apparently quite a few people have decided to use their eyes instead of ears lately, so it might be a bit too much to ask from most.



Agreed, the oversampling is even more useful now.

I also did buy this mostly for the oversampling back in the day (and for being able to open varying formats within one plugin, this is super useful!), but now I also use it for some complex mid/side and sidechaining setups. Dealing with a bunch of plugins within one window without any basic usability features is indeed quite frustrating.

I requested that the the LOGO name in the center of the GUI be aloud to dim !

Sometimes it gets in the way of seeing connections.

It would also be helpful if there were a Keyboard modifier [Shift, Cntrl, Alt, etc] that would make multiple connections, instead of one at a time.

[ex: Stereo out --> Stereo Input of the next module.

SO TRUE !

Well, the DUPLICATE function DOES work... (although is would be nicer to Alt+Drag)

I have had it confirmed that the oversampling remains a true multiple of our current project sample rate.

Thx for this information, i'm trying to upgrade but dl don't start for some reasons. Seems to have a bug somewhere. Hope that could be fix soon, that new search feature interrest me a bit and could be handy.

Wow, I hope that works for you soon.

I just did an example from no oversampling to 16x over here:

Testing Aliasing of Plugins (measurements)

Can anyone describe a metaplugin workflow for oversampling Melodyne?

Does it even work when a plugin has to capture audio? Presumably ARA is a non-starter.

Melodyne really f*cks with a vocal at less than 96k so would be useful/quicker than flying lower sample-rate vocals into an upsampled session etc

Thx for yours tests. They seems very interresting even though i'm not really into the anti-aliasing/oversampling things subjects.
The download still don't happen for me using firefox and chrome unfortunately. Strange!

Edit: The download finally works! The search feature is really welcomed and those who are into oversampling will be surely happy.

Great update. But PLEASE!!! For the next update...allow the space bar to be used for play/stop when the plugin is open from within metaplugin. It is a SERIOUS workflow killer to have to either click back to the metaplugin window or the daw itself.

Hi to all,
I am using metaplugin in Sound Forge to run Altiverb 7. The weird thing is that even when I use it in the most basic configuration: Audio input (left and right) to Altiverb and from there to Audio Output (left and right) but I get a sound as if I would put the altiverb with a double mix (wet) that I am actually using.
Could someone help and tell me what I am doing wrong?

Hi folks!
Hopefully this isn’t a stupid question... interested in your takes.
How is everyone using Acustica/Nebula with metaplugin? Specifically when oversampling?
I assume 2x oversampling is the max that can be done because the sampling ceiling is generally 96k..
In nebula, if I’m working in 44.1 and I use 2x oversampling in metaplugin, should I be using the 88.2 nebula libraries? I assume the answer is yes, but interested to hear how everyone else is doing it.
Cheers all.

I don't know, but I think you use anotjer sampled library, you just oversample nebula library with its own sample rate. So, you choose 96kHz sampled library and oversample it with 8x, so you get 96k*8....8 times less aliasing should be there. But i don't know how nebula libraries with its own sample rate behave in oversampled domain. Theoretically, aliasing should be less, but you still use "its own sample rate" impulses, but in oversampled domain. Complicated, but theoretically this should work this way.

Interesting. That would be pretty useful if thats the case. I'm trying to abuse the TimP LA2A and avoid as much aliasing as possible.
Because we're dealing with "samples" and not algos, I wondered if oversampling too much could mess up what the acustica/nebula plugins are doing, ie. filters cutoffs, Q factor, compressor speed etc.
Has anyone out there done any tests on extreme oversampling with Acustica tech?
I'd also be interested to know what happens if say you open up an Acqua in a 192k session for example. Would it be downsampling to 96k and then back again? Also, do Acqua and Nebula deal with SRC the same way?

Great update. Love this plugin company.

This is correct. If you are at 44.1kHz and oversample to 2x oversampling, then you should use 88.2 libraries. In N4/N4 Player you can easily see the sampling rate mentioned. The Aqua libraries will choose themselves the correct rate library but I do recommend having the 88.2kHz libraries installed.

Also, make sure when you load Metaplugin that you first engage the oversampling and only then load in a Nebula/Aqua plugin. Otherwise they will not load up the correct libraries/sampling rate.

I've tested this and indeed, Tim Pethericks "any sample rate" programs, the compressors, work at up to 8x oversampling. Possibly even x16 but I can't confirm that as my computer just isn't fast enough to do it realtime and I'm too lazy to render a bunch of test files.

Not sure how accurate the programs are at these high sampling rates but who cares, they sounded awesome!

This is a pretty cool update.
I was wondering what was randomly crashing metaplugin on the 4x OS setting. I'm guessing one of the plugs must have already been OSing and this pushed it past its limit. I'm in Cubase, but within the DAW or otherwise is there a reliable way to tell if there is OS and at what rate in a plugin?

I'm working in Ableton on a Mac and every session crashes the second time I either freeze or export a track, if I do have an instance of metaplugin in my session. Does anybody else have this same issue? or know a way to solve this issue? It's really weird since it works to freeze and export the first time you do it, but the second time it fails...

I am getting some pretty random latency behaviour from this. Anyone else? Pressing the PDC button several times and it jumps between values and doesn't settle. Maybe I'll actually read the manual

EDIT: lol...classic.....I guess I'll try without touching the pdc button then.....

I've got some issues with Decapitator oversampled in Metaplugin.

When on X4 oversampling (real-time and offline), the plugin doesn't pass audio when you reopen the session.
When on X2 oversampling, I had a very strange issue on one project, each time I recalled the session : Decapitator was outputing a very nasty noise (kind of extreme destruction of the source) until I reset the oversampling on X0 (an then again on X2 during the mixing session).
While I run Live everything is working fine, until I save, close, reopen the session and find the same issue.

I didn't try to export yet.
I'm using the VST last version in Ableton Live 10.1.30 on Mac Mojave...

It seems to work fine with other plugins (but to say the truth, I'm using Metaplugin almost only for Soundtoys plugins).

Anyone did have the same issue ?

By the way, what about the latency compensation ?
I've got the same problem as Karloff70, but I still didn't understand the point...