Hi,
I have a suggestion that may or may not make sense, but which I think would save a lot of people new to Megadrum (and forum members) a lot of frustration.
The most recurring problem is people not knowing how to set their pads up. From people who turn the module on for the first time, plug in a pad without configuring a single thing and come on to the forum asking what might be wrong, to those who do read the documentation but (understandably) struggle to grasp the many parameters there are and which ones to prioritise. The same issue keeps cropping up time and time again, and no matter how many times the questions are answered and people are directed to the documentation page, the answers in the forum get buried and the documentation page is either ignored or dismissed as incomprehensible.
My proposal would be to create a sort of setup wizard (within MDM?) that would take you step by step through the basic parameters to get a pad working, in a certain order. For instance, you choose jack input 4 (snare):
Name: snare (changeable)
Pad type: Single zone / Dual piezo / 3Way Yamaha / 3 Way Roland.
NEXT →
Note: xx (sets master note)
NEXT →
High level & Gain
The user presses 'start' and is instructed to hit the pad hard a number of times. If the value is under, say 300, the user is told to up Gain by 1 and repeat the process until high level is above, say 600 and under 900. Press 'done' and the value is saved.
NEXT →
Threshold.
You press 'start' and the application, through 'live updates', decreases the value of threshold until it detects auto-triggering (the user is instructed not to hit the pad), and raises the value by, say 3. If this can't be automated, tell the user to do it manually.
NEXT →Retrigger/DynLevel & DynTime.
I have my own order of configuring these but I suppose it would just be a matter of establishing the correct order and doing it step by step like above.
Depending on the pad type chosen, the steps are presented accordingly, with switch threshold detection, etc.
The idea would be to just have this for the bare minimum settings for different kinds of pads, Positional sensing values, alt notes, curves, compression, etc. can be left out to be done in MDM by the user – these are not normally things people get into until they are familiar with the module or they know what they are looking to do.
Some of the things I mention above are 'automated' to a degree, but that isn't even necessary. Just providing the user with step by step instructions in the application itself for basic essential parameters to get a pad up and running I think would help immensely.
What do you reckon Dmitri?