This is more about visually filtering what you have to make things easier, but I suspect the OP is busy tagging his sample sets with the construction kit extension I posted about above... to spend any more time complaining about what actually exists... in Studio OneBONES wrote: ↑Wed Jun 23, 2021 1:36 am How is that relevant to what you're doing, though? I have never in the 40 years I've been using synths thought "this is a job for a "cinematic synth" because, as far as I'm concerned, every synth I own is capable of doing "cinematic" sounds. Every synth is capable of doing "analogue emulation", even a DX7. Every synth is capable of doing "percussion" and all the rest of it. Seriously, go through the presets in any synth you own and look at all the different categories of sounds they break the presets into. And I don't have so many granular synths that I need to remind myself which ones they are.
What I am much more likely to want to recall is which synth has a particular patch I remember hearing 12 or 18 months ago when I got it, so being able to favourite patches within a synth's own browser is really handy, as is Studio One's ability to favourite a plugin with a particular patch pre-loaded. But tagging your plugins is ridiculous.
but in any case and to answer the OP's question, DAW developers have limited time to dedicate so much attention to one area in the course of year unlike dedicated browser management software developers do that focus entirely on that. If you go to use any 3D software, one of the most important aspects of that is the availability of plugins which the core software doesn't have or doesn't have at a more comprehensive level. In the same way, you can develop applications for DAWs.. but not all DAW's allow that.. which is really a topic all unto it self I think... Studio One is one that does...
