On 03/29/2014 10:42 PM, Jonathan Aquilina wrote: > > I agree with providing a basic set of plugins. >
Well, there's one thing we're all forgetting here (except me, because I'm saying it now). Lots of people like LMMS because it offers the best possibilities for collaboration. Users can expect that the plugins that come bundled with LMMS are present on all standard LMMS installations - we provide a sort of "standard base" that everyone can build their LMMS installation upon. And the "standard base" is already powerful enough that many people are capable of producing great songs with it. You want to make some of our plugins DLC? Well then, you might as well just kill the sharing platform. At least the songs portion of it. No one's going to bother going through songs with lists of dependencies with them "to play this song, you need x and y and z"... Another thing is, what's with this idea of killing plugins when we have something like 12 of them? What's the logic here? Every professional DAW comes with a good sized collection of native plugins, they're the calling card and trump card of that particular DAW, something to differentiate on. I could see the point if we had a 100 native instruments. I could see the problem if people were complaining it takes too much time to download LMMS because of the massive plugin library. But we have less than 15 of them. What's the point of bundling 6-7 instruments, then tell the users to download 6-7 more separately? I don't see who this would benefit and in what way. One instrument plugin takes at most 1MB of disk space in binary form - even less in source form. So what exactly are we trying to accomplish here? To provide a worse experience for the user? ------------------------------------------------------------------------------ _______________________________________________ LMMS-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmms-devel
