beats me wrote:
All I’m saying is don’t advertise something has 100 patterns and then there’s nothing in the pattern browser.
It’s like saying something has 3,000 samples but none of them appear in the sample browser until you manually add them one by one.
And I realize Komplete is a little more complex but I don’t get patterns having to be tied to kits. It’s not like you have a pattern for kick, snare, and hats but as soon as you load a different kit those notes are going to trigger all crashes, cowbells, and blocks. A snare note should be a snare note no matter what drum kit you load.
I’ll get over this, but it’s generally one of the first features I test drive when I get a drum plug-in with a sequencer and I thought the lack of patterns in the pattern browser meant something didn’t install properly or I needed to configure something.
And really which is a user more likely to use, snippets from an entire demo song or quality patterns that aren’t tied to any included song? A lot of the patterns included in the songs are laughable as a preset pattern. It’s really not that difficult to program a 4 count hat or kick. So one argument is you only save the patterns you think you’d use. My argument is 100 patterns should be quality, not 20 interesting usable patterns and 80 patterns of fluff or something a monkey could tap in with quantization turned on.
This thread inspires long winded bitching. I can't wait until a graduate to personal attacks.
It's definitely long winded, so I can't help to think that we haven't understood your root issue here.
When you do drums, you need primarily two things: a kit (sounds) and a pattern (triggering of sounds). For me, the sound selection is more fundamental, hence I start with selecting/auditioning kits. There is obviously a significant difference between an acoustic kit and a glitch or found sounds kit.
Once I found a nice kit, Maschine will also load dedicated patterns for that kit. I can then go, and change the patterns, and obviously, I can change single sounds and the whole kit later as well. But the key point is that I don't start searching for a pattern before I have found a kit. There is also a lot of situations where a pattern mostly makes sense in the context of a specific kit, e.g. having broken beats, rapid fire etc. could be more appropriate for a glitch/minimal kit rather than an acoustic kit.
Now, I could imagine, people which are more "traditional"/acoustic minded (rather than experimental) could see this the other way around. Like a drummer in a band who will use the same/similar kits every day, the sound selection might not be so important, the pattern is key. Not sure though what music you make.
But in any case, when you start with a clean slate using e.g. Addictive Drums and you start browsing through your patterns, how do you audition them without having selected a kit ? A pattern is just a soundless Midi file. So how do you make sure (in AD) that the kit "fits" the pattern you have selected. Maybe the pattern doesn't appeal to you during browsing because you are using the "wrong" kit ?
As for the other complaint, have you actually done as suggested before and loaded a KIT/group rather than a full demo song, and looked at the patterns that come with the kit ? My experience has been that these patterns are somewhat elaborate (not "two oneshots in a four bar loop").
I am fairly certain that if you would load all the kits in your expansion pack (which one are you referring to ?) one by one and counted the patterns associated with each kit, you would find that there indeed 100 patterns. So why not advertise that ?
It has already been confirmed that there is a scenario which Maschine doesn't cover "out of the box" (I believe), which is loading an individual pattern only. The suggestions and content provided do address that, but again, this might not be so important for most electronic music producers.