MeldaProduction

MeldaProduction · Post by **MeldaProduction** » Sat Dec 10, 2016 10:29 am

#1 - I'm afraid ignoring stuff is more complex than it looks due to the modularity of the system. I'll check but I don't promise anything.

#2 - saving kits - similarly to goldglob - here it works. Hard to say, maybe your host is taking the focus, or the saving dialog has this in the state - focused a different control from last time, hard to say.

#3 - goldglob quite didn't exlained it correctly - the designer works with components, while the pads contain all drums. Component is a tiny drumset. If it is a bass drum, then it's just bass drum. But if it is say toms, it's all of them, because they fit each other! I don't think anyone would like 5 completely different toms

. Same for hihat. There you might want a different open hihat for electronic styles, true, but that's just the limitation we need to live with.

goldglob · Post by **goldglob** » Sat Dec 10, 2016 3:05 pm

MeldaProduction wrote:..........

#3 - goldglob quite didn't exlained it correctly - the designer works with components, while the pads contain all drums. Component is a tiny drumset. If it is a bass drum, then it's just bass drum. But if it is say toms, it's all of them, because they fit each other! I don't think anyone would like 5 completely different toms . Same for hihat. There you might want a different open hihat for electronic styles, true, but that's just the limitation we need to live with.

It is good to hear a bit more about the strategy behind how the factory components are organized. I had earlier in the thread tried to explain that a component can be more than one drum, and then later tried to keep it simple in order to focus on the essential difference between pads and components. I think when Vojtech says that I didn't quite explain it correctly he perhaps means that I didn't explain it fully.
BTW, “I never made a mistake in my life. I thought I did once, but I was wrong.”

MeldaProduction · Post by **MeldaProduction** » Sun Dec 11, 2016 2:02 pm

Hehe actually I was mainly replying to "the reason open HH is not in the designer list is simply that it hasn't been created there", which is just wrong, because open hihat IS there, but it is included in the hihat component for obvious reason

. If there would be another "open hh" component, it would obviously be a conflict, who knows how that would end

.

goldglob · Post by **goldglob** » Sun Dec 11, 2016 11:50 pm

Understood: randomizing HH in Designer logically brings in a related trio of Hi-hat, Pedal hi-hat and Open hi-hat..sensible strategy..MD is intelligent

MeldaProduction · Post by **MeldaProduction** » Mon Dec 12, 2016 1:02 pm

Hehe thanks!

AtomOfScent · Post by **AtomOfScent** » Mon Dec 12, 2016 11:32 pm

Thanks for the clarification. It makes sense, but also means using the designer won't be a substitute for my original request (randomizing the sample associated with a drum pad).

I think it would also make sense to generate components for ALL drum types when using the option to create components from an analyzed imported sample library. If there are going to be exclusions, at least give the user choice over what they are.

MeldaProduction · Post by **MeldaProduction** » Wed Dec 14, 2016 7:10 pm

I'm afraid it doesn't work like that, the randomizer is based on components, so it needs to follow the components.

AtomOfScent · Post by **AtomOfScent** » Thu Dec 22, 2016 6:51 am

MeldaProduction wrote:I'm afraid it doesn't work like that, the randomizer is based on components, so it needs to follow the components.

Totally understandable.

But if you figure out a way to choose a random sample in the same folder, and/or with a similar naming scheme, I doubt those that don't use it will complain!

MeldaProduction · Post by **MeldaProduction** » Thu Dec 22, 2016 11:49 pm

Well, I'll think about a potential solution, but I'm not really sure to be honest...

MeldaProduction

KVR Audio

MDrummer - Quick Setup page feature requests and suggestions