MegaDrumWiki - New pages [en]

Sampling

2014-11-24T04:16:28Z

Airflamesred:

The purpose of the sampling block is to transform analog
inputs into an event stream with the following characteristics:

*accurately represents the strength of each hit

*does not produce false trigger events

*emits the event as soon as possible after it occurs
MD has four parameters that allow you to control this
process:

*Gain

*Threshold

*High Level

*MinScan

To explain how these work, let’s consider a simple piezo input. Consider the following (very simplified) output from a sensor that has been struck four times:

[[File:Hits_1.svg|center|frame|Multiple Hits]]

MD uses digital sampling to start the process; this is actually just like sampling an audio signal to turn it into a digital wave.
==Gain==
The first sampling parameter is Gain. Gain can be thought of as a volume knob. Just as a volume knob makes the music louder or quitter, the gain setting will make the signal from the piezo stronger or weaker.

Why would you do this?

When MD samples it expects the voltage of the signal to be in a specific voltage range. If the signal is too weak it will be difficult to detect that something of significance has happened, and if it is too strong, MD will be unable to distinguish between softer and harder hits.

If your piezo is ‘hot’, this means that it is more sensitive and that the electrical signal is already strong and needs a lower gain setting to avoid clipping the input. If your piezo is cool, this means that it is less sensitive and that a higher gain setting will be appropriate.

Gain helps you match what your piezo produces to what MD wants to consume.

Gain is the only parameter that affects the analog signal. The other three are working with the output of the A/D converter.

After sampling, the block has a digital representation of the analog signal with values in the range from 0-1023.

==Threshold==
Any real world analog system has some degree of noise present. This noise is sampled along with legitimate strike signals. For a piezo input, threshold is the level, below which, the signal is considered noise. When the signal rises above the threshold, the sampling block will generate an event.

Consider the following:

[[File:Sampling_hits.svg|frame||center|Threshold]]

With the lower line for threshold, it should be clear that the sampling block is going to generate a large number of events for activity that isn’t actually there. The sampled noise looks like very quiet strikes. A threshold that is too low can demonstrate the following symptoms:

* Repeated notes when nothing is actually happening on an input
* Random notes when nothing is actually happening on an input<ref>Not to be confused with notes that are caused by vibrations between pads that are mechanically connected (we’ll discuss configuring those tools later in the filtering section)</ref>

Of course, the threshold can also be set too high. This will cause MD miss softer notes. Consider the second strike: with the ‘too high’ threshold value, MD will not detect it as a hit.

This is a crucial performance parameter and it may take a bit of experimentation to find a value that works best. Please note that the threshold will be different for different pieces of gear in your set.

==High Level==
The sampling block does not pass the actual sampled level (0-1023) with the strike events. That would make setting the parameters in the other blocks unnecessarily difficult. Instead it normalizes the sampled level to a 0-255 scale, where 0 is the Threshold and 255 is the pad being struck as hard as possible.

High Level is simply the sampling level that corresponds to strength 255 for the event. Any sample levels higher than this will be transmitted as 255. Levels lower than this will be scaled on a straight line to the threshold level.

Tips for setting HighLevel:
* The auto-High level setting will allow the input block to automatically adjust the high level to the strength of the strongest hit it has seen. Briefly turning this on and then hitting the pad as hard as you can, a number of times, will produce a very good first estimate for HighLevel
* Reducing the HighLevel allows a sort of brick wall limiting function. If your sensor occasionally emits a very strong signal, it is OK to reduce the MaxLevel so that these are squashed into the top end of the musically useful strengths.
*Reducing HighLevel too far will reduce the smoothness of your velocity response.
*Raising HighLevel high above the actual levels generated by the sample will also degrade the velocity response, generally limiting the final MIDI notes to lower velocity values, no matter how hard the pad is struck.

==Min Scan==
MinScan controls how long after the input signal crosses the threshold MD will continue to sample the input. Consider:

[[File:Min_scan_time.svg|frame|center|Min Scan Time]]

Remember, that once the input signal crosses the threshold, the sampling block is going to generate an event. The next question is what strength should that event have?

