Serum 2

[teilo]

The Serum AU component is still just a bl@@dy VST wrapper.
Just lame.

That's true of nearly every developer who is not using JUCE or some open source equivalent. They develop to one plugin format and wrap. For example, u-He. They used to develop to VST2 and wrap. Now they develop to CLAP and wrap.

[martinjuenke]

It‘s the only dev in my portfolio who is not able to provide a proper AU component.
If I could sell Serum I would do it just for this reason. Enough competition on the market.

[jules99]

I'm waiting for Serum 3

[stoopicus]

It‘s the only dev in my portfolio who is not able to provide a proper AU component.
If I could sell Serum I would do it just for this reason. Enough competition on the market.

Honestly asking - why do you care what plugin API they primarily develop for? Minimizing the work required to support multiple formats is simply smart and I would actually be surprised at any who didn't abstract it in some way. So what's the problem with that abstraction layer being, simply, another plugin format they primarily develop for?

This just seems like a good practice to me and I would actually question any developer that did not do this.

[tumface]

The Serum AU component is still just a bl@@dy VST wrapper.
Just lame.

That's true of nearly every developer who is not using JUCE or some open source equivalent. They develop to one plugin format and wrap. For example, u-He. They used to develop to VST2 and wrap. Now they develop to CLAP and wrap.

There's nothing wrong with doing this. You can add as much extra functionality into a DLL/.vst3/.clap as you want, and have the wrapper tap into it when adapting it. For example, you could make your CLAP version have the VST3-specific note expression stuff within it, and when the VST3 wrapper loads the CLAP .dll internally, it can tap into the VST3 stuff, even though the CLAP version has no use for it because it has its own separate note expression handling.

In fact, if you ship a plugin this way, it can waste less disk space and prefetch/caching resources, since you only need 1 copy of the actual executable code.

[martinjuenke]

It‘s the only dev in my portfolio who is not able to provide a proper AU component.
If I could sell Serum I would do it just for this reason. Enough competition on the market.

Honestly asking - why do you care what plugin API they primarily develop for? Minimizing the work required to support multiple formats is simply smart and I would actually be surprised at any who didn't abstract it in some way. So what's the problem with that abstraction layer being, simply, another plugin format they primarily develop for?

This just seems like a good practice to me and I would actually question any developer that did not do this.

Because I delete all AAX, VST and VST3 files from my system to keep my hard drive as sober and unpoluted as possible.
Most developers give me the option to exclude these formats during their installation process. Bravo!
Others do not provide this option (shame on you Softube, UAD, Waves and a couple more) therefore I have to clean up their garbage afterwards with a specific program.
This procedure saves me GigaBytes of hard disc polution with all its side effects.

[stoopicus]

So, for Serum… don’t do that? Just this once?

[martinjuenke]

So, for Serum… don’t do that? Just this one?

Yes, it needs the VST file.
Otherwise you have a black screen.
As I said: lame.

[stoopicus]

Dynamically loading the VST from a tiny AU wrapper like that is one option that isn't super rare.I would just consider the pair a single plugin in cases like this and forget about it. You're only paying a very small incremental cost and this is a smart way to do it for the devs. You wouldn't really save anything truly meaningful if they compiled it into a single unit.

[martinjuenke]

Dynamically loading the VST from a tiny AU wrapper like that is one option that isn't super rare.I would just consider the pair a single plugin in cases like this and forget about it. You're only paying a very small incremental cost and this is a smart way to do it for the devs. You wouldn't really save anything truly meaningful if they compiled it into a single unit.

Both files are more or less of the same size.

[aMUSEd]

Dynamically loading the VST from a tiny AU wrapper like that is one option that isn't super rare.I would just consider the pair a single plugin in cases like this and forget about it. You're only paying a very small incremental cost and this is a smart way to do it for the devs. You wouldn't really save anything truly meaningful if they compiled it into a single unit.

Both files are more or less of the same size.

Serum2.component on my system is 2.4 MB
Serum2.vst3 is 32.8MB

[martinjuenke]

Dynamically loading the VST from a tiny AU wrapper like that is one option that isn't super rare.I would just consider the pair a single plugin in cases like this and forget about it. You're only paying a very small incremental cost and this is a smart way to do it for the devs. You wouldn't really save anything truly meaningful if they compiled it into a single unit.

Both files are more or less of the same size.

Serum2.component on my system is 2.4 MB
Serum2.vst3 is 32.8MB

Thanks for the info. Will check, that may have changed. However, I think I‘ve made my point. Don‘t want to further abuse this thread with my hard disc aesthetics and policies. Let‘s move on.

[swilow11]

So, for Serum… don’t do that? Just this once?

Come on now, you're being too logical here.

[_leras]

Because I delete all AAX, VST and VST3 files from my system to keep my hard drive as sober and unpoluted as possible.
Most developers give me the option to exclude these formats during their installation process. Bravo!
Others do not provide this option (shame on you Softube, UAD, Waves and a couple more) therefore I have to clean up their garbage afterwards with a specific program.
This procedure saves me GigaBytes of hard disc polution with all its side effects.

Why would you bother?

My vsts are not installed in that many spaces. They go in my system drive.l, installed at default locations (for simple installation and updating for those that are still manual.. Cough uhe)

Samples and all working project files go in different directorys. Simple.

[Razzia]

Why would you bother?

Most people who have been at it a while end up accumulating lots of plugins. Just glancing at my VST3 folder, I have around 200 plugins on my laptop and my VST3 folder is barely under 6.5GB. 200 sounds like a lot, but there are lots of plugins that come as multiple files. Some UAD 'plugins' are 4 versions of one compressor or 3 versions of an EQ. God help anyone with lots of Acustica products.

Imagine you use only one format and every vendor by default copied a VST2 x86, VST2 x64, VST3, AAX, and AU version onto your hard drive. Dozens of GB wasted space if you don't delete the stuff that's not being used.

Just to clarify, I'm not on a Mac. So AU being a wrapper doesn't affect me and is not my gripe with Serum 2, but I can absolutely understand why someone would clean up the various plugin formats and stick to just one.