Plug-in limit?

[irpacynot]

Is there a limit to the number of plugins you can utilize within Waveform? I don't even seem to have that many installed. But I think I've tried to install about 20 over the past few days, and all of them are now having errors. Didn't have any issues when I first started using the software.

[pough]

A limit to the number of plugins in just the list of available plugins? If there is, it's a number higher than 1,000.

"Having errors" is a very vague description.

[Watchful]

Are these scanning errors? In other words, are they failing the initial scan? Waveform supports 64-bit plugins only, and not all formats. For example, CLAP and AU formats are not supported.

If using .vst or .vst3, the plugins must strictly adhere to the Steinberg requirements, which not all do...even very popular ones can fail. Some DAWs are pretty lenient in this regard; Waveform is not.

Are these insertion errors? Other than the master bus, Waveform doesn't provide much of any limit. I've never encountered any errors, and I've had some long plugin chains over the years.

Are these playing errors? If you're getting static, popping, or sound cutouts, it's possibly a limitation on your system's RAM or processor. Freezing the plugins, or rendering them and eliminating them from the tracks, is a way to reduce system overhead.

[Peter Widdicombe]

Yeah, "plugins having errors" is vague. As above, do they scan and report errors, or do they misbehave?

System resources (and windows updates, if under windows) can make a big difference. I do find Windows doesn't work well for the first 10 minutes after power on, running scans and updates and whatever.

Different vst's also have quirks. Large sample libraries (BBC Symphony orchestra) will hiccup each time you change instruments, as it's loading more tables in memory. Surge worked ok, SurgeXT it really depends on how complex the patch is and how many "new features" you use. If you have 16G memory you may not see this, but on 4 G will act up - and even going into "screen saver" mode can cause glitches. Smaller simpler vst's (4OSC for instance) rarely misbehave in this manner.

[irpacynot]

Are these scanning errors? In other words, are they failing the initial scan? Waveform supports 64-bit plugins only, and not all formats. For example, CLAP and AU formats are not supported.

If using .vst or .vst3, the plugins must strictly adhere to the Steinberg requirements, which not all do...even very popular ones can fail. Some DAWs are pretty lenient in this regard; Waveform is not.

Are these insertion errors? Other than the master bus, Waveform doesn't provide much of any limit. I've never encountered any errors, and I've had some long plugin chains over the years.

Are these playing errors? If you're getting static, popping, or sound cutouts, it's possibly a limitation on your system's RAM or processor. Freezing the plugins, or rendering them and eliminating them from the tracks, is a way to reduce system overhead.

Yes, sorry guys. They're failing the initial scan. I'm usually looking to only download VST3, and 64-bit.

[Watchful]

Any particular plugins failing? I'm trying to look for commonalities. Some plugins, like those that come with other DAWs, will not work in Waveform (like the free ones that come with Cubase) as they're design to work in only one host.

I've had some vst3 plugihs fail in Waveform if they were beta or demos. Generally vst3 requirements are more strict, so Waveform likes them much better than vst2 formats.