If MinScan is too short, then MD will stop looking while the input is still rising. This will result in a trigger that does not accurately record its potential dynamic range.

However, MinScan represents a delay (latency) between the physical strike and a note being generated. Setting MinScan too long will result in longer latency.
Typically, rubber cymbals and pads are able to use a setting of 20 (2 msec) while mesh heads may require 30-50 (3-5msec). The bigger the pad, the longer MinScan will need to be to properly detect signal level.

<references />

Input Types

2014-11-24T04:14:00Z

Airflamesred: /* Piezo Sensor */

== Piezo Sensor ==
A piezo is an electronic component that (among other remarkable properties) will generate a voltage when struck. The voltage is proportional to the energy (velocity) in the strike. If there is a positional sensing board attached to your MegaDrum this will also measure the distance, from the piezo, that the drum head is struck.
Piezos are used when we need to know how hard something is being hit.

== Switch ==
Typically a film switch, this doesn’t convey information about how hard something was struck, but it can convey information about ''where'' it was struck.

== Potentiometer ==
A ‘volume knob’. This is used to indicate continuous positions (i.e. 10%, 40%, 100%, etc.). This is used for the Hi Hat controller.

== Hall Effect Sensor ==
This is a sensor that works with a magnet to provide continuous positions. It is similar in effect to a potentiometer.

[[Theory of Operation]]

Theory of Operation

2014-11-24T03:56:47Z

Airflamesred: /* Note Selection and Velocity Scaling */

Connecting a Yamaha or Roland drum brain to the corresponding pads is usually pretty simple. However, if you want to use a Roland pad with your Yamaha brain you may end up having to do some tweaking if you can even get it to work at all.

MegaDrum is agnostic with regards to the pad vendor and even supports a wide variety of DIY triggers. In order to do this, it needs to expose many more configuration options than the vendor specific units do. Unfortunately, having this large number of parameters available can make it difficult to understand just what parameter you should adjust when something is not behaving correctly. It can be hard to see the forest for the trees.

'''The purpose of this document is to explain the forest and where each tree fits.'''

(I have pictures that I will add when the wiki allows me to)

== Block Diagram ==
Consider the following (very simplified) block diagram:
[[File:Simple_block_diagram.svg|frame|Simple Block Diagram|none|800x800px]]

=== Sampling ===
The inputs from your pads are presenting some sort of analog signal. The purpose of sampling is to convert this signal into discrete events that can be dealt with more simply.

=== Filtering ===
Filtering is used to remove unwanted events from the event stream. A good example of this would be if a strike on one drum pad caused a faint strike to register on another pad that was connected to the same rack. MD allows a filter to be created that can reduce or eliminate this problem.

=== Note Selection and Velocity Scaling ===
This is the final step before transmitting a note. Based upon the input, a MIDI note and MIDI channel are selected and, based upon how hard the input was hit, a velocity is selected. MD provides some very nice tools for transforming input strike strength into a note velocity.

[[Input Types]]

[[Sampling]]

MegaDrum Manager

2014-11-22T22:07:03Z

Airflamesred: Created page with "The display on the MegaDrum is rather small and awkward to work with so a PC interface is available. With Megadrum Manager running you can access all the features of MegaDrum,..."

The display on the MegaDrum is rather small and awkward to work with so a PC interface is available. With Megadrum Manager running you can access all the features of MegaDrum, from you PC, far quicker an easier.

MegaDrum Configuration

2014-11-20T03:09:59Z

BiggerNoise:

[[Updating MegaDrum firmware]]<br>
[[Theory of Operation]]<br>
[[MegaDrum Manager]]<br>
[[Megadrum Commander]]

VSTi Configuration Guides

2014-11-20T03:08:37Z

BiggerNoise: Created page with "SuperiorDrummer2"

[[SuperiorDrummer2]]

Hardware

2014-11-20T03:08:11Z

BiggerNoise:

Just some links at the moment

[[Ordering ATmega]]<br/>

Contributor Guidelines

2014-11-20T02:23:02Z

