Going CLAP would be awesome—it is superior to VST3 in any way I can think of; VST2 should not be used anymore (in theory, unless it can still be used on existing plugins; I didn't read the "fine print" on the VST2 deprecation story).graywolf2004 wrote: Fri Jan 03, 2025 8:46 amI was saying that about BlueARP, but I agree with phreaque - between vst2 and vst3 I'd better use vst2, unless I need some specific features of vst3 (which I can't even imagine at this point)electro wrote: Wed Jan 01, 2025 1:06 amHow many other plugins does this rule apply to?graywolf2004 wrote: Sat Dec 28, 2024 4:18 pm My advice is to use vst2 if possible, it is more reliable and better tested.
Number '3' in vst3 doesn't mean that it is better than vst2 in every aspect. In general it is over-complicated and over-engineered (I already commented on that here), especially for simple plugins. VST3 might be better for multi-timbral / multi-layer plugins with complex GUI and patch structure, only in this case the complexity of VST3 might give some benefits. Recently I checked CLAP documentation and examples and I like what I saw so far, so hopefully after a while I will be able to introduce BlueARP as a CLAP plugin and maybe even discontinue VST3 (which is always additional PITA to test)
I would be the first to be happy if the VST3 format were dismissed (that would be a strong statement) but in this case, DAWs that don't support CLAP - cough Steiny cough - would be left without up-to-date BlueArp.