BiggerNoise: /* Signing Up */

== Signing Up==
If you are willing to contribute to {{SITENAME}}, please ask Biggernoise for an account on the [http://www.megadrum.info/forums/ forums] by means of a personal message. Please include your e-mail address so that I can set your account up properly.

There are guidelines in the [[Help:Contents|help section]] that should be read and understood prior to writing new or editing existing articles. It contains basic markup information and general guidelines.

== Developing Content ==
I think that we can develop content fairly organically by creating, finding, or clarifying wiki pages that answer broadly applicable questions. Many important topics have been already discussed on the forums, importing those topics should largely be a matter of editing, curation, and formatting.

Table.css

2010-09-14T07:45:48Z

Firelord: Created page with 'table.wikitable { margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse; } .wikitable th, .wikitable td { border: 1px…'

table.wikitable
{
margin: 1em 1em 1em 0;
background: #f9f9f9;
border: 1px #aaa solid;
border-collapse: collapse;
}

.wikitable th,
.wikitable td
{
border: 1px #aaa solid;
padding: 0.2em;
}

.wikitable th
{
background: #f2f2f2;
text-align: center;
}

.wikitable caption
{
font-weight: bold;
}

SuperiorDrummer2

2010-08-12T11:46:53Z

Firelord:

__NOTOC__ {{#css:Table.css}}
==Setting up MegaDrum and Superior Drummer 2==
'''Scope:'''
* Quick setup for Superior Drummer 2 (SD2)
* MIDI mapping for MegaDrum (MD)
* Not covering how to make MD settings OR advanced features of SD2.

'''Prerequisites:'''
* Low latency audio setup in Windows ([[Wikipedia:Audio_Stream_Input/Output|ASIO]])
* Tuning of MegaDrum to suit your kit - ([http://www.megadrum.info/content/megadrum-configuration MD configuration])
* MegaDrum connected to the PC via traditional MIDI interface or MIDI over USB interface
* Installation of Superior Drummer 2.2.1 and ToonTrack Solo 1.2.2 software

'''Notes:'''
* ToonTrack Solo is a 'host' program for the Superior Drummer 2 'VST' instrument. The VST could also be loaded into any other VST host programs such as Digital Audio Workstation (DAW) software like ProTools etc. In this description, references to SD2 may really mean the ToonTrack Solo host program or the VST.
* Setup described below is for a MegaDrum with a variable hi-hat pedal. You can of course also do simple switch based open or closed, but really you should consider to go fully variable because otherwise you are not taking advantage of one of the main reasons to use Superior Drummer 2, which is the so called 'transmutation' of the high hat sounds which makes a big difference to the realism.
* There is some overlap of functionality between MD & SD2 in the MIDI domain, with things like velocity curves etc. Just be aware of potential confusion by making settings in both places.

==Steps to setup SD2==
* Start 'ToonTrack Solo' program, Select Drummer to use 'Superior Drummer 2' (in other words start a new project).
* Note in the interface the difference between the host (ToonTrack solo) and the VST (Superior Drummer 2). ToonTrack Solo has the more conventional windows forms interface, whereas Superior has all the custom graphical widgets which kind of makes it a rich but confusing interface.
* Options->Audio->Audio Device, Choose device type 'ASIO' output driver 'ASIO4ALL v2', OK
* Options->Audio->Latency Settings, Choose the lowest possible setting without the audio breaking up. More info here: [[Configuring ASIO drivers]]
* By left clicking on the images of the drums or cymbals you should now hear sound
* Options->Controller, make sure to tick both 'e-drums' and 'cc offset'
* Options->MIDI Devices, Select your MegaDrum (may appear simply as 'USB Audio Device')
* Save the ToonTrack Solo project (file->save as *.tts file) next time you start, you can just double click the *.tts file to open up with all your settings for ToonTrack Solo as well as all the Superior Drummer presets that you might have made. It is also possible to independently save the presets of SD2 or subsets of them as *.S20 files and this is probably good idea as a separate backup if you rely on any specific fine tunings in SD2 but it is not necessary.
* You might be able now to quickly verify operation by using the Kick Drum since this mapping is probably already correct (Note number 36)

==MIDI Map to set in your MegaDrum==
You can get SD2 to learn the notes which your your MD is already set at but this is more a feature for other drum modules with fixed MIDI maps. Better I feel to set the MD to the defaults of SD2, it is much faster to setup this way.

The full default MIDI map for SD2 can be found in a pdf via somewhat hidden menu in SD2 (took me a while to find it anyway)

? -> Ny avatar -> MIDI Layout, this opens the pdf file 'Avatar1Keys.pdf' or you can open the pdf file directly now you know the name.

Anyway never mind about that as I will spell out the mappings that you might want to set in the MegaDrum here:

{| class="wikitable"
| align="center" style="background:#f0f0f0;"|'''MD Name'''
| align="center" style="background:#f0f0f0;"|'''MD Setting'''
| align="center" style="background:#f0f0f0;"|'''SD2 Default'''
| align="center" style="background:#f0f0f0;"|'''SD2 Name'''
| align="center" style="background:#f0f0f0;"|'''Articulation'''
| align="center" style="background:#f0f0f0;"|'''Optional custom tuning'''
| align="center" style="background:#f0f0f0;"|'''Notes'''
|-
| HiHat Pedal||CC Value||CC04||Hats||hatsCtrl||Pedal correction||HiHat Pedal->Type: F.Contr (so it sends cc messages) cc04 is the default
|-
| HiHat Pedal||Bow*||19||Hats||TipTrig||||* represents 4 separate settings for SO, HO, SCL, CL (or 2 separate settings in firmware < 20100613)
|-
| HiHat Pedal||Edge*||18||Hats||Trig||||
|-
| HiHat Pedal||Bell*||20||Hats||BellTrig||||
|-
| HiHat Pedal||Chick||21||Hats||Pedal||||
|-
| HiHat Pedal||Splsh||23||Hats||FootSplash||||
|-
| Ch01: Kick||Note||36||Kick||Kick||||
|-
| Ch02: HiHatB||Note||19||Hats||TipTrig||||Normally these represent the \"full open\" notes.. But for our purpose should be identical to the other 2 or 4 note settings for the same zone
|-
| Ch03: HiHatE||Note||18||Hats||Trig||||
|-
| Ch03: HiHatE||BNote||20||Hats||BellTrig||||(3rd zone)
|-
| Ch04: SnareH||Note||38||Snare||Center||||
|-
| ||||CC16||Snare||SnareCtrl||||cc16 is the default for MD but you need to enable the positional sensing feature (firmware >= 20100516 only)
|-
| Ch05: SnareR||Note||40||Snare||RimShot||||
|-
| Ch06: RideB||Note||51||Ride4||Ride||Aftertouch||
|-
| Ch07: RideE||Note||59||Ride4||Punch||Aftertouch||
|-
| Ch07: RideE||BNote||53||Ride4||Bell||||(3rd zone)
|-
| Ch08: CrashB||Note||49||Cymbal2||Crashed||Aftertouch||CrashA
|-
| Ch09: CrashE||||n/a||n/a||n/a||||
|-
| Ch10: Tom1H||Note||48||RackTom1||Center||||
|-
| Ch11: Tom1R||Note||82||RackTom1||RimShot||||
|-
| Ch12: Tom2H||Note||47||RackTom2||Center||||
|-
| Ch13: Tom2R||Note||80||RackTom2||RimShot||||
|-
| Ch14: Tom3H||Note||45||RackTom3||Center||||
|-
| Ch15: Tom3R||Note||78||RackTom3||RimShot||||
|-
| Ch16: Tom4H||Note||43||FloorTom1||Center||||
|-
| Ch17: Tom4R||Note||75||FloorTom1||RimShot||||
|-
| Ch18: Aux1H||Note||41||FloorTom2||Center||||
|-
| Ch19: Aux1R||Note||73||FloorTom2||RimShot||||
|-
| Ch20: Aux2H||Note||57||Cymbal5||Crashed||Aftertouch||CrashB
|-
| Ch21: Aux2R||||n/a||n/a||n/a||||
|-
| Ch22: Aux3H||||||||||||
|-
| Ch23: Aux3R||||||||||||
|-
| Ch24: Aux4H||||||||||||
|-
| Ch25: Aux4R||||||||||||
|-
| Ch26: Aux5H||||||||||||
|-
| Ch27: Aux5R||||||||||||
|-
| Ch28: Aux6H||Note||55||Cymbal3||Crashed||||Splash
|-
| Ch29: Aux6R||Note||52||Cymbal1||Crashed||||China - position not loaded by default
|-
| Ch30: Aux7H||Note||56||Cowbell||Cowbell||||position not loaded by default
|-
| Ch31: Aux7R||||||||||||
|-
|}

Make those settings for MIDI note number in MD either directly with the [http://www.megadrum.info/content/megadrum-configuration MegaDrum's LCD] or via [[MCT|MegaDrum Config Tool (MCT) software]]

All done - everything should work.

'''Notes:'''
* Only enable and map the inputs for which you actually have triggers attached too, else due to the high impedance inputs on MegaDrum, the unconnected but enabled inputs could easily cause triggering of sounds you don't want.
* Your Hi-Hat setup is such that you want it to always output the same notes for edge, bow & bell, regardless of the openness of the pedal (SD2 takes care of that part). This will mean setting the same note number in a few spots (firmware versions 20100613 and above have 5 levels below this only 3 levels).

==Some more detailed adjustments in SD2==
Note: some more (or less) detail on the following can be found via menu ?->Operation Manual in SD ("Superior_Drummer_Operation_Manual.pdf" file)

===Cymbal Chokes===
MD automatically sends MIDI aftertouch messages when a cymbal is choked (provided your cymbals have the feature). This does not require a separate MIDI note number

assignment. If you want to make use of this in SD2, you need to enable the feature as follows:

[[File:SD2-Aftertouch+.png]]

# Select the cymbal (right click on the graphic or select it from the drop down)
# Select the articulation. For most cymbals you will just do it on the 'crash' articulation. With the ride cymbals you may want to do this process for both 'ride' articulation and also for 'punch' articulation
# Turn on the 'edit articulation only' filter
# Enable the envelope
# Move the switch to the 'Aftertouch' position
# Drag the 'release' parameter or click and set the time directly. You can also change the 'hold' parameter

===High-Hat Pedal Correction===
As noted earlier the overlap in settings between MD / SD2.. you may consider not to touch the pedal correction in SD2 but try choosing a different curve in MD (or use a custom curve)

To get the proper sounds using the SD2 defaults, the end result should be:

* Closed (pedal down).. cc04 value >120
* Tight closed (pedal down with heel up) cc04 value = 127 (max) possibly also 126 counts as tight, not sure

the easiest way to see these numbers is with [[MCT]]

To do the tuning in SD2 refer to SD2 Operation Manual section 7.3

(todo)

==Notes==

Some SD2 settings that may be of interest.. ('Settings' menu in SD2)

* 'MIDI keys as numbers'

Updating MegaDrum firmware

2010-08-02T13:49:28Z

Firelord: /* Troubleshooting */

{{Note|This tutorial describes the updating procedure for the new encrypted firmware (issued since June 2010). If you are looking for a tutorial on updating the old, unencrypted firmware, check out the [[Updating MegaDrum firmware (legacy)]] article. Also you might want to read the [[programming USB firmware]] tutorial.}}
Keeping your MegaDrum firmware up-to-date is an important task because it ensures maximum stability and performance. MegaDrum firmware is regularly updated: new features (such as support for specific e-drum pads) are constantly added. So if something does not work for you it might be fixed in a new firmware version, based on [http://www.megadrum.info/forums/ your feedback].

This tutorial describes the updating procedure in detail.

== Prerequisites for updating ==
* MegaDrum must be pre-programmed with the protected bootloader
* You must have a working board with fully functional MegaDrum controls
* Updating may be done via USB or MIDI I/O

If you choose to update via USB for the very first time, connect MegaDrum to the PC and let it install the necessary drivers first (e.g. on Windows XP).

The [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1075 latest firmware version] is available for download from the forums.

== Firmware file naming convention ==
You should update with the right firmware for your MegaDrum version. All firmware files in the archive have the following naming scheme:

* megadrum''ppp''_''hh''_''yyyymmdd''.bin — '''22''' inputs versions
* megadrum''ppp''_''hh''_'''32'''_''yyyymmdd''.bin — '''32''' inputs versions
* megadrum''ppp''_''hh''_'''48'''_''yyyymmdd''.bin — '''48''' inputs versions
* megadrum''ppp''_''hh''_'''56'''_''yyyymmdd''.bin — '''56''' inputs versions

where

''ppp'' — AVR microcontroller type
:32 — for Atmega32
:324 — for Atmega324(p)
:644 — for Atmega644
''hh'' — crystal clock in MHz
:Atmega32 versions with a clock above 16MHz are overclocked, Atmega324(p)/644 versions with a clock above 20MHz are overclocked
''yyyymmdd'' — date (version) of the firmware.

== Update software ==
You will need to use a special PC application to update your MegaDrum firmware. Currently there are three options available. Choose the one that works for you.

=== mdfwupdate ===
{{video|
url =http://www.youtube.com/watch?v=Y8M3KIRuPWQ|
desc=Updating MegaDrum with mdfwupdate (with a GUI)}}

==== General information ====
* Platform support: Windows, Mac
* Tested in: Windows XP
* Type: Command-line utility. A GUI for selecting the firmware file is also available [http://www.megadrum.info/forums/viewtopic.php?p=14818#p14818 here].
* Source code: [http://www.megadrum.info/forums/viewtopic.php?p=15208#p15208 available] ''(C++)
''
==== Updating procedure ====
1. [http://www.megadrum.info/forums/viewtopic.php?p=14779#p14779 Download mdfwupdate] from the forum (note: if you have the GUI you do not need to download the command-line utility separately!), a test version is also [http://www.megadrum.info/forums/viewtopic.php?p=15283#p15283 available for the Mac]

2. Download the [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1075 firmware archive]

3. Power MegaDrum up while holding the key LEFT pressed. While keeping the key LEFT pressed the MIDI LED will be blinking indicating that it is entering the bootloader mode. When you release the key LEFT the LCD will show:
{{LCD|
color=white|
bgcolor=blue|
line1=FwSUpdater 16MHz|
line2=DOWN-ok.UP-clock|
caption=MegaDrum secure bootloader menu
}}

4. In MegaDrum select correct frequency for your ATmega crystal by pressing the key UP. Each time you press UP it will cycle one step through 16MHz→20MHz→24MHz→12MHz. If you use a 16MHz crystal for ATmega, you don't need to press UP since 16MHz is a default start up frequency for the bootloader

5. In MegaDrum press the key DOWN. The LED will light up and MegaDrum display will show (e.g. for 16MHz):
{{LCD|
color=white|
bgcolor=blue|
line1=FwSUpdater 16MHz|
line2=StartUpdateOnPC{{nbsp|1}}|
caption=MegaDrum secure bootloader in update mode
}}

6. Run the utility from the command line, e.g.:
<pre>
mdfwupdate.exe megadrum644_20_32_20100601.bin
</pre>

7. First it will prompt you to choose which MIDI output port to use. Type a number corresponding to the MegaDrum MIDI port and press Enter. It will now prompt you to choose which MIDI input port to use. Type a number corresponding to the MegaDrum MIDI port and press Enter. It will start updating the firmware and after a couple of minutes it will finish. While doing the update it will show progress on the command line and on the LCD. On the LCD it will look like this:
{{LCD|
color=white|
bgcolor=blue|
line1=88886>ater 16MHz|
line2=StartUpdateOnPC{{nbsp|1}}|
caption=MegaDrum secure bootloader during the update
}}

8. When update has finished, the utility will show
<pre>
Transferring.. 100% done.
MegaDrum updated successfully.
</pre>

MegaDrum will then reboot and start with new firmware and you will see the copyright screen:
{{LCD|
color=white|
bgcolor=blue|
caption=Copyright screen
}}

Note that you might not see it due to poor contrast setting. Tweak the contrast from the menu by pressing the LEFT key once and then pressing UP/DOWN until you clearly see the text on your LCD.

=== MDUpdate ===
{{video|
url =http://www.youtube.com/watch?v=-N5YrSE4nxo|
desc=Updating MegaDrum with MDUpdate test under Windows XP}}
[[File:MDUpdate.png‎|250px|thumb|MDUpdate screenshot]]

==== General information ====
* Platform support: Windows, Linux (under [[wikipedia:Wine_(software)|Wine]])
* Tested in: Windows XP, OpenSUSE 11.2
* Type: GUI
* Source code: [http://www.megadrum.info/forums/viewtopic.php?p=15285#p15285 available] ''(C++, [http://wxdsgn.sourceforge.net/ wxDev-C++] and [http://www.codeblocks.org/ Code::Blocks] projects)''

==== Updating procedure ====
The procedure is basically the same as for [[#mdfwupdate|mdfupdate]]. The obvious difference is that everything is done by means of a GUI. Here's a quick rundown:

1. Download [http://www.megadrum.info/forums/viewtopic.php?p=15245#p15245 MDUpdate]

2. Download the [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1075 firmware files]

3. Start MegaDrum in bootloader mode, select the correct frequency, switch to live update mode

4. Run MDUpdate, select the correct firmware, MIDI I/O ports and press '''Run MegaDrum Update'''

5. Wait for the firmware update to finish.

=== Megadrum Config Tool ===
{{Main|Megadrum Config Tool}}
{{video|
url =http://www.youtube.com/watch?v=5hjP4Kut5lQ|
desc=Updating MegaDrum with MCT v1.84}}

==== General Information ====
* Platform support: Windows, Linux, Mac<ref>See [http://www.megadrum.info/forums/viewtopic.php?p=15211#p15211 this forum post] about using MCT on Mac</ref>
* Tested in: Windows XP
* Type: GUI
* Source code: [http://code.google.com/p/megadrumconfigtool/ available] ''(Java, [http://netbeans.org/ NetBeans] project)''

==== Firmware updating procedure ====
{{Note|[[MCT]] supports encrypted firmware updates since version 1.84.}}

The basics of the updating procedure are given in the [[#mdfwupdate|mdfwupdate]] section of this tutorial.

1. Download [http://www.megadrum.info/configtool/ Megadrum Config Tool v 1.84] via the installer.

2. Download the [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1075 firmware files]

3. Start MegaDrum in either normal mode or bootloader mode

4. Start MCT, and set up the options:
* MCU type and clock frequency
* Bootloader type to v5
* Correct MIDI I/O ports which correspond to MegaDrum

5. In MCT menu go to <code>Firmware → UPDATE FIRMWARE</code>

6. Now close MCT and power off your MegaDrum

7. Start MegaDrum with the LEFT key pressed (in bootloader mode), select the correct crystal frequency

8. Open MCT, select the correct firmware file

9. Press LEFT on MegaDrum to send a confirmation message to MCT, the <code>Proceed</code> button should be enabled

10. Press DOWN on MegaDrum to enter live update mode

11. Press <code>Proceed</code> button in MCT

12. Wait for the update to finish, once it is finished restart MCT

== Troubleshooting ==
{{Main|Troubleshooting firmware updates}}
If you cannot update your MegaDrum firmware, there could be several reasons:
* You are trying to update via an unsecure bootloader
* You are using wrong update software (e.g. MIDI-OX) with the protected bootloader
* Your board has defects
* MegaDrum controls are not functional
* MIDI/USB communication fails for some reason
* You have found a bug in the updating software. Please [http://www.megadrum.info/forums/ report it]!

== See also ==
* [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1252 Updating firmware with protected bootloader] forum discussion

== Notes ==
<references />

[[Category:Tutorials]]