https://www.megadrum.info/wiki/api.php?action=feedcontributions&feedformat=atom&user=FirelordMegaDrumWiki - User contributions [en]2026-04-30T22:35:55ZUser contributionsMediaWiki 1.25.2https://www.megadrum.info/wiki/index.php?title=Help:Contents&diff=132Help:Contents2010-11-23T12:59:47Z<p>Firelord: /* Adding videos */</p>
<hr />
<div>'''Welcome to the {{SITENAME}} help section!''' This page currently contains:<br />
* General formatting documentation to help you get started writing articles;<br />
* Some guidelines on writing new/editing articles for {{SITENAME}}.<br />
<br />
'''Please read the following carefully especially if you haven't worked with MediaWiki based projects before.'''<br />
<br />
If you are looking for help with building/buying/troubleshooting MegaDrum, please refer to the [http://www.megadrum.info/ forums] for now.<br />
<br />
== MediaWiki markup ==<br />
<br />
=== Basic formatting ===<br />
The most important part of a MediaWiki article is meaningful plain text. However, formatting is required to deliver rich content. Basically, you enter text with special control characters/structures to get formatting effects. For example, to get '''bold''' text you would enter the following:<br />
<br />
<pre>'''This text is bold'''</pre><br />
<br />
This will render:<br />
<br />
'''This text is bold'''<br />
<br />
Please refer to the [http://www.mediawiki.org/wiki/Help:Formatting basic formatting documentation]. You can also learn the formatting rules from viewing the content of existing MediaWiki pages (e.g. [http://wikipedia.org/ Wikipedia] pages).<br />
<br />
=== Linking ===<br />
Linking to pages is explained in detail [http://www.mediawiki.org/wiki/Help:Links here]. Here is an example link to the MegaDrum article on {{SITENAME}} (this is an example of linking between {{SITENAME}} pages):<br />
<br />
<pre>[[MegaDrum]]</pre><br />
<br />
This will give the following output:<br />
<br />
[[MegaDrum]]<br />
<br />
Remember that it is bad practice to link every single word because this brings confusion to the reader.<br />
<br />
=== Article sections ===<br />
Dividing your article into sections is a good idea to separate different important parts of information from each other. To add a new section to the article use this code:<br />
<br />
<pre>==New section==</pre><br />
<br />
And if you need a subsection, type:<br />
<br />
<pre>===New section subsection===</pre><br />
<br />
More information can be obtained [http://meta.wikimedia.org/wiki/Help:Section here].<br />
<br />
If an article contains multiple sections, a table of contents will be automatically shown in the beginning of the page.<br />
<br />
=== Templates ===<br />
This is one of the most amazing features of MediaWiki. Templates are actually regular MediaWiki pages that can be inserted into other pages. However, parameters can be passed to templates that make them really flexible.<br />
<br />
To invoke an existing template you use the code<br />
<br />
<pre>{{Template_name}}</pre><br />
<br />
For example, here is the <nowiki>{{</nowiki>[[Template:LCD|LCD]]<nowiki>}}</nowiki> template without parameters. The code to invoke it is:<br />
<pre>{{LCD}}</pre><br />
<br />
This code will render:<br />
{{LCD}}<br />
<br />
And here is an example of the template with parameters:<br />
<pre>{{LCD|<br />
color=white|<br />
float=right|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2♦|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}</pre><br />
<br />
This renders the following: {{LCD|<br />
color=white|<br />
float=right|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2♦|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
<br />
Templates usually come with documentation on how to use them. If you are making a new template please take some time to document its features. Do this by adding a '''doc''' subpage to your template. More info on this [[Template:Documentation|here]].<br />
<br />
=== Adding images ===<br />
This is neatly documented [http://www.mediawiki.org/wiki/Help:Images here]. Everything else falls under the [[#Guidelines|guidelines]] part of this page.<br />
<br />
=== Adding videos ===<br />
Currently there is two ways for doing this. One is invoking the video template, for example:<br />
<pre>{{video|<br />
url=http://www.youtube.com/watch?v=-7u4USyw0gU|<br />
desc=How to remove the ATmega MCU from its socket}}</pre><br />
<br />
This renders:<br />
<br />
{{video|<br />
url=http://www.youtube.com/watch?v=-7u4USyw0gU|<br />
desc=How to remove the ATMega MCU from its socket}}<br />
<br />
Another way is to insert a video directly into the page using this syntax:<br />
<br />
<pre>{{#ev:youtube|-7u4USyw0gU|250|right|How to remove the ATmega MCU from its socket}}</pre><br />
<br />
The video may appear outside of the parent section. Please note, that <nowiki>{{#ev:...}}</nowiki> is '''not''' a template but a special extension.<br />
<br />
=== References ===<br />
References can be used as footnotes. Here is an example.<br />
<br />
<pre>Here is some information that has an associated note.<ref group="notes">This is the note.</ref></pre><br />
<br />
This will render:<br />
Here is some information that has an associated note.<ref group="notes">This is the note.</ref><br />
<br />
Notes are usually added to the bottom of the page by using something like<br />
<br />
<pre>== Notes ==<br />
<references group="notes" /></pre><br />
<br />
More about references [http://www.mediawiki.org/wiki/Extension:Cite/Cite.php here].<br />
<br />
=== wikEd ===<br />
This extension can come in handy for simplifying editing articles. It can be installed for example as a Greasemonkey script in Firefox. Read more about it [http://www.mediawiki.org/wiki/Extension:WikEd here].<br />
<br />
== Guidelines ==<br />
This section contains some basic guidelines to help you get started writing (editing) articles.<br />
<br />
=== Writing ===<br />
The main goal of writing wiki articles is to provide the reader with required information. Writing quality material is the second goal. When writing articles periodically check that:<br />
* You maintain a good informative level of expression and provide enough (but not too much) links to pages with explanatory material. In other words, the article should be understandable by both beginners and advanced users;<br />
* Your writing/editing results in a quality article render. You should use the preview button.<br />
<br />
If you can, check pages with multiple applied CSS styles in a variety of browsers to determine display errors. If any exist, first post a report to the discussion page. However, if you are completely certain you can easily fix this, please do so.<br />
<br />
=== When to link to a main article? ===<br />
When the topic in question is important and requires detailed explanation. Invoke the <nowiki>{{</nowiki>[[Template:Main|Main]]<nowiki>}}</nowiki> template like so:<br />
<br />
<pre><br />
== Section title (or subsection, etc.) ==<br />
{{Main|Your_article}}<br />
</pre><br />
<br />
=== Linking ===<br />
When you link to a {{SITENAME}} page using the <nowiki>[[Some_page]]</nowiki> syntax the link will be displayed regardless of the page existence which gives the reader with editing rights the ability to create it. This is useful, however sometimes it is better to use a different type of linking, especially when a similar page exists in Wikipedia or any other wiki. Then there is simply no need to recreate it for {{SITENAME}}.<br />
<br />
Here is a concrete example. Suppose we want to let the reader know what DIY stands for. Instead of linking it to a {{SITENAME}} page we can link to Wikipedia using the following syntax:<br />
<pre>[[Wikipedia:do-it-yourself|DIY]]</pre><br />
Which gives the following output:<br />
[[Wikipedia:do-it-yourself|DIY]]<br />
<br />
=== Editing existing pages ===<br />
Only edit existing ''quality'' pages when:<br />
* You know what you are doing;<br />
* You've found a spelling or factual error that you know how to correct;<br />
* You can provide more useful information (i.e. expand an article).<br />
<br />
This is important because only registered wiki users are given editing rights. This means that an article will usually have few authors and sudden changes in an article may cause conflicts. So the best thing you can do in case you think that the article is either severly outdated or needs to be rewritten is to go to the article talk page first (accessible by clicking the page discussion tab) and sharing your thoughts with the rest of the users.<br />
<br />
'''Always preview pages first'''. Also remember to check ''This is a minor edit'' checkbox before saving a page when making only a minor edit.<br />
<br />
Be especially careful when editing templates. These are used on multiple pages and thus must be handled with care.<br />
<br />
=== Inserting images ===<br />
It is good practice to insert images with secondary illustrative purpose as thumbnails. The width of those thumbnails should not exceed 250 pixels. This takes into account the variety of display settings used to view the wiki pages and should work for everyone. Also, these thumbnails should be aligned right (this is the default setting).<br />
<br />
=== Inserting videos ===<br />
When to insert videos as links within a box notification:<br />
* When the content of an article can be replaced by viewing the video<br />
* When the video is accompanied by quality annotations and/or comments<br />
<br />
When to embed videos into pages:<br />
* When the videos are used as accompanying material<br />
<br />
The same rule applies for embedded videos as for inserting image thumbnails: use max 250 pixel widths and keep the aligned to the right of the page.<br />
<br />
=== Unfinished articles ===<br />
If you think that the article suffers from too little informative quality you can insert the template <nowiki>{{</nowiki>[[Template:Stub|Stub]]<nowiki>}}</nowiki> at the top (or bottom) of the page. Please use this sparingly.<br />
<br />
=== Writing translations ===<br />
The preferred language for this wiki is English. In order to write a translation make a subpage for your language for the main page. E.g. for a Russian translation of the [[MegaDrum]] page, make a [[MegaDrum/ru]] subpage. After the translation is complete, insert the language bar on the top of the parent and child pages by invoking the <nowiki>{{</nowiki>[[Template:Languages|Languages]]<nowiki>}}</nowiki> template like so:<br />
<br />
<pre>{{Languages}}</pre><br />
<br />
This will render the language bar:<br />
<br />
{{Languages}}<br />
<br />
=== Conclusion ===<br />
Keep in mind that these are only general guidelines and that there may be exceptions. Thank you for taking your time reading this. We are looking forward to your contributions.<br />
<br />
== Notes ==<br />
<references group="notes" /></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Talk:SuperiorDrummer2&diff=131Talk:SuperiorDrummer22010-09-14T08:00:40Z<p>Firelord: </p>
<hr />
<div>todo<br />
<br />
# add more step by step detail plus screen shots on how to do the hi-hat pedal correction in SD2<br />
<br />
--[[User:Dm9876|Dm9876]] 11:32, 13 August 2010 (UTC)<br />
: Added a table style that should improve readability. [[User:Firelord|Firelord]] 08:00, 14 September 2010 (UTC)</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=SuperiorDrummer2&diff=130SuperiorDrummer22010-09-14T07:57:37Z<p>Firelord: </p>
<hr />
<div>__NOTOC__ {{#css:Table.css}}<br />
==Setting up MegaDrum and Superior Drummer 2==<br />
'''Scope:'''<br />
* Quick setup for Superior Drummer 2 (SD2)<br />
* MIDI mapping for MegaDrum (MD)<br />
* Not covering how to make MD settings OR advanced features of SD2.<br />
<br />
'''Prerequisites:'''<br />
* Low latency audio setup in Windows ([[Wikipedia:Audio_Stream_Input/Output|ASIO]])<br />
* Tuning of MegaDrum to suit your kit - ([http://www.megadrum.info/content/megadrum-configuration MD configuration])<br />
* MegaDrum connected to the PC via traditional MIDI interface or MIDI over USB interface<br />
* Installation of Superior Drummer 2.2.1 and ToonTrack Solo 1.2.2 software<br />
<br />
'''Notes:'''<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
==Steps to setup SD2==<br />
* Start 'ToonTrack Solo' program, Select Drummer to use 'Superior Drummer 2' (in other words start a new project).<br />
* 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.<br />
* Options->Audio->Audio Device, Choose device type 'ASIO' output driver 'ASIO4ALL v2', OK<br />
* Options->Audio->Latency Settings, Choose the lowest possible setting without the audio breaking up. More info here: [[Configuring ASIO drivers]]<br />
* By left clicking on the images of the drums or cymbals you should now hear sound<br />
* Options->Controller, make sure to tick both 'e-drums' and 'cc offset'<br />
* Options->MIDI Devices, Select your MegaDrum (may appear simply as 'USB Audio Device')<br />
* 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.<br />
* You might be able now to quickly verify operation by using the Kick Drum since this mapping is probably already correct (Note number 36)<br />
<br />
==MIDI Map to set in your MegaDrum==<br />
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.<br />
<br />
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)<br />
<br />
? -> Ny avatar -> MIDI Layout, this opens the pdf file 'Avatar1Keys.pdf' or you can open the pdf file directly now you know the name.<br />
<br />
Anyway never mind about that as I will spell out the mappings that you might want to set in the MegaDrum here:<br />
<br />
{| class="wikitable"<br />
| align="center" style="background:#f0f0f0;"|'''MD Name'''<br />
| align="center" style="background:#f0f0f0;"|'''MD Setting'''<br />
| align="center" style="background:#f0f0f0;"|'''SD2 Default'''<br />
| align="center" style="background:#f0f0f0;"|'''SD2 Name'''<br />
| align="center" style="background:#f0f0f0;"|'''Articulation'''<br />
| align="center" style="background:#f0f0f0;"|'''Optional custom tuning'''<br />
| align="center" style="background:#f0f0f0;"|'''Notes'''<br />
|-<br />
| HiHat Pedal||CC Value||CC04||Hats||hatsCtrl||Pedal correction||HiHat Pedal->Type: F.Contr (so it sends cc messages) cc04 is the default<br />
|-<br />
| HiHat Pedal||Bow*||19||Hats||TipTrig||||* represents 4 separate settings for SO, HO, SCL, CL (or 2 separate settings in firmware < 20100613)<br />
|-<br />
| HiHat Pedal||Edge*||18||Hats||Trig||||<br />
|-<br />
| HiHat Pedal||Bell*||20||Hats||BellTrig||||<br />
|-<br />
| HiHat Pedal||Chick||21||Hats||Pedal||||<br />
|-<br />
| HiHat Pedal||Splsh||23||Hats||FootSplash||||<br />
|-<br />
| Ch01: Kick||Note||36||Kick||Kick||||<br />
|-<br />
| 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<br />
|-<br />
| Ch03: HiHatE||Note||18||Hats||Trig||||<br />
|-<br />
| Ch03: HiHatE||BNote||20||Hats||BellTrig||||(3rd zone)<br />
|-<br />
| Ch04: SnareH||Note||38||Snare||Center||||<br />
|-<br />
| ||||CC16||Snare||SnareCtrl||||cc16 is the default for MD but you need to enable the positional sensing feature (firmware >= 20100516 only)<br />
|-<br />
| Ch05: SnareR||Note||40||Snare||RimShot||||<br />
|-<br />
| Ch06: RideB||Note||51||Ride4||Ride||Aftertouch||<br />
|-<br />
| Ch07: RideE||Note||59||Ride4||Punch||Aftertouch||<br />
|-<br />
| Ch07: RideE||BNote||53||Ride4||Bell||||(3rd zone)<br />
|-<br />
| Ch08: CrashB||Note||49||Cymbal2||Crashed||Aftertouch||CrashA<br />
|-<br />
| Ch09: CrashE||||n/a||n/a||n/a||||<br />
|-<br />
| Ch10: Tom1H||Note||48||RackTom1||Center||||<br />
|-<br />
| Ch11: Tom1R||Note||82||RackTom1||RimShot||||<br />
|-<br />
| Ch12: Tom2H||Note||47||RackTom2||Center||||<br />
|-<br />
| Ch13: Tom2R||Note||80||RackTom2||RimShot||||<br />
|-<br />
| Ch14: Tom3H||Note||45||RackTom3||Center||||<br />
|-<br />
| Ch15: Tom3R||Note||78||RackTom3||RimShot||||<br />
|-<br />
| Ch16: Tom4H||Note||43||FloorTom1||Center||||<br />
|-<br />
| Ch17: Tom4R||Note||75||FloorTom1||RimShot||||<br />
|-<br />
| Ch18: Aux1H||Note||41||FloorTom2||Center||||<br />
|-<br />
| Ch19: Aux1R||Note||73||FloorTom2||RimShot||||<br />
|-<br />
| Ch20: Aux2H||Note||57||Cymbal5||Crashed||Aftertouch||CrashB<br />
|-<br />
| Ch21: Aux2R||||n/a||n/a||n/a||||<br />
|-<br />
| Ch22: Aux3H||||||||||||<br />
|-<br />
| Ch23: Aux3R||||||||||||<br />
|-<br />
| Ch24: Aux4H||||||||||||<br />
|-<br />
| Ch25: Aux4R||||||||||||<br />
|-<br />
| Ch26: Aux5H||||||||||||<br />
|-<br />
| Ch27: Aux5R||||||||||||<br />
|-<br />
| Ch28: Aux6H||Note||55||Cymbal3||Crashed||||Splash<br />
|-<br />
| Ch29: Aux6R||Note||52||Cymbal1||Crashed||||China - position not loaded by default<br />
|-<br />
| Ch30: Aux7H||Note||56||Cowbell||Cowbell||||position not loaded by default<br />
|-<br />
| Ch31: Aux7R||||||||||||<br />
|- <br />
|}<br />
<br />
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]] <br />
<br />
All done - everything should work.<br />
<br />
'''Notes:'''<br />
* 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.<br />
* 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).<br />
<br />
==Some more detailed adjustments in SD2==<br />
Note: some more (or less) detail on the following can be found via menu ?->Operation Manual in SD ("Superior_Drummer_Operation_Manual.pdf" file)<br />
<br />
===Cymbal Chokes===<br />
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 <br />
<br />
assignment. If you want to make use of this in SD2, you need to enable the feature as follows:<br />
<br />
[[File:SD2-Aftertouch+.png]]<br />
<br />
# Select the cymbal (right click on the graphic or select it from the drop down)<br />
# 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<br />
# Turn on the 'edit articulation only' filter<br />
# Enable the envelope<br />
# Move the switch to the 'Aftertouch' position<br />
# Drag the 'release' parameter or click and set the time directly. You can also change the 'hold' parameter <br />
<br />
===High-Hat Pedal Correction===<br />
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)<br />
<br />
To get the proper sounds using the SD2 defaults, the end result should be:<br />
<br />
* Closed (pedal down).. cc04 value >120<br />
* Tight closed (pedal down with heel up) cc04 value = 127 (max) possibly also 126 counts as tight, not sure<br />
<br />
the easiest way to see these numbers is with [[MCT]]<br />
<br />
To do the tuning in SD2 refer to SD2 Operation Manual section 7.3<br />
<br />
(todo)<br />
<br />
==Notes==<br />
<br />
Some SD2 settings that may be of interest.. ('Settings' menu in SD2)<br />
<br />
* 'MIDI keys as numbers'</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=SuperiorDrummer2&diff=129SuperiorDrummer22010-09-14T07:50:33Z<p>Firelord: </p>
<hr />
<div>__NOTOC__ {{#css:Table.css}}<br />
==Setting up MegaDrum and Superior Drummer 2==<br />
'''Scope:'''<br />
* Quick setup for Superior Drummer 2 (SD2)<br />
* MIDI mapping for MegaDrum (MD)<br />
* Not covering how to make MD settings OR advanced features of SD2.<br />
<br />
'''Prerequisites:'''<br />
* Low latency audio setup in Windows ([[ASIO]])<br />
* Tuning of MegaDrum to suit your kit - ([http://www.megadrum.info/content/megadrum-configuration MD configuration])<br />
* MegaDrum connected to the PC via traditional MIDI interface or MIDI over USB interface<br />
* Installation of Superior Drummer 2.2.1 and ToonTrack Solo 1.2.2 software<br />
<br />
'''Notes:'''<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
==Steps to setup SD2==<br />
* Start 'ToonTrack Solo' program, Select Drummer to use 'Superior Drummer 2' (in other words start a new project).<br />
* 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.<br />
* Options->Audio->Audio Device, Choose device type 'ASIO' output driver 'ASIO4ALL v2', OK<br />
* Options->Audio->Latency Settings, Choose the lowest possible setting without the audio breaking up. More info here: [[ASIO]]<br />
* By left clicking on the images of the drums or cymbals you should now hear sound<br />
* Options->Controller, make sure to tick both 'e-drums' and 'cc offset'<br />
* Options->MIDI Devices, Select your MegaDrum (may appear simply as 'USB Audio Device')<br />
* 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.<br />
* You might be able now to quickly verify operation by using the Kick Drum since this mapping is probably already correct (Note number 36)<br />
<br />
==MIDI Map to set in your MegaDrum==<br />
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.<br />
<br />
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)<br />
<br />
? -> Ny avatar -> MIDI Layout, this opens the pdf file 'Avatar1Keys.pdf' or you can open the pdf file directly now you know the name.<br />
<br />
Anyway never mind about that as I will spell out the mappings that you might want to set in the MegaDrum here:<br />
<br />
{| class="wikitable"<br />
| align="center" style="background:#f0f0f0;"|'''MD Name'''<br />
| align="center" style="background:#f0f0f0;"|'''MD Setting'''<br />
| align="center" style="background:#f0f0f0;"|'''SD2 Default'''<br />
| align="center" style="background:#f0f0f0;"|'''SD2 Name'''<br />
| align="center" style="background:#f0f0f0;"|'''Articulation'''<br />
| align="center" style="background:#f0f0f0;"|'''Optional custom tuning'''<br />
| align="center" style="background:#f0f0f0;"|'''Notes'''<br />
|-<br />
| HiHat Pedal||CC Value||CC04||Hats||hatsCtrl||Pedal correction||HiHat Pedal->Type: F.Contr (so it sends cc messages) cc04 is the default<br />
|-<br />
| HiHat Pedal||Bow*||19||Hats||TipTrig||||* represents 4 separate settings for SO, HO, SCL, CL (or 2 separate settings in firmware < 20100613)<br />
|-<br />
| HiHat Pedal||Edge*||18||Hats||Trig||||<br />
|-<br />
| HiHat Pedal||Bell*||20||Hats||BellTrig||||<br />
|-<br />
| HiHat Pedal||Chick||21||Hats||Pedal||||<br />
|-<br />
| HiHat Pedal||Splsh||23||Hats||FootSplash||||<br />
|-<br />
| Ch01: Kick||Note||36||Kick||Kick||||<br />
|-<br />
| 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<br />
|-<br />
| Ch03: HiHatE||Note||18||Hats||Trig||||<br />
|-<br />
| Ch03: HiHatE||BNote||20||Hats||BellTrig||||(3rd zone)<br />
|-<br />
| Ch04: SnareH||Note||38||Snare||Center||||<br />
|-<br />
| ||||CC16||Snare||SnareCtrl||||cc16 is the default for MD but you need to enable the positional sensing feature (firmware >= 20100516 only)<br />
|-<br />
| Ch05: SnareR||Note||40||Snare||RimShot||||<br />
|-<br />
| Ch06: RideB||Note||51||Ride4||Ride||Aftertouch||<br />
|-<br />
| Ch07: RideE||Note||59||Ride4||Punch||Aftertouch||<br />
|-<br />
| Ch07: RideE||BNote||53||Ride4||Bell||||(3rd zone)<br />
|-<br />
| Ch08: CrashB||Note||49||Cymbal2||Crashed||Aftertouch||CrashA<br />
|-<br />
| Ch09: CrashE||||n/a||n/a||n/a||||<br />
|-<br />
| Ch10: Tom1H||Note||48||RackTom1||Center||||<br />
|-<br />
| Ch11: Tom1R||Note||82||RackTom1||RimShot||||<br />
|-<br />
| Ch12: Tom2H||Note||47||RackTom2||Center||||<br />
|-<br />
| Ch13: Tom2R||Note||80||RackTom2||RimShot||||<br />
|-<br />
| Ch14: Tom3H||Note||45||RackTom3||Center||||<br />
|-<br />
| Ch15: Tom3R||Note||78||RackTom3||RimShot||||<br />
|-<br />
| Ch16: Tom4H||Note||43||FloorTom1||Center||||<br />
|-<br />
| Ch17: Tom4R||Note||75||FloorTom1||RimShot||||<br />
|-<br />
| Ch18: Aux1H||Note||41||FloorTom2||Center||||<br />
|-<br />
| Ch19: Aux1R||Note||73||FloorTom2||RimShot||||<br />
|-<br />
| Ch20: Aux2H||Note||57||Cymbal5||Crashed||Aftertouch||CrashB<br />
|-<br />
| Ch21: Aux2R||||n/a||n/a||n/a||||<br />
|-<br />
| Ch22: Aux3H||||||||||||<br />
|-<br />
| Ch23: Aux3R||||||||||||<br />
|-<br />
| Ch24: Aux4H||||||||||||<br />
|-<br />
| Ch25: Aux4R||||||||||||<br />
|-<br />
| Ch26: Aux5H||||||||||||<br />
|-<br />
| Ch27: Aux5R||||||||||||<br />
|-<br />
| Ch28: Aux6H||Note||55||Cymbal3||Crashed||||Splash<br />
|-<br />
| Ch29: Aux6R||Note||52||Cymbal1||Crashed||||China - position not loaded by default<br />
|-<br />
| Ch30: Aux7H||Note||56||Cowbell||Cowbell||||position not loaded by default<br />
|-<br />
| Ch31: Aux7R||||||||||||<br />
|- <br />
|}<br />
<br />
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]] <br />
<br />
All done - everything should work.<br />
<br />
'''Notes:'''<br />
* 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.<br />
* 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).<br />
<br />
==Some more detailed adjustments in SD2==<br />
Note: some more (or less) detail on the following can be found via menu ?->Operation Manual in SD ("Superior_Drummer_Operation_Manual.pdf" file)<br />
<br />
===Cymbal Chokes===<br />
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 <br />
<br />
assignment. If you want to make use of this in SD2, you need to enable the feature as follows:<br />
<br />
[[File:SD2-Aftertouch+.png]]<br />
<br />
# Select the cymbal (right click on the graphic or select it from the drop down)<br />
# 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<br />
# Turn on the 'edit articulation only' filter<br />
# Enable the envelope<br />
# Move the switch to the 'Aftertouch' position<br />
# Drag the 'release' parameter or click and set the time directly. You can also change the 'hold' parameter <br />
<br />
===High-Hat Pedal Correction===<br />
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)<br />
<br />
To get the proper sounds using the SD2 defaults, the end result should be:<br />
<br />
* Closed (pedal down).. cc04 value >120<br />
* Tight closed (pedal down with heel up) cc04 value = 127 (max) possibly also 126 counts as tight, not sure<br />
<br />
the easiest way to see these numbers is with [[MCT]]<br />
<br />
To do the tuning in SD2 refer to SD2 Operation Manual section 7.3<br />
<br />
(todo)<br />
<br />
==Notes==<br />
<br />
Some SD2 settings that may be of interest.. ('Settings' menu in SD2)<br />
<br />
* 'MIDI keys as numbers'</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Table.css&diff=128Table.css2010-09-14T07:45:48Z<p>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…'</p>
<hr />
<div>table.wikitable<br />
{<br />
margin: 1em 1em 1em 0;<br />
background: #f9f9f9;<br />
border: 1px #aaa solid;<br />
border-collapse: collapse;<br />
}<br />
<br />
.wikitable th,<br />
.wikitable td<br />
{<br />
border: 1px #aaa solid;<br />
padding: 0.2em;<br />
}<br />
<br />
.wikitable th<br />
{<br />
background: #f2f2f2;<br />
text-align: center;<br />
}<br />
<br />
.wikitable caption<br />
{<br />
font-weight: bold;<br />
}</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=SuperiorDrummer2&diff=127SuperiorDrummer22010-09-14T07:32:06Z<p>Firelord: /* Setting up MegaDrum and Superior Drummer 2 */</p>
<hr />
<div>__NOTOC__<br />
==Setting up MegaDrum and Superior Drummer 2==<br />
'''Scope:'''<br />
* Quick setup for Superior Drummer 2 (SD2)<br />
* MIDI mapping for MegaDrum (MD)<br />
* Not covering how to make MD settings OR advanced features of SD2.<br />
<br />
'''Prerequisites:'''<br />
* Low latency audio setup in Windows ([[ASIO]])<br />
* Tuning of MegaDrum to suit your kit - ([http://www.megadrum.info/content/megadrum-configuration MD configuration])<br />
* MegaDrum connected to the PC via traditional MIDI interface or MIDI over USB interface<br />
* Installation of Superior Drummer 2.2.1 and ToonTrack Solo 1.2.2 software<br />
<br />
'''Notes:'''<br />
* 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.<br />
* 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.<br />
* 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.<br />
<br />
==Steps to setup SD2==<br />
* Start 'ToonTrack Solo' program, Select Drummer to use 'Superior Drummer 2' (in other words start a new project).<br />
* 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.<br />
* Options->Audio->Audio Device, Choose device type 'ASIO' output driver 'ASIO4ALL v2', OK<br />
* Options->Audio->Latency Settings, Choose the lowest possible setting without the audio breaking up. More info here: [[ASIO]]<br />
* By left clicking on the images of the drums or cymbals you should now hear sound<br />
* Options->Controller, make sure to tick both 'e-drums' and 'cc offset'<br />
* Options->MIDI Devices, Select your MegaDrum (may appear simply as 'USB Audio Device')<br />
* 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.<br />
* You might be able now to quickly verify operation by using the Kick Drum since this mapping is probably already correct (Note number 36)<br />
<br />
==MIDI Map to set in your MegaDrum==<br />
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.<br />
<br />
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)<br />
<br />
? -> Ny avatar -> MIDI Layout, this opens the pdf file 'Avatar1Keys.pdf' or you can open the pdf file directly now you know the name.<br />
<br />
Anyway never mind about that as I will spell out the mappings that you might want to set in the MegaDrum here:<br />
<br />
{| {{table}}<br />
| align="center" style="background:#f0f0f0;"|'''MD Name'''<br />
| align="center" style="background:#f0f0f0;"|'''MD Setting'''<br />
| align="center" style="background:#f0f0f0;"|'''SD2 Default'''<br />
| align="center" style="background:#f0f0f0;"|'''SD2 Name'''<br />
| align="center" style="background:#f0f0f0;"|'''Articulation'''<br />
| align="center" style="background:#f0f0f0;"|'''Optional custom tuning'''<br />
| align="center" style="background:#f0f0f0;"|'''Notes'''<br />
|-<br />
| HiHat Pedal||CC Value||CC04||Hats||hatsCtrl||Pedal correction||HiHat Pedal->Type: F.Contr (so it sends cc messages) cc04 is the default<br />
|-<br />
| HiHat Pedal||Bow*||19||Hats||TipTrig||||* represents 4 separate settings for SO, HO, SCL, CL (or 2 separate settings in firmware < 20100613)<br />
|-<br />
| HiHat Pedal||Edge*||18||Hats||Trig||||<br />
|-<br />
| HiHat Pedal||Bell*||20||Hats||BellTrig||||<br />
|-<br />
| HiHat Pedal||Chick||21||Hats||Pedal||||<br />
|-<br />
| HiHat Pedal||Splsh||23||Hats||FootSplash||||<br />
|-<br />
| Ch01: Kick||Note||36||Kick||Kick||||<br />
|-<br />
| 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<br />
|-<br />
| Ch03: HiHatE||Note||18||Hats||Trig||||<br />
|-<br />
| Ch03: HiHatE||BNote||20||Hats||BellTrig||||(3rd zone)<br />
|-<br />
| Ch04: SnareH||Note||38||Snare||Center||||<br />
|-<br />
| ||||CC16||Snare||SnareCtrl||||cc16 is the default for MD but you need to enable the positional sensing feature (firmware >= 20100516 only)<br />
|-<br />
| Ch05: SnareR||Note||40||Snare||RimShot||||<br />
|-<br />
| Ch06: RideB||Note||51||Ride4||Ride||Aftertouch||<br />
|-<br />
| Ch07: RideE||Note||59||Ride4||Punch||Aftertouch||<br />
|-<br />
| Ch07: RideE||BNote||53||Ride4||Bell||||(3rd zone)<br />
|-<br />
| Ch08: CrashB||Note||49||Cymbal2||Crashed||Aftertouch||CrashA<br />
|-<br />
| Ch09: CrashE||||n/a||n/a||n/a||||<br />
|-<br />
| Ch10: Tom1H||Note||48||RackTom1||Center||||<br />
|-<br />
| Ch11: Tom1R||Note||82||RackTom1||RimShot||||<br />
|-<br />
| Ch12: Tom2H||Note||47||RackTom2||Center||||<br />
|-<br />
| Ch13: Tom2R||Note||80||RackTom2||RimShot||||<br />
|-<br />
| Ch14: Tom3H||Note||45||RackTom3||Center||||<br />
|-<br />
| Ch15: Tom3R||Note||78||RackTom3||RimShot||||<br />
|-<br />
| Ch16: Tom4H||Note||43||FloorTom1||Center||||<br />
|-<br />
| Ch17: Tom4R||Note||75||FloorTom1||RimShot||||<br />
|-<br />
| Ch18: Aux1H||Note||41||FloorTom2||Center||||<br />
|-<br />
| Ch19: Aux1R||Note||73||FloorTom2||RimShot||||<br />
|-<br />
| Ch20: Aux2H||Note||57||Cymbal5||Crashed||Aftertouch||CrashB<br />
|-<br />
| Ch21: Aux2R||||n/a||n/a||n/a||||<br />
|-<br />
| Ch22: Aux3H||||||||||||<br />
|-<br />
| Ch23: Aux3R||||||||||||<br />
|-<br />
| Ch24: Aux4H||||||||||||<br />
|-<br />
| Ch25: Aux4R||||||||||||<br />
|-<br />
| Ch26: Aux5H||||||||||||<br />
|-<br />
| Ch27: Aux5R||||||||||||<br />
|-<br />
| Ch28: Aux6H||Note||55||Cymbal3||Crashed||||Splash<br />
|-<br />
| Ch29: Aux6R||Note||52||Cymbal1||Crashed||||China - position not loaded by default<br />
|-<br />
| Ch30: Aux7H||Note||56||Cowbell||Cowbell||||position not loaded by default<br />
|-<br />
| Ch31: Aux7R||||||||||||<br />
|-<br />
| <br />
|}<br />
<br />
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]] <br />
<br />
All done - everything should work.<br />
<br />
'''Notes:'''<br />
* 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.<br />
* 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).<br />
<br />
==Some more detailed adjustments in SD2==<br />
Note: some more (or less) detail on the following can be found via menu ?->Operation Manual in SD ("Superior_Drummer_Operation_Manual.pdf" file)<br />
<br />
===Cymbal Chokes===<br />
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 <br />
<br />
assignment. If you want to make use of this in SD2, you need to enable the feature as follows:<br />
<br />
[[File:SD2-Aftertouch+.png]]<br />
<br />
# Select the cymbal (right click on the graphic or select it from the drop down)<br />
# 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<br />
# Turn on the 'edit articulation only' filter<br />
# Enable the envelope<br />
# Move the switch to the 'Aftertouch' position<br />
# Drag the 'release' parameter or click and set the time directly. You can also change the 'hold' parameter <br />
<br />
===High-Hat Pedal Correction===<br />
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)<br />
<br />
To get the proper sounds using the SD2 defaults, the end result should be:<br />
<br />
* Closed (pedal down).. cc04 value >120<br />
* Tight closed (pedal down with heel up) cc04 value = 127 (max) possibly also 126 counts as tight, not sure<br />
<br />
the easiest way to see these numbers is with [[MCT]]<br />
<br />
To do the tuning in SD2 refer to SD2 Operation Manual section 7.3<br />
<br />
(todo)<br />
<br />
==Notes==<br />
<br />
Some SD2 settings that may be of interest.. ('Settings' menu in SD2)<br />
<br />
* 'MIDI keys as numbers'</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Help:Contents&diff=126Help:Contents2010-09-05T14:33:56Z<p>Firelord: /* Editing existing pages */</p>
<hr />
<div>'''Welcome to the {{SITENAME}} help section!''' This page currently contains:<br />
* General formatting documentation to help you get started writing articles;<br />
* Some guidelines on writing new/editing articles for {{SITENAME}}.<br />
<br />
'''Please read the following carefully especially if you haven't worked with MediaWiki based projects before.'''<br />
<br />
If you are looking for help with building/buying/troubleshooting MegaDrum, please refer to the [http://www.megadrum.info/ forums] for now.<br />
<br />
== MediaWiki markup ==<br />
<br />
=== Basic formatting ===<br />
The most important part of a MediaWiki article is meaningful plain text. However, formatting is required to deliver rich content. Basically, you enter text with special control characters/structures to get formatting effects. For example, to get '''bold''' text you would enter the following:<br />
<br />
<pre>'''This text is bold'''</pre><br />
<br />
This will render:<br />
<br />
'''This text is bold'''<br />
<br />
Please refer to the [http://www.mediawiki.org/wiki/Help:Formatting basic formatting documentation]. You can also learn the formatting rules from viewing the content of existing MediaWiki pages (e.g. [http://wikipedia.org/ Wikipedia] pages).<br />
<br />
=== Linking ===<br />
Linking to pages is explained in detail [http://www.mediawiki.org/wiki/Help:Links here]. Here is an example link to the MegaDrum article on {{SITENAME}} (this is an example of linking between {{SITENAME}} pages):<br />
<br />
<pre>[[MegaDrum]]</pre><br />
<br />
This will give the following output:<br />
<br />
[[MegaDrum]]<br />
<br />
Remember that it is bad practice to link every single word because this brings confusion to the reader.<br />
<br />
=== Article sections ===<br />
Dividing your article into sections is a good idea to separate different important parts of information from each other. To add a new section to the article use this code:<br />
<br />
<pre>==New section==</pre><br />
<br />
And if you need a subsection, type:<br />
<br />
<pre>===New section subsection===</pre><br />
<br />
More information can be obtained [http://meta.wikimedia.org/wiki/Help:Section here].<br />
<br />
If an article contains multiple sections, a table of contents will be automatically shown in the beginning of the page.<br />
<br />
=== Templates ===<br />
This is one of the most amazing features of MediaWiki. Templates are actually regular MediaWiki pages that can be inserted into other pages. However, parameters can be passed to templates that make them really flexible.<br />
<br />
To invoke an existing template you use the code<br />
<br />
<pre>{{Template_name}}</pre><br />
<br />
For example, here is the <nowiki>{{</nowiki>[[Template:LCD|LCD]]<nowiki>}}</nowiki> template without parameters. The code to invoke it is:<br />
<pre>{{LCD}}</pre><br />
<br />
This code will render:<br />
{{LCD}}<br />
<br />
And here is an example of the template with parameters:<br />
<pre>{{LCD|<br />
color=white|<br />
float=right|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2♦|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}</pre><br />
<br />
This renders the following: {{LCD|<br />
color=white|<br />
float=right|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2♦|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
<br />
Templates usually come with documentation on how to use them. If you are making a new template please take some time to document its features. Do this by adding a '''doc''' subpage to your template. More info on this [[Template:Documentation|here]].<br />
<br />
=== Adding images ===<br />
This is neatly documented [http://www.mediawiki.org/wiki/Help:Images here]. Everything else falls under the [[#Guidelines|guidelines]] part of this page.<br />
<br />
=== Adding videos ===<br />
Currently there is two ways for doing this. One is invoking the video template, for example:<br />
<pre>{{video|<br />
url=http://www.youtube.com/watch?v=-7u4USyw0gU|<br />
desc=How to remove the ATmega MCU from its socket}}</pre><br />
<br />
This renders:<br />
<br />
{{video|<br />
url=http://www.youtube.com/watch?v=-7u4USyw0gU|<br />
desc=How to remove the ATMega MCU from its socket}}<br />
<br />
Another way is to insert a video directly into the page using this syntax:<br />
<br />
<pre>{{#ev:youtube|-7u4USyw0gU|250|right|How to remove the ATmega MCU from its socket}}</pre><br />
{{#ev:youtube|-7u4USyw0gU|250|right|How to remove the ATmega MCU from its socket}}<br />
<br />
You should see the result of this on the right of the page: it may appear outside of the parent section. Please note, that <nowiki>{{#ev:...}}</nowiki> is '''not''' a template but a special extension.<br />
<br />
=== References ===<br />
References can be used as footnotes. Here is an example.<br />
<br />
<pre>Here is some information that has an associated note.<ref group="notes">This is the note.</ref></pre><br />
<br />
This will render:<br />
Here is some information that has an associated note.<ref group="notes">This is the note.</ref><br />
<br />
Notes are usually added to the bottom of the page by using something like<br />
<br />
<pre>== Notes ==<br />
<references group="notes" /></pre><br />
<br />
More about references [http://www.mediawiki.org/wiki/Extension:Cite/Cite.php here].<br />
<br />
=== wikEd ===<br />
This extension can come in handy for simplifying editing articles. It can be installed for example as a Greasemonkey script in Firefox. Read more about it [http://www.mediawiki.org/wiki/Extension:WikEd here].<br />
<br />
== Guidelines ==<br />
This section contains some basic guidelines to help you get started writing (editing) articles.<br />
<br />
=== Writing ===<br />
The main goal of writing wiki articles is to provide the reader with required information. Writing quality material is the second goal. When writing articles periodically check that:<br />
* You maintain a good informative level of expression and provide enough (but not too much) links to pages with explanatory material. In other words, the article should be understandable by both beginners and advanced users;<br />
* Your writing/editing results in a quality article render. You should use the preview button.<br />
<br />
If you can, check pages with multiple applied CSS styles in a variety of browsers to determine display errors. If any exist, first post a report to the discussion page. However, if you are completely certain you can easily fix this, please do so.<br />
<br />
=== When to link to a main article? ===<br />
When the topic in question is important and requires detailed explanation. Invoke the <nowiki>{{</nowiki>[[Template:Main|Main]]<nowiki>}}</nowiki> template like so:<br />
<br />
<pre><br />
== Section title (or subsection, etc.) ==<br />
{{Main|Your_article}}<br />
</pre><br />
<br />
=== Linking ===<br />
When you link to a {{SITENAME}} page using the <nowiki>[[Some_page]]</nowiki> syntax the link will be displayed regardless of the page existence which gives the reader with editing rights the ability to create it. This is useful, however sometimes it is better to use a different type of linking, especially when a similar page exists in Wikipedia or any other wiki. Then there is simply no need to recreate it for {{SITENAME}}.<br />
<br />
Here is a concrete example. Suppose we want to let the reader know what DIY stands for. Instead of linking it to a {{SITENAME}} page we can link to Wikipedia using the following syntax:<br />
<pre>[[Wikipedia:do-it-yourself|DIY]]</pre><br />
Which gives the following output:<br />
[[Wikipedia:do-it-yourself|DIY]]<br />
<br />
=== Editing existing pages ===<br />
Only edit existing ''quality'' pages when:<br />
* You know what you are doing;<br />
* You've found a spelling or factual error that you know how to correct;<br />
* You can provide more useful information (i.e. expand an article).<br />
<br />
This is important because only registered wiki users are given editing rights. This means that an article will usually have few authors and sudden changes in an article may cause conflicts. So the best thing you can do in case you think that the article is either severly outdated or needs to be rewritten is to go to the article talk page first (accessible by clicking the page discussion tab) and sharing your thoughts with the rest of the users.<br />
<br />
'''Always preview pages first'''. Also remember to check ''This is a minor edit'' checkbox before saving a page when making only a minor edit.<br />
<br />
Be especially careful when editing templates. These are used on multiple pages and thus must be handled with care.<br />
<br />
=== Inserting images ===<br />
It is good practice to insert images with secondary illustrative purpose as thumbnails. The width of those thumbnails should not exceed 250 pixels. This takes into account the variety of display settings used to view the wiki pages and should work for everyone. Also, these thumbnails should be aligned right (this is the default setting).<br />
<br />
=== Inserting videos ===<br />
When to insert videos as links within a box notification:<br />
* When the content of an article can be replaced by viewing the video<br />
* When the video is accompanied by quality annotations and/or comments<br />
<br />
When to embed videos into pages:<br />
* When the videos are used as accompanying material<br />
<br />
The same rule applies for embedded videos as for inserting image thumbnails: use max 250 pixel widths and keep the aligned to the right of the page.<br />
<br />
=== Unfinished articles ===<br />
If you think that the article suffers from too little informative quality you can insert the template <nowiki>{{</nowiki>[[Template:Stub|Stub]]<nowiki>}}</nowiki> at the top (or bottom) of the page. Please use this sparingly.<br />
<br />
=== Writing translations ===<br />
The preferred language for this wiki is English. In order to write a translation make a subpage for your language for the main page. E.g. for a Russian translation of the [[MegaDrum]] page, make a [[MegaDrum/ru]] subpage. After the translation is complete, insert the language bar on the top of the parent and child pages by invoking the <nowiki>{{</nowiki>[[Template:Languages|Languages]]<nowiki>}}</nowiki> template like so:<br />
<br />
<pre>{{Languages}}</pre><br />
<br />
This will render the language bar:<br />
<br />
{{Languages}}<br />
<br />
=== Conclusion ===<br />
Keep in mind that these are only general guidelines and that there may be exceptions. Thank you for taking your time reading this. We are looking forward to your contributions.<br />
<br />
== Notes ==<br />
<references group="notes" /></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Help:Contents&diff=125Help:Contents2010-09-05T14:28:34Z<p>Firelord: /* Templates */</p>
<hr />
<div>'''Welcome to the {{SITENAME}} help section!''' This page currently contains:<br />
* General formatting documentation to help you get started writing articles;<br />
* Some guidelines on writing new/editing articles for {{SITENAME}}.<br />
<br />
'''Please read the following carefully especially if you haven't worked with MediaWiki based projects before.'''<br />
<br />
If you are looking for help with building/buying/troubleshooting MegaDrum, please refer to the [http://www.megadrum.info/ forums] for now.<br />
<br />
== MediaWiki markup ==<br />
<br />
=== Basic formatting ===<br />
The most important part of a MediaWiki article is meaningful plain text. However, formatting is required to deliver rich content. Basically, you enter text with special control characters/structures to get formatting effects. For example, to get '''bold''' text you would enter the following:<br />
<br />
<pre>'''This text is bold'''</pre><br />
<br />
This will render:<br />
<br />
'''This text is bold'''<br />
<br />
Please refer to the [http://www.mediawiki.org/wiki/Help:Formatting basic formatting documentation]. You can also learn the formatting rules from viewing the content of existing MediaWiki pages (e.g. [http://wikipedia.org/ Wikipedia] pages).<br />
<br />
=== Linking ===<br />
Linking to pages is explained in detail [http://www.mediawiki.org/wiki/Help:Links here]. Here is an example link to the MegaDrum article on {{SITENAME}} (this is an example of linking between {{SITENAME}} pages):<br />
<br />
<pre>[[MegaDrum]]</pre><br />
<br />
This will give the following output:<br />
<br />
[[MegaDrum]]<br />
<br />
Remember that it is bad practice to link every single word because this brings confusion to the reader.<br />
<br />
=== Article sections ===<br />
Dividing your article into sections is a good idea to separate different important parts of information from each other. To add a new section to the article use this code:<br />
<br />
<pre>==New section==</pre><br />
<br />
And if you need a subsection, type:<br />
<br />
<pre>===New section subsection===</pre><br />
<br />
More information can be obtained [http://meta.wikimedia.org/wiki/Help:Section here].<br />
<br />
If an article contains multiple sections, a table of contents will be automatically shown in the beginning of the page.<br />
<br />
=== Templates ===<br />
This is one of the most amazing features of MediaWiki. Templates are actually regular MediaWiki pages that can be inserted into other pages. However, parameters can be passed to templates that make them really flexible.<br />
<br />
To invoke an existing template you use the code<br />
<br />
<pre>{{Template_name}}</pre><br />
<br />
For example, here is the <nowiki>{{</nowiki>[[Template:LCD|LCD]]<nowiki>}}</nowiki> template without parameters. The code to invoke it is:<br />
<pre>{{LCD}}</pre><br />
<br />
This code will render:<br />
{{LCD}}<br />
<br />
And here is an example of the template with parameters:<br />
<pre>{{LCD|<br />
color=white|<br />
float=right|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2♦|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}</pre><br />
<br />
This renders the following: {{LCD|<br />
color=white|<br />
float=right|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2♦|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
<br />
Templates usually come with documentation on how to use them. If you are making a new template please take some time to document its features. Do this by adding a '''doc''' subpage to your template. More info on this [[Template:Documentation|here]].<br />
<br />
=== Adding images ===<br />
This is neatly documented [http://www.mediawiki.org/wiki/Help:Images here]. Everything else falls under the [[#Guidelines|guidelines]] part of this page.<br />
<br />
=== Adding videos ===<br />
Currently there is two ways for doing this. One is invoking the video template, for example:<br />
<pre>{{video|<br />
url=http://www.youtube.com/watch?v=-7u4USyw0gU|<br />
desc=How to remove the ATmega MCU from its socket}}</pre><br />
<br />
This renders:<br />
<br />
{{video|<br />
url=http://www.youtube.com/watch?v=-7u4USyw0gU|<br />
desc=How to remove the ATMega MCU from its socket}}<br />
<br />
Another way is to insert a video directly into the page using this syntax:<br />
<br />
<pre>{{#ev:youtube|-7u4USyw0gU|250|right|How to remove the ATmega MCU from its socket}}</pre><br />
{{#ev:youtube|-7u4USyw0gU|250|right|How to remove the ATmega MCU from its socket}}<br />
<br />
You should see the result of this on the right of the page: it may appear outside of the parent section. Please note, that <nowiki>{{#ev:...}}</nowiki> is '''not''' a template but a special extension.<br />
<br />
=== References ===<br />
References can be used as footnotes. Here is an example.<br />
<br />
<pre>Here is some information that has an associated note.<ref group="notes">This is the note.</ref></pre><br />
<br />
This will render:<br />
Here is some information that has an associated note.<ref group="notes">This is the note.</ref><br />
<br />
Notes are usually added to the bottom of the page by using something like<br />
<br />
<pre>== Notes ==<br />
<references group="notes" /></pre><br />
<br />
More about references [http://www.mediawiki.org/wiki/Extension:Cite/Cite.php here].<br />
<br />
=== wikEd ===<br />
This extension can come in handy for simplifying editing articles. It can be installed for example as a Greasemonkey script in Firefox. Read more about it [http://www.mediawiki.org/wiki/Extension:WikEd here].<br />
<br />
== Guidelines ==<br />
This section contains some basic guidelines to help you get started writing (editing) articles.<br />
<br />
=== Writing ===<br />
The main goal of writing wiki articles is to provide the reader with required information. Writing quality material is the second goal. When writing articles periodically check that:<br />
* You maintain a good informative level of expression and provide enough (but not too much) links to pages with explanatory material. In other words, the article should be understandable by both beginners and advanced users;<br />
* Your writing/editing results in a quality article render. You should use the preview button.<br />
<br />
If you can, check pages with multiple applied CSS styles in a variety of browsers to determine display errors. If any exist, first post a report to the discussion page. However, if you are completely certain you can easily fix this, please do so.<br />
<br />
=== When to link to a main article? ===<br />
When the topic in question is important and requires detailed explanation. Invoke the <nowiki>{{</nowiki>[[Template:Main|Main]]<nowiki>}}</nowiki> template like so:<br />
<br />
<pre><br />
== Section title (or subsection, etc.) ==<br />
{{Main|Your_article}}<br />
</pre><br />
<br />
=== Linking ===<br />
When you link to a {{SITENAME}} page using the <nowiki>[[Some_page]]</nowiki> syntax the link will be displayed regardless of the page existence which gives the reader with editing rights the ability to create it. This is useful, however sometimes it is better to use a different type of linking, especially when a similar page exists in Wikipedia or any other wiki. Then there is simply no need to recreate it for {{SITENAME}}.<br />
<br />
Here is a concrete example. Suppose we want to let the reader know what DIY stands for. Instead of linking it to a {{SITENAME}} page we can link to Wikipedia using the following syntax:<br />
<pre>[[Wikipedia:do-it-yourself|DIY]]</pre><br />
Which gives the following output:<br />
[[Wikipedia:do-it-yourself|DIY]]<br />
<br />
=== Editing existing pages ===<br />
Only edit existing ''quality'' pages when:<br />
* You know what you are doing;<br />
* You've found a spelling or factual error that you know how to correct;<br />
* You can provide more useful information (i.e. expand an article).<br />
<br />
This is important because only registered wiki users are given editing rights. This means that an article will usually have few authors and sudden changes in an article may cause conflicts (may be in the form of so-called 'editing wars'). So the best thing you can do in case you think that the article is either severly outdated or needs to be rewritten is to go to the article talk page first (accessible by clicking the page discussion tab) and sharing your thoughts with the rest of the users.<br />
<br />
'''Always preview pages first'''. Also remember to check ''This is a minor edit'' checkbox before saving a page when making only a minor edit.<br />
<br />
Be especially careful when editing templates. These are used on multiple pages and thus must be handled with care.<br />
<br />
=== Inserting images ===<br />
It is good practice to insert images with secondary illustrative purpose as thumbnails. The width of those thumbnails should not exceed 250 pixels. This takes into account the variety of display settings used to view the wiki pages and should work for everyone. Also, these thumbnails should be aligned right (this is the default setting).<br />
<br />
=== Inserting videos ===<br />
When to insert videos as links within a box notification:<br />
* When the content of an article can be replaced by viewing the video<br />
* When the video is accompanied by quality annotations and/or comments<br />
<br />
When to embed videos into pages:<br />
* When the videos are used as accompanying material<br />
<br />
The same rule applies for embedded videos as for inserting image thumbnails: use max 250 pixel widths and keep the aligned to the right of the page.<br />
<br />
=== Unfinished articles ===<br />
If you think that the article suffers from too little informative quality you can insert the template <nowiki>{{</nowiki>[[Template:Stub|Stub]]<nowiki>}}</nowiki> at the top (or bottom) of the page. Please use this sparingly.<br />
<br />
=== Writing translations ===<br />
The preferred language for this wiki is English. In order to write a translation make a subpage for your language for the main page. E.g. for a Russian translation of the [[MegaDrum]] page, make a [[MegaDrum/ru]] subpage. After the translation is complete, insert the language bar on the top of the parent and child pages by invoking the <nowiki>{{</nowiki>[[Template:Languages|Languages]]<nowiki>}}</nowiki> template like so:<br />
<br />
<pre>{{Languages}}</pre><br />
<br />
This will render the language bar:<br />
<br />
{{Languages}}<br />
<br />
=== Conclusion ===<br />
Keep in mind that these are only general guidelines and that there may be exceptions. Thank you for taking your time reading this. We are looking forward to your contributions.<br />
<br />
== Notes ==<br />
<references group="notes" /></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Help:Contents&diff=124Help:Contents2010-09-05T14:26:48Z<p>Firelord: /* Templates */</p>
<hr />
<div>'''Welcome to the {{SITENAME}} help section!''' This page currently contains:<br />
* General formatting documentation to help you get started writing articles;<br />
* Some guidelines on writing new/editing articles for {{SITENAME}}.<br />
<br />
'''Please read the following carefully especially if you haven't worked with MediaWiki based projects before.'''<br />
<br />
If you are looking for help with building/buying/troubleshooting MegaDrum, please refer to the [http://www.megadrum.info/ forums] for now.<br />
<br />
== MediaWiki markup ==<br />
<br />
=== Basic formatting ===<br />
The most important part of a MediaWiki article is meaningful plain text. However, formatting is required to deliver rich content. Basically, you enter text with special control characters/structures to get formatting effects. For example, to get '''bold''' text you would enter the following:<br />
<br />
<pre>'''This text is bold'''</pre><br />
<br />
This will render:<br />
<br />
'''This text is bold'''<br />
<br />
Please refer to the [http://www.mediawiki.org/wiki/Help:Formatting basic formatting documentation]. You can also learn the formatting rules from viewing the content of existing MediaWiki pages (e.g. [http://wikipedia.org/ Wikipedia] pages).<br />
<br />
=== Linking ===<br />
Linking to pages is explained in detail [http://www.mediawiki.org/wiki/Help:Links here]. Here is an example link to the MegaDrum article on {{SITENAME}} (this is an example of linking between {{SITENAME}} pages):<br />
<br />
<pre>[[MegaDrum]]</pre><br />
<br />
This will give the following output:<br />
<br />
[[MegaDrum]]<br />
<br />
Remember that it is bad practice to link every single word because this brings confusion to the reader.<br />
<br />
=== Article sections ===<br />
Dividing your article into sections is a good idea to separate different important parts of information from each other. To add a new section to the article use this code:<br />
<br />
<pre>==New section==</pre><br />
<br />
And if you need a subsection, type:<br />
<br />
<pre>===New section subsection===</pre><br />
<br />
More information can be obtained [http://meta.wikimedia.org/wiki/Help:Section here].<br />
<br />
If an article contains multiple sections, a table of contents will be automatically shown in the beginning of the page.<br />
<br />
=== Templates ===<br />
This is one of the most amazing features of MediaWiki. Templates are actually regular MediaWiki pages that can be inserted into other pages. However, parameters can be passed to templates that make them really flexible.<br />
<br />
To invoke an existing template you use the code<br />
<br />
<pre>{{Template_name}}</pre><br />
<br />
For example, here is the <nowiki>{{</nowiki>[[Template:LCD|LCD]]<nowiki>}}</nowiki> template without parameters. The code to invoke it is:<br />
<pre>{{LCD}}</pre><br />
<br />
This code will render:<br />
{{LCD}}<br />
<br />
And here is an example of the template with parameters:<br />
<pre>{{LCD|<br />
color=white|<br />
align=right|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2♦|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}</pre><br />
<br />
This renders the following:<br />
<br />
{{LCD|<br />
color=white|<br />
align=right|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2♦|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
<br />
Templates usually come with documentation on how to use them. If you are making a new template please take some time to document its features. Do this by adding a '''doc''' subpage to your template. More info on this [[Template:Documentation|here]].<br />
<br />
=== Adding images ===<br />
This is neatly documented [http://www.mediawiki.org/wiki/Help:Images here]. Everything else falls under the [[#Guidelines|guidelines]] part of this page.<br />
<br />
=== Adding videos ===<br />
Currently there is two ways for doing this. One is invoking the video template, for example:<br />
<pre>{{video|<br />
url=http://www.youtube.com/watch?v=-7u4USyw0gU|<br />
desc=How to remove the ATmega MCU from its socket}}</pre><br />
<br />
This renders:<br />
<br />
{{video|<br />
url=http://www.youtube.com/watch?v=-7u4USyw0gU|<br />
desc=How to remove the ATMega MCU from its socket}}<br />
<br />
Another way is to insert a video directly into the page using this syntax:<br />
<br />
<pre>{{#ev:youtube|-7u4USyw0gU|250|right|How to remove the ATmega MCU from its socket}}</pre><br />
{{#ev:youtube|-7u4USyw0gU|250|right|How to remove the ATmega MCU from its socket}}<br />
<br />
You should see the result of this on the right of the page: it may appear outside of the parent section. Please note, that <nowiki>{{#ev:...}}</nowiki> is '''not''' a template but a special extension.<br />
<br />
=== References ===<br />
References can be used as footnotes. Here is an example.<br />
<br />
<pre>Here is some information that has an associated note.<ref group="notes">This is the note.</ref></pre><br />
<br />
This will render:<br />
Here is some information that has an associated note.<ref group="notes">This is the note.</ref><br />
<br />
Notes are usually added to the bottom of the page by using something like<br />
<br />
<pre>== Notes ==<br />
<references group="notes" /></pre><br />
<br />
More about references [http://www.mediawiki.org/wiki/Extension:Cite/Cite.php here].<br />
<br />
=== wikEd ===<br />
This extension can come in handy for simplifying editing articles. It can be installed for example as a Greasemonkey script in Firefox. Read more about it [http://www.mediawiki.org/wiki/Extension:WikEd here].<br />
<br />
== Guidelines ==<br />
This section contains some basic guidelines to help you get started writing (editing) articles.<br />
<br />
=== Writing ===<br />
The main goal of writing wiki articles is to provide the reader with required information. Writing quality material is the second goal. When writing articles periodically check that:<br />
* You maintain a good informative level of expression and provide enough (but not too much) links to pages with explanatory material. In other words, the article should be understandable by both beginners and advanced users;<br />
* Your writing/editing results in a quality article render. You should use the preview button.<br />
<br />
If you can, check pages with multiple applied CSS styles in a variety of browsers to determine display errors. If any exist, first post a report to the discussion page. However, if you are completely certain you can easily fix this, please do so.<br />
<br />
=== When to link to a main article? ===<br />
When the topic in question is important and requires detailed explanation. Invoke the <nowiki>{{</nowiki>[[Template:Main|Main]]<nowiki>}}</nowiki> template like so:<br />
<br />
<pre><br />
== Section title (or subsection, etc.) ==<br />
{{Main|Your_article}}<br />
</pre><br />
<br />
=== Linking ===<br />
When you link to a {{SITENAME}} page using the <nowiki>[[Some_page]]</nowiki> syntax the link will be displayed regardless of the page existence which gives the reader with editing rights the ability to create it. This is useful, however sometimes it is better to use a different type of linking, especially when a similar page exists in Wikipedia or any other wiki. Then there is simply no need to recreate it for {{SITENAME}}.<br />
<br />
Here is a concrete example. Suppose we want to let the reader know what DIY stands for. Instead of linking it to a {{SITENAME}} page we can link to Wikipedia using the following syntax:<br />
<pre>[[Wikipedia:do-it-yourself|DIY]]</pre><br />
Which gives the following output:<br />
[[Wikipedia:do-it-yourself|DIY]]<br />
<br />
=== Editing existing pages ===<br />
Only edit existing ''quality'' pages when:<br />
* You know what you are doing;<br />
* You've found a spelling or factual error that you know how to correct;<br />
* You can provide more useful information (i.e. expand an article).<br />
<br />
This is important because only registered wiki users are given editing rights. This means that an article will usually have few authors and sudden changes in an article may cause conflicts (may be in the form of so-called 'editing wars'). So the best thing you can do in case you think that the article is either severly outdated or needs to be rewritten is to go to the article talk page first (accessible by clicking the page discussion tab) and sharing your thoughts with the rest of the users.<br />
<br />
'''Always preview pages first'''. Also remember to check ''This is a minor edit'' checkbox before saving a page when making only a minor edit.<br />
<br />
Be especially careful when editing templates. These are used on multiple pages and thus must be handled with care.<br />
<br />
=== Inserting images ===<br />
It is good practice to insert images with secondary illustrative purpose as thumbnails. The width of those thumbnails should not exceed 250 pixels. This takes into account the variety of display settings used to view the wiki pages and should work for everyone. Also, these thumbnails should be aligned right (this is the default setting).<br />
<br />
=== Inserting videos ===<br />
When to insert videos as links within a box notification:<br />
* When the content of an article can be replaced by viewing the video<br />
* When the video is accompanied by quality annotations and/or comments<br />
<br />
When to embed videos into pages:<br />
* When the videos are used as accompanying material<br />
<br />
The same rule applies for embedded videos as for inserting image thumbnails: use max 250 pixel widths and keep the aligned to the right of the page.<br />
<br />
=== Unfinished articles ===<br />
If you think that the article suffers from too little informative quality you can insert the template <nowiki>{{</nowiki>[[Template:Stub|Stub]]<nowiki>}}</nowiki> at the top (or bottom) of the page. Please use this sparingly.<br />
<br />
=== Writing translations ===<br />
The preferred language for this wiki is English. In order to write a translation make a subpage for your language for the main page. E.g. for a Russian translation of the [[MegaDrum]] page, make a [[MegaDrum/ru]] subpage. After the translation is complete, insert the language bar on the top of the parent and child pages by invoking the <nowiki>{{</nowiki>[[Template:Languages|Languages]]<nowiki>}}</nowiki> template like so:<br />
<br />
<pre>{{Languages}}</pre><br />
<br />
This will render the language bar:<br />
<br />
{{Languages}}<br />
<br />
=== Conclusion ===<br />
Keep in mind that these are only general guidelines and that there may be exceptions. Thank you for taking your time reading this. We are looking forward to your contributions.<br />
<br />
== Notes ==<br />
<references group="notes" /></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Help:Contents&diff=123Help:Contents2010-08-19T17:45:56Z<p>Firelord: /* Adding videos */</p>
<hr />
<div>'''Welcome to the {{SITENAME}} help section!''' This page currently contains:<br />
* General formatting documentation to help you get started writing articles;<br />
* Some guidelines on writing new/editing articles for {{SITENAME}}.<br />
<br />
'''Please read the following carefully especially if you haven't worked with MediaWiki based projects before.'''<br />
<br />
If you are looking for help with building/buying/troubleshooting MegaDrum, please refer to the [http://www.megadrum.info/ forums] for now.<br />
<br />
== MediaWiki markup ==<br />
<br />
=== Basic formatting ===<br />
The most important part of a MediaWiki article is meaningful plain text. However, formatting is required to deliver rich content. Basically, you enter text with special control characters/structures to get formatting effects. For example, to get '''bold''' text you would enter the following:<br />
<br />
<pre>'''This text is bold'''</pre><br />
<br />
This will render:<br />
<br />
'''This text is bold'''<br />
<br />
Please refer to the [http://www.mediawiki.org/wiki/Help:Formatting basic formatting documentation]. You can also learn the formatting rules from viewing the content of existing MediaWiki pages (e.g. [http://wikipedia.org/ Wikipedia] pages).<br />
<br />
=== Linking ===<br />
Linking to pages is explained in detail [http://www.mediawiki.org/wiki/Help:Links here]. Here is an example link to the MegaDrum article on {{SITENAME}} (this is an example of linking between {{SITENAME}} pages):<br />
<br />
<pre>[[MegaDrum]]</pre><br />
<br />
This will give the following output:<br />
<br />
[[MegaDrum]]<br />
<br />
Remember that it is bad practice to link every single word because this brings confusion to the reader.<br />
<br />
=== Article sections ===<br />
Dividing your article into sections is a good idea to separate different important parts of information from each other. To add a new section to the article use this code:<br />
<br />
<pre>==New section==</pre><br />
<br />
And if you need a subsection, type:<br />
<br />
<pre>===New section subsection===</pre><br />
<br />
More information can be obtained [http://meta.wikimedia.org/wiki/Help:Section here].<br />
<br />
If an article contains multiple sections, a table of contents will be automatically shown in the beginning of the page.<br />
<br />
=== Templates ===<br />
This is one of the most amazing features of MediaWiki. Templates are actually regular MediaWiki pages that can be inserted into other pages. However, parameters can be passed to templates that make them really flexible.<br />
<br />
To invoke an existing template you use the code<br />
<br />
<pre>{{Template_name}}</pre><br />
<br />
For example, here is the <nowiki>{{</nowiki>[[Template:LCD|LCD]]<nowiki>}}</nowiki> template without parameters. The code to invoke it is:<br />
<pre>{{LCD}}</pre><br />
<br />
This code will render:<br />
{{LCD}}<br />
<br />
And here is an example of the template with parameters:<br />
<pre>{{LCD|<br />
color=white|<br />
align=right|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2♦|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}</pre><br />
<br />
This renders the following:<br />
<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2♦|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
<br />
Templates usually come with documentation on how to use them. If you are making a new template please take some time to document its features. Do this by adding a '''doc''' subpage to your template. More info on this [[Template:Documentation|here]].<br />
<br />
=== Adding images ===<br />
This is neatly documented [http://www.mediawiki.org/wiki/Help:Images here]. Everything else falls under the [[#Guidelines|guidelines]] part of this page.<br />
<br />
=== Adding videos ===<br />
Currently there is two ways for doing this. One is invoking the video template, for example:<br />
<pre>{{video|<br />
url=http://www.youtube.com/watch?v=-7u4USyw0gU|<br />
desc=How to remove the ATmega MCU from its socket}}</pre><br />
<br />
This renders:<br />
<br />
{{video|<br />
url=http://www.youtube.com/watch?v=-7u4USyw0gU|<br />
desc=How to remove the ATMega MCU from its socket}}<br />
<br />
Another way is to insert a video directly into the page using this syntax:<br />
<br />
<pre>{{#ev:youtube|-7u4USyw0gU|250|right|How to remove the ATmega MCU from its socket}}</pre><br />
{{#ev:youtube|-7u4USyw0gU|250|right|How to remove the ATmega MCU from its socket}}<br />
<br />
You should see the result of this on the right of the page: it may appear outside of the parent section. Please note, that <nowiki>{{#ev:...}}</nowiki> is '''not''' a template but a special extension.<br />
<br />
=== References ===<br />
References can be used as footnotes. Here is an example.<br />
<br />
<pre>Here is some information that has an associated note.<ref group="notes">This is the note.</ref></pre><br />
<br />
This will render:<br />
Here is some information that has an associated note.<ref group="notes">This is the note.</ref><br />
<br />
Notes are usually added to the bottom of the page by using something like<br />
<br />
<pre>== Notes ==<br />
<references group="notes" /></pre><br />
<br />
More about references [http://www.mediawiki.org/wiki/Extension:Cite/Cite.php here].<br />
<br />
=== wikEd ===<br />
This extension can come in handy for simplifying editing articles. It can be installed for example as a Greasemonkey script in Firefox. Read more about it [http://www.mediawiki.org/wiki/Extension:WikEd here].<br />
<br />
== Guidelines ==<br />
This section contains some basic guidelines to help you get started writing (editing) articles.<br />
<br />
=== Writing ===<br />
The main goal of writing wiki articles is to provide the reader with required information. Writing quality material is the second goal. When writing articles periodically check that:<br />
* You maintain a good informative level of expression and provide enough (but not too much) links to pages with explanatory material. In other words, the article should be understandable by both beginners and advanced users;<br />
* Your writing/editing results in a quality article render. You should use the preview button.<br />
<br />
If you can, check pages with multiple applied CSS styles in a variety of browsers to determine display errors. If any exist, first post a report to the discussion page. However, if you are completely certain you can easily fix this, please do so.<br />
<br />
=== When to link to a main article? ===<br />
When the topic in question is important and requires detailed explanation. Invoke the <nowiki>{{</nowiki>[[Template:Main|Main]]<nowiki>}}</nowiki> template like so:<br />
<br />
<pre><br />
== Section title (or subsection, etc.) ==<br />
{{Main|Your_article}}<br />
</pre><br />
<br />
=== Linking ===<br />
When you link to a {{SITENAME}} page using the <nowiki>[[Some_page]]</nowiki> syntax the link will be displayed regardless of the page existence which gives the reader with editing rights the ability to create it. This is useful, however sometimes it is better to use a different type of linking, especially when a similar page exists in Wikipedia or any other wiki. Then there is simply no need to recreate it for {{SITENAME}}.<br />
<br />
Here is a concrete example. Suppose we want to let the reader know what DIY stands for. Instead of linking it to a {{SITENAME}} page we can link to Wikipedia using the following syntax:<br />
<pre>[[Wikipedia:do-it-yourself|DIY]]</pre><br />
Which gives the following output:<br />
[[Wikipedia:do-it-yourself|DIY]]<br />
<br />
=== Editing existing pages ===<br />
Only edit existing ''quality'' pages when:<br />
* You know what you are doing;<br />
* You've found a spelling or factual error that you know how to correct;<br />
* You can provide more useful information (i.e. expand an article).<br />
<br />
This is important because only registered wiki users are given editing rights. This means that an article will usually have few authors and sudden changes in an article may cause conflicts (may be in the form of so-called 'editing wars'). So the best thing you can do in case you think that the article is either severly outdated or needs to be rewritten is to go to the article talk page first (accessible by clicking the page discussion tab) and sharing your thoughts with the rest of the users.<br />
<br />
'''Always preview pages first'''. Also remember to check ''This is a minor edit'' checkbox before saving a page when making only a minor edit.<br />
<br />
Be especially careful when editing templates. These are used on multiple pages and thus must be handled with care.<br />
<br />
=== Inserting images ===<br />
It is good practice to insert images with secondary illustrative purpose as thumbnails. The width of those thumbnails should not exceed 250 pixels. This takes into account the variety of display settings used to view the wiki pages and should work for everyone. Also, these thumbnails should be aligned right (this is the default setting).<br />
<br />
=== Inserting videos ===<br />
When to insert videos as links within a box notification:<br />
* When the content of an article can be replaced by viewing the video<br />
* When the video is accompanied by quality annotations and/or comments<br />
<br />
When to embed videos into pages:<br />
* When the videos are used as accompanying material<br />
<br />
The same rule applies for embedded videos as for inserting image thumbnails: use max 250 pixel widths and keep the aligned to the right of the page.<br />
<br />
=== Unfinished articles ===<br />
If you think that the article suffers from too little informative quality you can insert the template <nowiki>{{</nowiki>[[Template:Stub|Stub]]<nowiki>}}</nowiki> at the top (or bottom) of the page. Please use this sparingly.<br />
<br />
=== Writing translations ===<br />
The preferred language for this wiki is English. In order to write a translation make a subpage for your language for the main page. E.g. for a Russian translation of the [[MegaDrum]] page, make a [[MegaDrum/ru]] subpage. After the translation is complete, insert the language bar on the top of the parent and child pages by invoking the <nowiki>{{</nowiki>[[Template:Languages|Languages]]<nowiki>}}</nowiki> template like so:<br />
<br />
<pre>{{Languages}}</pre><br />
<br />
This will render the language bar:<br />
<br />
{{Languages}}<br />
<br />
=== Conclusion ===<br />
Keep in mind that these are only general guidelines and that there may be exceptions. Thank you for taking your time reading this. We are looking forward to your contributions.<br />
<br />
== Notes ==<br />
<references group="notes" /></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Updating_MegaDrum_firmware&diff=122Updating MegaDrum firmware2010-08-16T20:23:42Z<p>Firelord: /* Troubleshooting */</p>
<hr />
<div>{{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.}}<br />
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].<br />
<br />
This tutorial describes the updating procedure in detail.<br />
<br />
== Prerequisites for updating ==<br />
* MegaDrum must be pre-programmed with the protected bootloader<br />
* You must have a working board with fully functional MegaDrum controls<br />
* Updating may be done via USB or MIDI I/O<br />
<br />
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).<br />
<br />
The [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1075 latest firmware version] is available for download from the forums.<br />
<br />
== Firmware file naming convention ==<br />
You should update with the right firmware for your MegaDrum version. All firmware files in the archive have the following naming scheme:<br />
<br />
* megadrum''ppp''_''hh''_''yyyymmdd''.bin — '''22''' inputs versions<br />
* megadrum''ppp''_''hh''_'''32'''_''yyyymmdd''.bin — '''32''' inputs versions<br />
* megadrum''ppp''_''hh''_'''48'''_''yyyymmdd''.bin — '''48''' inputs versions<br />
* megadrum''ppp''_''hh''_'''56'''_''yyyymmdd''.bin — '''56''' inputs versions<br />
<br />
where<br />
<br />
''ppp'' — AVR microcontroller type<br />
:32 — for Atmega32<br />
:324 — for Atmega324(p)<br />
:644 — for Atmega644<br />
''hh'' — crystal clock in MHz<br />
:Atmega32 versions with a clock above 16MHz are overclocked, Atmega324(p)/644 versions with a clock above 20MHz are overclocked<br />
''yyyymmdd'' — date (version) of the firmware.<br />
<br />
== Update software ==<br />
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.<br />
<br />
=== mdfwupdate ===<br />
{{video|<br />
url =http://www.youtube.com/watch?v=Y8M3KIRuPWQ|<br />
desc=Updating MegaDrum with mdfwupdate (with a GUI)}}<br />
<br />
==== General information ====<br />
* Platform support: Windows, Mac<br />
* Tested in: Windows XP<br />
* 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].<br />
* Source code: [http://www.megadrum.info/forums/viewtopic.php?p=15208#p15208 available] ''(C++)<br />
''<br />
==== Updating procedure ====<br />
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]<br />
<br />
2. Download the [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1075 firmware archive]<br />
<br />
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:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=FwSUpdater 16MHz|<br />
line2=DOWN-ok.UP-clock|<br />
caption=MegaDrum secure bootloader menu<br />
}}<br />
<br />
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<br />
<br />
5. In MegaDrum press the key DOWN. The LED will light up and MegaDrum display will show (e.g. for 16MHz):<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=FwSUpdater 16MHz|<br />
line2=StartUpdateOnPC{{nbsp|1}}|<br />
caption=MegaDrum secure bootloader in update mode<br />
}}<br />
<br />
6. Run the utility from the command line, e.g.:<br />
<pre><br />
mdfwupdate.exe megadrum644_20_32_20100601.bin<br />
</pre><br />
<br />
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:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=88886>ater 16MHz|<br />
line2=StartUpdateOnPC{{nbsp|1}}|<br />
caption=MegaDrum secure bootloader during the update<br />
}}<br />
<br />
8. When update has finished, the utility will show<br />
<pre><br />
Transferring.. 100% done.<br />
MegaDrum updated successfully.<br />
</pre><br />
<br />
MegaDrum will then reboot and start with new firmware and you will see the copyright screen:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
caption=Copyright screen<br />
}}<br />
<br />
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.<br />
<br />
=== MDUpdate ===<br />
{{video|<br />
url =http://www.youtube.com/watch?v=-N5YrSE4nxo|<br />
desc=Updating MegaDrum with MDUpdate test under Windows XP}}<br />
[[File:MDUpdate.png|250px|thumb|MDUpdate screenshot]]<br />
<br />
==== General information ====<br />
* Platform support: Windows, Linux (under [[wikipedia:Wine_(software)|Wine]])<br />
* Tested in: Windows XP, OpenSUSE 11.2<br />
* Type: GUI<br />
* 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)''<br />
<br />
==== Updating procedure ====<br />
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:<br />
<br />
1. Download [http://www.megadrum.info/forums/viewtopic.php?p=15245#p15245 MDUpdate]<br />
<br />
2. Download the [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1075 firmware files]<br />
<br />
3. Start MegaDrum in bootloader mode, select the correct frequency, switch to live update mode<br />
<br />
4. Run MDUpdate, select the correct firmware, MIDI I/O ports and press '''Run MegaDrum Update'''<br />
<br />
5. Wait for the firmware update to finish.<br />
<br />
=== Megadrum Config Tool ===<br />
{{Main|Megadrum Config Tool}}<br />
{{video|<br />
url =http://www.youtube.com/watch?v=5hjP4Kut5lQ|<br />
desc=Updating MegaDrum with MCT v1.84}}<br />
<br />
==== General Information ====<br />
* 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><br />
* Tested in: Windows XP<br />
* Type: GUI<br />
* Source code: [http://code.google.com/p/megadrumconfigtool/ available] ''(Java, [http://netbeans.org/ NetBeans] project)''<br />
<br />
==== Firmware updating procedure ====<br />
{{Note|[[MCT]] supports encrypted firmware updates since version 1.84.}}<br />
<br />
The basics of the updating procedure are given in the [[#mdfwupdate|mdfwupdate]] section of this tutorial.<br />
<br />
1. Download [http://www.megadrum.info/configtool/ Megadrum Config Tool v 1.84] via the installer.<br />
<br />
2. Download the [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1075 firmware files]<br />
<br />
3. Start MegaDrum in either normal mode or bootloader mode<br />
<br />
4. Start MCT, and set up the options:<br />
* MCU type and clock frequency<br />
* Bootloader type to v5<br />
* Correct MIDI I/O ports which correspond to MegaDrum<br />
<br />
5. In MCT menu go to <code>Firmware → UPDATE FIRMWARE</code><br />
<br />
6. Now close MCT and power off your MegaDrum<br />
<br />
7. Start MegaDrum with the LEFT key pressed (in bootloader mode), select the correct crystal frequency<br />
<br />
8. Open MCT, select the correct firmware file<br />
<br />
9. Press LEFT on MegaDrum to send a confirmation message to MCT, the <code>Proceed</code> button should be enabled<br />
<br />
10. Press DOWN on MegaDrum to enter live update mode<br />
<br />
11. Press <code>Proceed</code> button in MCT<br />
<br />
12. Wait for the update to finish, once it is finished restart MCT<br />
<br />
== Troubleshooting ==<br />
{{Main|Troubleshooting firmware updates}}<br />
If you cannot update your MegaDrum firmware, there could be several reasons:<br />
* You are trying to update via an unsecure bootloader<br />
* You are using wrong update software (e.g. MIDI-OX) with the protected bootloader<br />
* Your board has defects<br />
* MegaDrum controls are not functional<br />
* MIDI/USB communication fails for some reason<br />
* You have found a bug in the updating software. Please [http://www.megadrum.info/forums/ report it]!<br />
<br />
== See also ==<br />
* [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1252 Updating firmware with protected bootloader] forum discussion<br />
<br />
== Notes ==<br />
<references /><br />
<br />
[[Category:Tutorials]]</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Updating_MegaDrum_firmware&diff=121Updating MegaDrum firmware2010-08-16T20:23:07Z<p>Firelord: /* Megadrum Config Tool */</p>
<hr />
<div>{{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.}}<br />
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].<br />
<br />
This tutorial describes the updating procedure in detail.<br />
<br />
== Prerequisites for updating ==<br />
* MegaDrum must be pre-programmed with the protected bootloader<br />
* You must have a working board with fully functional MegaDrum controls<br />
* Updating may be done via USB or MIDI I/O<br />
<br />
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).<br />
<br />
The [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1075 latest firmware version] is available for download from the forums.<br />
<br />
== Firmware file naming convention ==<br />
You should update with the right firmware for your MegaDrum version. All firmware files in the archive have the following naming scheme:<br />
<br />
* megadrum''ppp''_''hh''_''yyyymmdd''.bin — '''22''' inputs versions<br />
* megadrum''ppp''_''hh''_'''32'''_''yyyymmdd''.bin — '''32''' inputs versions<br />
* megadrum''ppp''_''hh''_'''48'''_''yyyymmdd''.bin — '''48''' inputs versions<br />
* megadrum''ppp''_''hh''_'''56'''_''yyyymmdd''.bin — '''56''' inputs versions<br />
<br />
where<br />
<br />
''ppp'' — AVR microcontroller type<br />
:32 — for Atmega32<br />
:324 — for Atmega324(p)<br />
:644 — for Atmega644<br />
''hh'' — crystal clock in MHz<br />
:Atmega32 versions with a clock above 16MHz are overclocked, Atmega324(p)/644 versions with a clock above 20MHz are overclocked<br />
''yyyymmdd'' — date (version) of the firmware.<br />
<br />
== Update software ==<br />
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.<br />
<br />
=== mdfwupdate ===<br />
{{video|<br />
url =http://www.youtube.com/watch?v=Y8M3KIRuPWQ|<br />
desc=Updating MegaDrum with mdfwupdate (with a GUI)}}<br />
<br />
==== General information ====<br />
* Platform support: Windows, Mac<br />
* Tested in: Windows XP<br />
* 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].<br />
* Source code: [http://www.megadrum.info/forums/viewtopic.php?p=15208#p15208 available] ''(C++)<br />
''<br />
==== Updating procedure ====<br />
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]<br />
<br />
2. Download the [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1075 firmware archive]<br />
<br />
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:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=FwSUpdater 16MHz|<br />
line2=DOWN-ok.UP-clock|<br />
caption=MegaDrum secure bootloader menu<br />
}}<br />
<br />
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<br />
<br />
5. In MegaDrum press the key DOWN. The LED will light up and MegaDrum display will show (e.g. for 16MHz):<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=FwSUpdater 16MHz|<br />
line2=StartUpdateOnPC{{nbsp|1}}|<br />
caption=MegaDrum secure bootloader in update mode<br />
}}<br />
<br />
6. Run the utility from the command line, e.g.:<br />
<pre><br />
mdfwupdate.exe megadrum644_20_32_20100601.bin<br />
</pre><br />
<br />
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:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=88886>ater 16MHz|<br />
line2=StartUpdateOnPC{{nbsp|1}}|<br />
caption=MegaDrum secure bootloader during the update<br />
}}<br />
<br />
8. When update has finished, the utility will show<br />
<pre><br />
Transferring.. 100% done.<br />
MegaDrum updated successfully.<br />
</pre><br />
<br />
MegaDrum will then reboot and start with new firmware and you will see the copyright screen:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
caption=Copyright screen<br />
}}<br />
<br />
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.<br />
<br />
=== MDUpdate ===<br />
{{video|<br />
url =http://www.youtube.com/watch?v=-N5YrSE4nxo|<br />
desc=Updating MegaDrum with MDUpdate test under Windows XP}}<br />
[[File:MDUpdate.png|250px|thumb|MDUpdate screenshot]]<br />
<br />
==== General information ====<br />
* Platform support: Windows, Linux (under [[wikipedia:Wine_(software)|Wine]])<br />
* Tested in: Windows XP, OpenSUSE 11.2<br />
* Type: GUI<br />
* 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)''<br />
<br />
==== Updating procedure ====<br />
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:<br />
<br />
1. Download [http://www.megadrum.info/forums/viewtopic.php?p=15245#p15245 MDUpdate]<br />
<br />
2. Download the [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1075 firmware files]<br />
<br />
3. Start MegaDrum in bootloader mode, select the correct frequency, switch to live update mode<br />
<br />
4. Run MDUpdate, select the correct firmware, MIDI I/O ports and press '''Run MegaDrum Update'''<br />
<br />
5. Wait for the firmware update to finish.<br />
<br />
=== Megadrum Config Tool ===<br />
{{Main|Megadrum Config Tool}}<br />
{{video|<br />
url =http://www.youtube.com/watch?v=5hjP4Kut5lQ|<br />
desc=Updating MegaDrum with MCT v1.84}}<br />
<br />
==== General Information ====<br />
* 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><br />
* Tested in: Windows XP<br />
* Type: GUI<br />
* Source code: [http://code.google.com/p/megadrumconfigtool/ available] ''(Java, [http://netbeans.org/ NetBeans] project)''<br />
<br />
==== Firmware updating procedure ====<br />
{{Note|[[MCT]] supports encrypted firmware updates since version 1.84.}}<br />
<br />
The basics of the updating procedure are given in the [[#mdfwupdate|mdfwupdate]] section of this tutorial.<br />
<br />
1. Download [http://www.megadrum.info/configtool/ Megadrum Config Tool v 1.84] via the installer.<br />
<br />
2. Download the [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1075 firmware files]<br />
<br />
3. Start MegaDrum in either normal mode or bootloader mode<br />
<br />
4. Start MCT, and set up the options:<br />
* MCU type and clock frequency<br />
* Bootloader type to v5<br />
* Correct MIDI I/O ports which correspond to MegaDrum<br />
<br />
5. In MCT menu go to <code>Firmware → UPDATE FIRMWARE</code><br />
<br />
6. Now close MCT and power off your MegaDrum<br />
<br />
7. Start MegaDrum with the LEFT key pressed (in bootloader mode), select the correct crystal frequency<br />
<br />
8. Open MCT, select the correct firmware file<br />
<br />
9. Press LEFT on MegaDrum to send a confirmation message to MCT, the <code>Proceed</code> button should be enabled<br />
<br />
10. Press DOWN on MegaDrum to enter live update mode<br />
<br />
11. Press <code>Proceed</code> button in MCT<br />
<br />
12. Wait for the update to finish, once it is finished restart MCT<br />
<br />
== Troubleshooting ==<br />
{{Main|Troubleshooting the firmware update}}<br />
If you cannot update your MegaDrum firmware, there could be several reasons:<br />
* You are trying to update via an unsecure bootloader<br />
* You are using wrong update software (e.g. MIDI-OX) with the protected bootloader<br />
* Your board has defects<br />
* MegaDrum controls are not functional<br />
* MIDI/USB communication fails for some reason<br />
* You have found a bug in the updating software. Please [http://www.megadrum.info/forums/ report it]!<br />
<br />
== See also ==<br />
* [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1252 Updating firmware with protected bootloader] forum discussion<br />
<br />
== Notes ==<br />
<references /><br />
<br />
[[Category:Tutorials]]</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=MegaDrum&diff=111MegaDrum2010-08-02T16:07:23Z<p>Firelord: </p>
<hr />
<div>[[File:ExampleAssembledMegaDrum.jpg|250px|thumb|An assembled MegaDrum module]]'''MegaDrum''' is a feature-rich [[MIDI drum trigger]] module developed by [[Dmitri Skachkov]]. It was made public as a [[wikipedia:Do_it_yourself|do-it-yourself]] project in the Internet on August&nbsp;1st,&nbsp;2007. Since then it has gained recognition from various drummers all over the world, from amateurs and hobbyists to professional drummers. Because of constant firmware and hardware improvement, MegaDrum has acquired support for a wide variety of drumpads from different manufacturers.<br />
<br />
As a [[wikipedia:MIDI|MIDI]] drum trigger MegaDrum does not have any built-in sounds. Its main purpose is to convert signals from commercial and do-it-yourself [[wikipedia:Electronic_drum|electronic drum pads]] into MIDI messages which are then fed to a [[wikipedia:Drum_machine|drum machine]]/[[wikipedia:Sampler_(musical_instrument)|sampler]] or a PC.<br />
<br />
The openness of the project allowed for community contributions. Among notable ones are a hardware design upgrade (courtesy of [[Synthex]]) which added plug-and-play [[wikipedia:USB|USB]] support and a multiplatform Java application to control MegaDrum from a PC — [[Megadrum Config Tool]], written by [[Raúl Muñoz Benavente]]. The MegaDrum logo was made by forum member [http://www.megadrum.info/forums/memberlist.php?mode=viewprofile&u=97 duje07].<br />
<br />
Although MegaDrum is an open DIY-project, its firmware is not open-source. Commercial use (e.g. building a MegaDrum module and offering it for sale) requires Dmitri's explicit permission.<br />
<br />
== Features ==<br />
{{#ev:youtube|T8DWjfIUVbA|250|right|MegaDrum in action (courtesy of <a href="http://www.megadrum.info/forums/memberlist.php?mode=viewprofile&u=800">hchriste</a>)}}<br />
As a MIDI drum trigger MegaDrum offers the following features:<br />
<br />
<table cellpadding="0" cellspacing="0" border="0"><br />
<tr><br />
<td><br />
* 20/22/32/40/48/56 velocity-sensitive input channels;<br />
* 9 levels of input gain;<br />
* 10 different velocity curves and 4 custom adjustable curves;<br />
* Multilevel crosstalk suppression with 4 individual groups;<br />
* Threshold and retrigger settings;<br />
* Automatic high-level adjustment;<br />
* Velocity curves compression and shifting;<br />
* Positional sensing;<br />
* Support for simple switched and variable hi-hat controllers;<br />
</td><br />
<td style="padding-left: 20px;"><br />
* Support for for dual zone piezo-switch pads;<br />
* Support for 3 zone Roland style cymbals;<br />
* Support for 3 zone Yamaha style cymbals;<br />
* Firmware is software upgradable;<br />
* MIDI I/O with SysEx support;<br />
* USB powered with plug-n-play support and MIDI over USB;<br />
* Easy menu navigation and easy group settings adjustments;<br />
* 16x2 LCD with VU meters;<br />
* CC Choke support on every Dual Zone piezo/switch pad or 3 zone cymbals.<br />
</td><br />
</tr><br />
</table><br /><br />
<br />
As a do-it-yourself module:<br />
<br />
* Based on [[wikipedia:Atmel_AVR|ATmega]] microcontroller. Currently supported are ATmega 32/324P/644 running at 16, 20 and 24 MHz;<br />
* Uses widely available and mostly inexpensive components;<br />
* Potentiometer-free design;<br />
* ATmega/PIC chips can be programmed with simple programming cables/programmers.<ref>Initial programming of ATmega is now done by Dmitri, see [[#Legal_issues|why]].</ref><br />
<br />
== Building MegaDrum ==<br />
{{Main|Building MegaDrum}}<br />
You have the following options for building MegaDrum:<br />
* Build it yourself. Additionally you will have to order a chip from Dmitri;<br />
* Order a [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1139 Synthex kit] — using a kit greatly simplifies the assembly process;<br />
* [http://www.megadrum.info/content/i-can-build-it-you Ask Dmitri to build the module for you].<br />
<br />
Note that there are also other people who have Dmitri's permission to build and sell MegaDrum modules. See the [http://www.megadrum.info/forums/ forums] for more information.<br />
<br />
If you choose to build the module yourself you will need the following:<br />
* At least basic [[wikipedia:soldering|soldering]]/general [[wikipedia:electronics|electronics]] skills;<br />
* You have to know how to read a schematic;<br />
* You have to be able to tell one electronic part from another;<br />
* Tools are required to build MegaDrum, among them: a good soldering iron, pliers, wirecutters, a multimeter and so forth;<br />
* You need to know how to operate the aforementioned tools;<br />
* In case of making [[wikipedia:Printed_circuit_board|printed circuit boards]] at home using the toner transfer method you will need a good laser printer with quality toner, some photopaper and an etchant.<br />
<br />
It should be noted that MegaDrum is not a beginner's project and thus if you strongly feel that you're not up for the task of building it from scratch it is most likely so. Of course, if you're not afraid to learn and obtain the necessary DIY skills, you are probably capable of building MegaDrum. Otherwise, you might consider ordering a kit (it comes with quality PCB's) or simply buying the assembled module.<br />
<br />
== Updating MegaDrum firmware ==<br />
{{Main|Updating MegaDrum firmware}}<br />
Once you've built MegaDrum and received the ATmega chip from Dmitri it is time to program its firmware. This is done by means of a PC: MegaDrum can be updated either via USB or via MIDI I/O. There are several options for different platforms. See the [[Updating MegaDrum firmware|main article]] for details.<br />
<br />
== MegaDrum Configuration ==<br />
{{Main|MegaDrum Configuration}}<br />
<br />
== MegaDrum MIDI SySex support ==<br />
{{Main|MegaDrum MIDI SysEx support}}<br />
MegaDrum supports MIDI SySex messages. This allows to control/configure MegaDrum from a PC and load/store practically unlimited number of custom MegaDrum configs in addition to configs stored in built-in non-volatile memory. <br />
<br />
== Legal issues ==<br />
In spring 2010 [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1245 it was discovered] that a person was building and selling MegaDrum modules without Dmitri's consent. Unfortunately, it was not possible to convince the person to cease his activities. It was then decided to encrypt future firmware releases to prevent abusive commercial use. This is why since June 2010 all new firmware files are encrypted. Updating MegaDrum with encrypted firmware requires a special type of secure bootloader which can only be programmed into the ATmega chip by Dmitri. There are two choices for obtaining a programmed chip:<br />
* Send Dmitri a compatible ATmega for programming;<br />
* Order a new chip from Dmitri.<br />
<br />
See [[ordering ATmega]] for details.<br />
<br />
== See also ==<br />
* [http://www.megadrum.info/forums/viewtopic.php?f=3&t=502 What is MegaDrum about?] forum post<br />
<br />
== Notes ==<br />
<references /></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=MegaDrum&diff=110MegaDrum2010-08-02T16:06:35Z<p>Firelord: /* Updating MegaDrum firmware */</p>
<hr />
<div>[[File:ExampleAssembledMegaDrum.jpg|250px|thumb|An assembled MegaDrum module]]'''MegaDrum''' is a feature-rich [[MIDI drum trigger]] module developed by [[Dmitri Skachkov]]. It was made public as a [[wikipedia:Do_it_yourself|do-it-yourself]] project in the Internet on August&nbsp;1st,&nbsp;2007. Since then it has gained recognition from various drummers all over the world, from amateurs and hobbyists to professional drummers. Because of constant firmware and hardware improvement, MegaDrum has acquired support for a wide variety of drumpads from different manufacturers.<br />
<br />
As a [[wikipedia:MIDI|MIDI]] drum trigger MegaDrum does not have any built-in sounds. Its main purpose is to convert signals from commercial and do-it-yourself [[wikipedia:Electronic_drum|electronic drum pads]] into MIDI messages which are then fed to a [[wikipedia:Drum_machine|drum machine]]/[[wikipedia:Sampler_(musical_instrument)|sampler]] or a PC.<br />
<br />
The openness of the project allowed for community contributions. Among notable ones are a hardware design upgrade (courtesy of [[Synthex]]) which added plug-and-play [[wikipedia:USB|USB]] support and a multiplatform Java application to control MegaDrum from a PC — [[MegaDrum Config Tool]], written by [[Raúl Muñoz Benavente]]. The MegaDrum logo was made by forum member [http://www.megadrum.info/forums/memberlist.php?mode=viewprofile&u=97 duje07].<br />
<br />
Although MegaDrum is an open DIY-project, its firmware is not open-source. Commercial use (e.g. building a MegaDrum module and offering it for sale) requires Dmitri's explicit permission.<br />
<br />
== Features ==<br />
{{#ev:youtube|T8DWjfIUVbA|250|right|MegaDrum in action (courtesy of <a href="http://www.megadrum.info/forums/memberlist.php?mode=viewprofile&u=800">hchriste</a>)}}<br />
As a MIDI drum trigger MegaDrum offers the following features:<br />
<br />
<table cellpadding="0" cellspacing="0" border="0"><br />
<tr><br />
<td><br />
* 20/22/32/40/48/56 velocity-sensitive input channels;<br />
* 9 levels of input gain;<br />
* 10 different velocity curves and 4 custom adjustable curves;<br />
* Multilevel crosstalk suppression with 4 individual groups;<br />
* Threshold and retrigger settings;<br />
* Automatic high-level adjustment;<br />
* Velocity curves compression and shifting;<br />
* Positional sensing;<br />
* Support for simple switched and variable hi-hat controllers;<br />
</td><br />
<td style="padding-left: 20px;"><br />
* Support for for dual zone piezo-switch pads;<br />
* Support for 3 zone Roland style cymbals;<br />
* Support for 3 zone Yamaha style cymbals;<br />
* Firmware is software upgradable;<br />
* MIDI I/O with SysEx support;<br />
* USB powered with plug-n-play support and MIDI over USB;<br />
* Easy menu navigation and easy group settings adjustments;<br />
* 16x2 LCD with VU meters;<br />
* CC Choke support on every Dual Zone piezo/switch pad or 3 zone cymbals.<br />
</td><br />
</tr><br />
</table><br /><br />
<br />
As a do-it-yourself module:<br />
<br />
* Based on [[wikipedia:Atmel_AVR|ATmega]] microcontroller. Currently supported are ATmega 32/324P/644 running at 16, 20 and 24 MHz;<br />
* Uses widely available and mostly inexpensive components;<br />
* Potentiometer-free design;<br />
* ATmega/PIC chips can be programmed with simple programming cables/programmers.<ref>Initial programming of ATmega is now done by Dmitri, see [[#Legal_issues|why]].</ref><br />
<br />
== Building MegaDrum ==<br />
{{Main|Building MegaDrum}}<br />
You have the following options for building MegaDrum:<br />
* Build it yourself. Additionally you will have to order a chip from Dmitri;<br />
* Order a [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1139 Synthex kit] — using a kit greatly simplifies the assembly process;<br />
* [http://www.megadrum.info/content/i-can-build-it-you Ask Dmitri to build the module for you].<br />
<br />
Note that there are also other people who have Dmitri's permission to build and sell MegaDrum modules. See the [http://www.megadrum.info/forums/ forums] for more information.<br />
<br />
If you choose to build the module yourself you will need the following:<br />
* At least basic [[wikipedia:soldering|soldering]]/general [[wikipedia:electronics|electronics]] skills;<br />
* You have to know how to read a schematic;<br />
* You have to be able to tell one electronic part from another;<br />
* Tools are required to build MegaDrum, among them: a good soldering iron, pliers, wirecutters, a multimeter and so forth;<br />
* You need to know how to operate the aforementioned tools;<br />
* In case of making [[wikipedia:Printed_circuit_board|printed circuit boards]] at home using the toner transfer method you will need a good laser printer with quality toner, some photopaper and an etchant.<br />
<br />
It should be noted that MegaDrum is not a beginner's project and thus if you strongly feel that you're not up for the task of building it from scratch it is most likely so. Of course, if you're not afraid to learn and obtain the necessary DIY skills, you are probably capable of building MegaDrum. Otherwise, you might consider ordering a kit (it comes with quality PCB's) or simply buying the assembled module.<br />
<br />
== Updating MegaDrum firmware ==<br />
{{Main|Updating MegaDrum firmware}}<br />
Once you've built MegaDrum and received the ATmega chip from Dmitri it is time to program its firmware. This is done by means of a PC: MegaDrum can be updated either via USB or via MIDI I/O. There are several options for different platforms. See the [[Updating MegaDrum firmware|main article]] for details.<br />
<br />
== MegaDrum Configuration ==<br />
{{Main|MegaDrum Configuration}}<br />
<br />
== MegaDrum MIDI SySex support ==<br />
{{Main|MegaDrum MIDI SysEx support}}<br />
MegaDrum supports MIDI SySex messages. This allows to control/configure MegaDrum from a PC and load/store practically unlimited number of custom MegaDrum configs in addition to configs stored in built-in non-volatile memory. <br />
<br />
== Legal issues ==<br />
In spring 2010 [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1245 it was discovered] that a person was building and selling MegaDrum modules without Dmitri's consent. Unfortunately, it was not possible to convince the person to cease his activities. It was then decided to encrypt future firmware releases to prevent abusive commercial use. This is why since June 2010 all new firmware files are encrypted. Updating MegaDrum with encrypted firmware requires a special type of secure bootloader which can only be programmed into the ATmega chip by Dmitri. There are two choices for obtaining a programmed chip:<br />
* Send Dmitri a compatible ATmega for programming;<br />
* Order a new chip from Dmitri.<br />
<br />
See [[ordering ATmega]] for details.<br />
<br />
== See also ==<br />
* [http://www.megadrum.info/forums/viewtopic.php?f=3&t=502 What is MegaDrum about?] forum post<br />
<br />
== Notes ==<br />
<references /></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=File:MDUpdate.png&diff=109File:MDUpdate.png2010-08-02T13:49:45Z<p>Firelord: </p>
<hr />
<div></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Updating_MegaDrum_firmware&diff=108Updating MegaDrum firmware2010-08-02T13:49:28Z<p>Firelord: Created page with '{{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 …'</p>
<hr />
<div>{{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.}}<br />
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].<br />
<br />
This tutorial describes the updating procedure in detail.<br />
<br />
== Prerequisites for updating ==<br />
* MegaDrum must be pre-programmed with the protected bootloader<br />
* You must have a working board with fully functional MegaDrum controls<br />
* Updating may be done via USB or MIDI I/O<br />
<br />
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).<br />
<br />
The [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1075 latest firmware version] is available for download from the forums.<br />
<br />
== Firmware file naming convention ==<br />
You should update with the right firmware for your MegaDrum version. All firmware files in the archive have the following naming scheme:<br />
<br />
* megadrum''ppp''_''hh''_''yyyymmdd''.bin — '''22''' inputs versions<br />
* megadrum''ppp''_''hh''_'''32'''_''yyyymmdd''.bin — '''32''' inputs versions<br />
* megadrum''ppp''_''hh''_'''48'''_''yyyymmdd''.bin — '''48''' inputs versions<br />
* megadrum''ppp''_''hh''_'''56'''_''yyyymmdd''.bin — '''56''' inputs versions<br />
<br />
where<br />
<br />
''ppp'' — AVR microcontroller type<br />
:32 — for Atmega32<br />
:324 — for Atmega324(p)<br />
:644 — for Atmega644<br />
''hh'' — crystal clock in MHz<br />
:Atmega32 versions with a clock above 16MHz are overclocked, Atmega324(p)/644 versions with a clock above 20MHz are overclocked<br />
''yyyymmdd'' — date (version) of the firmware.<br />
<br />
== Update software ==<br />
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.<br />
<br />
=== mdfwupdate ===<br />
{{video|<br />
url =http://www.youtube.com/watch?v=Y8M3KIRuPWQ|<br />
desc=Updating MegaDrum with mdfwupdate (with a GUI)}}<br />
<br />
==== General information ====<br />
* Platform support: Windows, Mac<br />
* Tested in: Windows XP<br />
* 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].<br />
* Source code: [http://www.megadrum.info/forums/viewtopic.php?p=15208#p15208 available] ''(C++)<br />
''<br />
==== Updating procedure ====<br />
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]<br />
<br />
2. Download the [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1075 firmware archive]<br />
<br />
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:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=FwSUpdater 16MHz|<br />
line2=DOWN-ok.UP-clock|<br />
caption=MegaDrum secure bootloader menu<br />
}}<br />
<br />
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<br />
<br />
5. In MegaDrum press the key DOWN. The LED will light up and MegaDrum display will show (e.g. for 16MHz):<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=FwSUpdater 16MHz|<br />
line2=StartUpdateOnPC{{nbsp|1}}|<br />
caption=MegaDrum secure bootloader in update mode<br />
}}<br />
<br />
6. Run the utility from the command line, e.g.:<br />
<pre><br />
mdfwupdate.exe megadrum644_20_32_20100601.bin<br />
</pre><br />
<br />
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:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=88886>ater 16MHz|<br />
line2=StartUpdateOnPC{{nbsp|1}}|<br />
caption=MegaDrum secure bootloader during the update<br />
}}<br />
<br />
8. When update has finished, the utility will show<br />
<pre><br />
Transferring.. 100% done.<br />
MegaDrum updated successfully.<br />
</pre><br />
<br />
MegaDrum will then reboot and start with new firmware and you will see the copyright screen:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
caption=Copyright screen<br />
}}<br />
<br />
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.<br />
<br />
=== MDUpdate ===<br />
{{video|<br />
url =http://www.youtube.com/watch?v=-N5YrSE4nxo|<br />
desc=Updating MegaDrum with MDUpdate test under Windows XP}}<br />
[[File:MDUpdate.png|250px|thumb|MDUpdate screenshot]]<br />
<br />
==== General information ====<br />
* Platform support: Windows, Linux (under [[wikipedia:Wine_(software)|Wine]])<br />
* Tested in: Windows XP, OpenSUSE 11.2<br />
* Type: GUI<br />
* 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)''<br />
<br />
==== Updating procedure ====<br />
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:<br />
<br />
1. Download [http://www.megadrum.info/forums/viewtopic.php?p=15245#p15245 MDUpdate]<br />
<br />
2. Download the [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1075 firmware files]<br />
<br />
3. Start MegaDrum in bootloader mode, select the correct frequency, switch to live update mode<br />
<br />
4. Run MDUpdate, select the correct firmware, MIDI I/O ports and press '''Run MegaDrum Update'''<br />
<br />
5. Wait for the firmware update to finish.<br />
<br />
=== Megadrum Config Tool ===<br />
{{Main|Megadrum Config Tool}}<br />
{{video|<br />
url =http://www.youtube.com/watch?v=5hjP4Kut5lQ|<br />
desc=Updating MegaDrum with MCT v1.84b}}<br />
<br />
==== General Information ====<br />
* 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><br />
* Tested in: Windows XP<br />
* Type: GUI<br />
* Source code: [http://www.megadrum.info/forums/viewtopic.php?p=15738#p15738 available] ''(Java, [http://netbeans.org/ NetBeans] project)''<br />
<br />
==== Firmware updating procedure ====<br />
{{Note|[[MCT]] supports encrypted firmware updates in version 1.84b.}}<br />
<br />
The basics of the updating procedure are given in the [[#mdfwupdate|mdfwupdate]] section of this tutorial.<br />
<br />
1. Download [http://www.megadrum.info/forums/viewtopic.php?p=15733#p15733 Megadrum Config Tool v 1.84b] via the installer.<br />
<br />
2. Download the [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1075 firmware files]<br />
<br />
3. Start MegaDrum in either normal mode or bootloader mode<br />
<br />
4. Start MCT, and set up the options:<br />
* MCU type and clock frequency<br />
* Bootloader type to v5<br />
* Correct MIDI I/O ports which correspond to MegaDrum<br />
<br />
5. In MCT menu go to <code>Firmware → UPDATE FIRMWARE</code><br />
<br />
6. Now close MCT and power off your MegaDrum<br />
<br />
7. Start MegaDrum with the LEFT key pressed (in bootloader mode), select the correct crystal frequency<br />
<br />
8. Open MCT, select the correct firmware file<br />
<br />
9. Press LEFT on MegaDrum to send a confirmation message to MCT, the <code>Proceed</code> button should be enabled<br />
<br />
10. Press DOWN on MegaDrum to enter live update mode<br />
<br />
11. Press <code>Proceed</code> button in MCT<br />
<br />
12. Wait for the update to finish, once it is finished restart MCT<br />
<br />
== Troubleshooting ==<br />
{{Main|Troubleshooting the firmware update}}<br />
If you cannot update your MegaDrum firmware, there could be several reasons:<br />
* You are trying to update via an unsecure bootloader<br />
* You are using wrong update software (e.g. MIDI-OX) with the protected bootloader<br />
* Your board has defects<br />
* MegaDrum controls are not functional<br />
* MIDI/USB communication fails for some reason<br />
* You have found a bug in the updating software. Please [http://www.megadrum.info/forums/ report it]!<br />
<br />
== See also ==<br />
* [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1252 Updating firmware with protected bootloader] forum discussion<br />
<br />
== Notes ==<br />
<references /><br />
<br />
[[Category:Tutorials]]</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Template:Note&diff=107Template:Note2010-08-02T13:47:49Z<p>Firelord: Created page with '<div style="padding: 0.5em 0.5em 0.5em 2em; border: 0;">''<span style="color: red;">Note:</span> {{{1|Your note}}}''</div>'</p>
<hr />
<div><div style="padding: 0.5em 0.5em 0.5em 2em; border: 0;">''<span style="color: red;">Note:</span> {{{1|Your note}}}''</div></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Template:LCD&diff=106Template:LCD2010-08-02T13:37:14Z<p>Firelord: </p>
<hr />
<div><includeonly>{{#css:Template:LCD/style.css}}<div class="lcd-container" align="center" style="float: {{{float|none}}}; clear: {{{float|none}}};"><br />
<table class="lcd-table" align="center" summary="MegaDrum display" style="background: {{{bgcolor|#00FF00}}};"><br />
<tr><br />
<td class="lcd-row1 {{{contrast|}}}" style="color: {{{color|#000000}}};">{{{line1|&lt;MegaDrum.info&nbsp;&gt;}}}</td><br />
</tr><br />
<tr><br />
<td class="lcd-row2 {{{contrast|}}}" style="color: {{{color|#000000}}};">{{{line2|(c)D.Skachkov&nbsp;&nbsp;&nbsp;}}}</td><br />
</tr><br />
</table><br />
''{{{caption|MegaDrum display}}}''<br />
</div></includeonly><br />
<noinclude>{{documentation}}</noinclude></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Template:LCD/style.css&diff=105Template:LCD/style.css2010-08-02T13:36:49Z<p>Firelord: </p>
<hr />
<div>div.lcd-container<br />
{<br />
margin: 1em auto 1em auto;<br />
padding: 0.5em;<br />
border: 1px solid #B0B0B0;<br />
background: #F9F9F9;<br />
text-align: center;<br />
width: 400px;<br />
}<br />
<br />
table.lcd-table<br />
{<br />
border: 5px #000000 solid;<br />
text-align: center;<br />
width: 250px;<br />
}<br />
<br />
td.lcd-row1, td.lcd-row2<br />
{<br />
letter-spacing:3px;<br />
font-family: 'Courier New', Courier, monospace;<br />
font-weight: bold;<br />
font-size: 20px;<br />
text-align: left;<br />
}<br />
<br />
td.lcd-row1<br />
{<br />
padding: 10px 10px 2px 10px;<br />
}<br />
<br />
td.lcd-row2<br />
{<br />
padding: 2px 10px 10px 10px;<br />
}<br />
<br />
.poor-contrast<br />
{<br />
-ms-filter: "progid:DXImageTransform.Microsoft.Alpha(Opacity=25)";<br />
filter: alpha(opacity=25);<br />
-moz-opacity: 0.25;<br />
-khtml-opacity: 0.25;<br />
opacity: 0.25;<br />
}</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Main_Page&diff=104Main Page2010-08-01T20:54:46Z<p>Firelord: /* About MegaDrum */</p>
<hr />
<div>'''Welcome to the MegaDrum wiki!''' Here you will find the most current information about MegaDrum, as well as a wealth of guides, tutorials, troubleshooting tips and much more! Also, if you are willing to contribute to {{SITENAME}}, please ask Dmitri for an account on the [http://www.megadrum.info/forums/ forums] by means of a personal message. Also consider the [[Help:Contents|help section]] prior to writing new or editing existing articles. It contains basic markup information and general guidelines.<br />
== About MegaDrum ==<br />
{{Main|MegaDrum}}<br />
MegaDrum is a [[MIDI drum trigger]] module publically released as a [[wikipedia:do-it-yourself|do-it-yourself]] project by [[Dmitri Skachkov]]. It is used as an [[wikipedia:electronic_drum_module|electronic drum module]] without built-in sounds. It is cheap and relatively easy to build for an average DIY-enthusiast.</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Template:LCD/doc&diff=103Template:LCD/doc2010-07-28T21:47:24Z<p>Firelord: </p>
<hr />
<div>This template is used to illustrate various MegaDrum settings that a user can observe on the LCD screen. Here's how it works in a nutshell: you write the following code:<br />
<pre><br />
{{LCD|<br />
color=black|<br />
bgcolor=#00FF00|<br />
line1=&lt;MegaDrum.info &gt;|<br />
line2=(c)D.Skachkov{{nbsp|2}}{{LCD/arrows|black}}|<br />
caption=MegaDrum copyright screen and contrast adjust<br />
}}<br />
</pre><br />
<br />
And get this result:<br />
{{LCD|<br />
color=black|<br />
bgcolor=#00FF00|<br />
line1=&lt;MegaDrum.info&nbsp;&gt;|<br />
line2=(c)D.Skachkov{{nbsp|2}}{{LCD/arrows|black}}|<br />
caption=MegaDrum copyright screen and contrast adjust<br />
}}<br />
<br />
As you can see, there is 2 lines, 16 characters in each. This mimics the type of LCD currently used with MegaDrum.<br />
<br />
The format of the template is self-explanatory. Any parameter can be omitted. Defaults are: black characters on green background. The default text is the copyright screen and default caption is "MegaDrum display". Observe the main template to see how it looks.<br />
<br />
'''A note on text formatting: Please note that if a line contains more than a single whitespace character you will need to use the Nbsp template. For example, let's say you need 5 consecutive space characters in a string. You would write this as:'''<br />
<br />
<pre><br />
{{nbsp|5}}<br />
</pre><br />
<br />
Please consult the [[Template:Nbsp|documentation]] for more information.<br />
<br />
'''Also consider using &amp;lt; for the "&lt;" character and "&amp;gt;" for the "&gt;" character.'''<br />
<br />
Here's another example. Note that I used a different color/bgcolor here. You can also use standard RGB color representations such as &#35;00FF00.<br />
<pre><br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=█_______________|<br />
line2=________________|<br />
caption=MegaDrum VU Meter screen<br />
}}<br />
</pre><br />
<br />
Result:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=█_______________|<br />
line2=________________|<br />
caption=MegaDrum VU Meter screen<br />
}}<br />
<br />
Finally here is an example settings screen.<br />
<br />
<pre><br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=&amp;lt;CustomCurve1{{nbsp|2}}&amp;gt;|<br />
line2=P1:{{nbsp|11}}2{{LCD/arrows|white}}|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
</pre><br />
<br />
Note that to insert a up/down arrow symbol a special template is used. Here's the syntax:<br />
<pre>{{LCD/arrows|color}}</pre><br />
where color can be: ''black'', ''blue'', ''red'', ''magenta'', ''green'', ''cyan'', ''yellow'' and ''white''. Please use the same color as you do for the LCD font.<br />
<br />
The result is as follows:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2{{LCD/arrows|white}}|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
<br />
You can also float the LCD screen to left/right using an additional float parameter. For example, here is the previous example right-aligned:<br />
<pre><br />
{{LCD|<br />
color=white|<br />
float=right|<br />
bgcolor=blue|<br />
line1=&amp;lt;CustomCurve1{{nbsp|2}}&amp;gt;|<br />
line2=P1:{{nbsp|11}}2{{LCD/arrows|white}}|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
</pre><br />
<br />
{{LCD|<br />
color=white|<br />
float=right|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2{{LCD/arrows|white}}|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
You should see the container to the right of this text.<br />
<br />
To make an example of poor contrast of this screen, add one more parameter: contrast=poor-contrast. This makes the font barely visible. The full example is:<br />
<pre><br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
contrast=poor-contrast|<br />
line1=&amp;lt;CustomCurve1{{nbsp|2}}&amp;gt;|<br />
line2=P1:{{nbsp|11}}2{{LCD/arrows|white}}|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
</pre><br />
<br />
Here's how it will look like:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
contrast=poor-contrast|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2{{LCD/arrows|white}}|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Template:LCD/style.css&diff=102Template:LCD/style.css2010-07-28T21:46:46Z<p>Firelord: Created page with 'div.lcd-container { margin: 0.5em 0.5em 0.5em 0.5em; padding: 0.5em; border: 1px solid #B0B0B0; background: #F9F9F9; text-align: center; width: 400px; } …'</p>
<hr />
<div>div.lcd-container<br />
{<br />
margin: 0.5em 0.5em 0.5em 0.5em;<br />
padding: 0.5em;<br />
border: 1px solid #B0B0B0;<br />
background: #F9F9F9;<br />
text-align: center;<br />
width: 400px;<br />
}<br />
<br />
table.lcd-table<br />
{<br />
border: 5px #000000 solid;<br />
text-align: center;<br />
width: 250px;<br />
}<br />
<br />
td.lcd-row1, td.lcd-row2<br />
{<br />
letter-spacing:3px;<br />
font-family: 'Courier New', Courier, monospace;<br />
font-weight: bold;<br />
font-size: 20px;<br />
text-align: left;<br />
}<br />
<br />
td.lcd-row1<br />
{<br />
padding: 10px 10px 2px 10px;<br />
}<br />
<br />
td.lcd-row2<br />
{<br />
padding: 2px 10px 10px 10px;<br />
}<br />
<br />
.poor-contrast<br />
{<br />
-ms-filter: "progid:DXImageTransform.Microsoft.Alpha(Opacity=25)";<br />
filter: alpha(opacity=25);<br />
-moz-opacity: 0.25;<br />
-khtml-opacity: 0.25;<br />
opacity: 0.25;<br />
}</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Template:LCD&diff=101Template:LCD2010-07-28T21:46:01Z<p>Firelord: </p>
<hr />
<div><includeonly><br />
{{#css:Template:LCD/style.css}}<br />
<div class="lcd-container" align="center" style="float: {{{float|none}}}; clear: {{{float|none}}};"><br />
<table class="lcd-table" align="center" summary="MegaDrum display" style="background: {{{bgcolor|#00FF00}}};"><br />
<tr><br />
<td class="lcd-row1 {{{contrast|}}}" style="color: {{{color|#000000}}};">{{{line1|&lt;MegaDrum.info&nbsp;&gt;}}}</td><br />
</tr><br />
<tr><br />
<td class="lcd-row2 {{{contrast|}}}" style="color: {{{color|#000000}}};">{{{line2|(c)D.Skachkov&nbsp;&nbsp;&nbsp;}}}</td><br />
</tr><br />
</table><br />
''{{{caption|MegaDrum display}}}''<br />
</div></includeonly><br />
<noinclude>{{documentation}}</noinclude></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Template:LCD/doc&diff=100Template:LCD/doc2010-07-24T19:25:04Z<p>Firelord: </p>
<hr />
<div>This template is used to illustrate various MegaDrum settings that a user can observe on the LCD screen. Here's how it works in a nutshell: you write the following code:<br />
<pre><br />
{{LCD|<br />
color=black|<br />
bgcolor=#00FF00|<br />
line1=&lt;MegaDrum.info &gt;|<br />
line2=(c)D.Skachkov{{nbsp|2}}{{LCD/arrows|black}}|<br />
caption=MegaDrum copyright screen and contrast adjust<br />
}}<br />
</pre><br />
<br />
And get this result:<br />
{{LCD|<br />
color=black|<br />
bgcolor=#00FF00|<br />
line1=&lt;MegaDrum.info&nbsp;&gt;|<br />
line2=(c)D.Skachkov{{nbsp|2}}{{LCD/arrows|black}}|<br />
caption=MegaDrum copyright screen and contrast adjust<br />
}}<br />
<br />
As you can see, there is 2 lines, 16 characters in each. This mimics the type of LCD currently used with MegaDrum.<br />
<br />
The format of the template is self-explanatory. Any parameter can be omitted. Defaults are: black characters on green background. The default text is the copyright screen and default caption is "MegaDrum display". Observe the main template to see how it looks.<br />
<br />
'''A note on text formatting: Please note that if a line contains more than a single whitespace character you will need to use the Nbsp template. For example, let's say you need 5 consecutive space characters in a string. You would write this as:'''<br />
<br />
<pre><br />
{{nbsp|5}}<br />
</pre><br />
<br />
Please consult the [[Template:Nbsp|documentation]] for more information.<br />
<br />
'''Also consider using &amp;lt; for the "&lt;" character and "&amp;gt;" for the "&gt;" character.'''<br />
<br />
Here's another example. Note that I used a different color/bgcolor here. You can also use standard RGB color representations such as &#35;00FF00.<br />
<pre><br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=█_______________|<br />
line2=________________|<br />
caption=MegaDrum VU Meter screen<br />
}}<br />
</pre><br />
<br />
Result:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=█_______________|<br />
line2=________________|<br />
caption=MegaDrum VU Meter screen<br />
}}<br />
<br />
Finally here is an example settings screen.<br />
<br />
<pre><br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=&amp;lt;CustomCurve1{{nbsp|2}}&amp;gt;|<br />
line2=P1:{{nbsp|11}}2{{LCD/arrows|white}}|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
</pre><br />
<br />
Note that to insert a up/down arrow symbol a special template is used. Here's the syntax:<br />
<pre>{{LCD/arrows|color}}</pre><br />
where color can be: ''black'', ''blue'', ''red'', ''magenta'', ''green'', ''cyan'', ''yellow'' and ''white''. Please use the same color as you do for the LCD font.<br />
<br />
The result is as follows:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2{{LCD/arrows|white}}|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
<br />
You can also float the LCD screen to left/right using an additional float parameter. For example, here is the previous example right-aligned:<br />
<pre><br />
{{LCD|<br />
color=white|<br />
float=right|<br />
bgcolor=blue|<br />
line1=&amp;lt;CustomCurve1{{nbsp|2}}&amp;gt;|<br />
line2=P1:{{nbsp|11}}2{{LCD/arrows|white}}|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
</pre><br />
<br />
{{LCD|<br />
color=white|<br />
float=right|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2{{LCD/arrows|white}}|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
You should see the container to the right of this text.</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Template:LCD&diff=99Template:LCD2010-07-24T19:13:30Z<p>Firelord: </p>
<hr />
<div><includeonly><br />
{{#css:<br />
div.lcd-container<br />
{<br />
margin: 0.5em 0.5em 0.5em 0.5em;<br />
padding: 0.5em;<br />
border: 1px solid #B0B0B0;<br />
background: #F9F9F9;<br />
text-align: center;<br />
width: 400px;<br />
}<br />
<br />
table.lcd-table<br />
{<br />
border: 5px #000000 solid;<br />
text-align: center;<br />
width: 250px;<br />
}<br />
<br />
td.lcd-row1, td.lcd-row2<br />
{<br />
letter-spacing:3px;<br />
font-family: 'Courier New', Courier, monospace;<br />
font-weight: bold;<br />
font-size: 20px;<br />
text-align: left;<br />
}<br />
<br />
td.lcd-row1<br />
{<br />
padding: 10px 10px 2px 10px;<br />
}<br />
<br />
td.lcd-row2<br />
{<br />
padding: 2px 10px 10px 10px;<br />
}<br />
}}<br />
<div class="lcd-container" align="center" style="float: {{{float|none}}}; clear: {{{float|none}}};"><br />
<table class="lcd-table" align="center" summary="MegaDrum display" style="background: {{{bgcolor|#00FF00}}};"><br />
<tr><br />
<td class="lcd-row1" style="color: {{{color|#000000}}};">{{{line1|&lt;MegaDrum.info&nbsp;&gt;}}}</td><br />
</tr><br />
<tr><br />
<td class="lcd-row2" style="color: {{{color|#000000}}};">{{{line2|(c)D.Skachkov&nbsp;&nbsp;&nbsp;}}}</td><br />
</tr><br />
</table><br />
''{{{caption|MegaDrum display}}}''<br />
</div></includeonly><br />
<noinclude>{{documentation}}</noinclude></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Template:LCD/doc&diff=98Template:LCD/doc2010-07-24T19:11:46Z<p>Firelord: </p>
<hr />
<div>This template is used to illustrate various MegaDrum settings that a user can observe on the LCD screen. Here's how it works in a nutshell: you write the following code:<br />
<pre><br />
{{LCD|<br />
color=black|<br />
bgcolor=#00FF00|<br />
line1=&lt;MegaDrum.info &gt;|<br />
line2=(c)D.Skachkov{{nbsp|2}}{{LCD/arrows|black}}|<br />
caption=MegaDrum copyright screen and contrast adjust<br />
}}<br />
</pre><br />
<br />
And get this result:<br />
{{LCD|<br />
color=black|<br />
bgcolor=#00FF00|<br />
line1=&lt;MegaDrum.info&nbsp;&gt;|<br />
line2=(c)D.Skachkov{{nbsp|2}}{{LCD/arrows|black}}|<br />
caption=MegaDrum copyright screen and contrast adjust<br />
}}<br />
<br />
As you can see, there is 2 lines, 16 characters in each. This mimics the type of LCD currently used with MegaDrum.<br />
<br />
The format of the template is self-explanatory. Any parameter can be omitted. Defaults are: black characters on green background. The default text is the copyright screen and default caption is "MegaDrum display". Observe the main template to see how it looks.<br />
<br />
'''A note on text formatting: Please note that if a line contains more than a single whitespace character you will need to use the Nbsp template. For example, let's say you need 5 consecutive space characters in a string. You would write this as:'''<br />
<br />
<pre><br />
{{nbsp|5}}<br />
</pre><br />
<br />
Please consult the [[Template:Nbsp|documentation]] for more information.<br />
<br />
'''Also consider using &amp;lt; for the "&lt;" character and "&amp;gt;" for the "&gt;" character.'''<br />
<br />
Here's another example. Note that I used a different color/bgcolor here. You can also use standard RGB color representations such as &#35;00FF00.<br />
<pre><br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=█_______________|<br />
line2=________________|<br />
caption=MegaDrum VU Meter screen<br />
}}<br />
</pre><br />
<br />
Result:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=█_______________|<br />
line2=________________|<br />
caption=MegaDrum VU Meter screen<br />
}}<br />
<br />
Finally here is an example settings screen.<br />
<br />
<pre><br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=&amp;lt;CustomCurve1{{nbsp|2}}&amp;gt;|<br />
line2=P1:{{nbsp|11}}2{{LCD/arrows|white}}|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
</pre><br />
<br />
Note that to insert a up/down arrow symbol a special template is used. Here's the syntax:<br />
<pre>{{LCD/arrows|color}}</pre><br />
where color can be: ''black'', ''blue'', ''red'', ''magenta'', ''green'', ''cyan'', ''yellow'' and ''white''. Please use the same color as you do for the LCD font.<br />
<br />
The result is as follows:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2{{LCD/arrows|white}}|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Template:LCD/doc&diff=97Template:LCD/doc2010-07-24T19:11:03Z<p>Firelord: </p>
<hr />
<div>This template is used to illustrate various MegaDrum settings that a user can observe on the LCD screen. Here's how it works in a nutshell: you write the following code:<br />
<pre><br />
{{LCD|<br />
color=black|<br />
bgcolor=#00FF00|<br />
line1=&lt;MegaDrum.info &gt;|<br />
line2=(c)D.Skachkov{{nbsp|2}}{{LCD/arrows|black}}|<br />
caption=MegaDrum copyright screen and contrast adjust<br />
}}<br />
</pre><br />
<br />
And get this result:<br />
{{LCD|<br />
color=black|<br />
bgcolor=#00FF00|<br />
line1=&lt;MegaDrum.info&nbsp;&gt;|<br />
line2=(c)D.Skachkov{{nbsp|2}}{{LCD/arrows|black}}|<br />
caption=MegaDrum copyright screen and contrast adjust<br />
}}<br />
<br />
As you can see, there is 2 lines, 16 characters in each. This mimics the type of LCD currently used with MegaDrum.<br />
<br />
The format of the template is self-explanatory. Any parameter can be omitted. Defaults are: black characters on green background. The default text is the copyright screen and default caption is "MegaDrum display". Observe the main template to see how it looks.<br />
<br />
'''A note on text formatting: Please note that if a line contains more than a single whitespace character you will need to use the Nbsp template. For example, let's say you need 5 consecutive space characters in a string. You would write this as:'''<br />
<br />
<pre><br />
{{nbsp|5}}<br />
</pre><br />
<br />
Please consult the [[Template:Nbsp|documentation]] for more information.<br />
<br />
'''Also consider using &amp;lt; for the "&lt;" character and "&amp;gt;" for the "&gt;" character.'''<br />
<br />
Here's another example. Note that I used a different color/bgcolor here. You can also use standard RGB color representations such as &#35;00FF00.<br />
<pre><br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=█_______________|<br />
line2=________________|<br />
caption=MegaDrum VU Meter screen<br />
}}<br />
</pre><br />
<br />
Result:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=█_______________|<br />
line2=________________|<br />
caption=MegaDrum VU Meter screen<br />
}}<br />
<br />
Finally here is an example settings screen.<br />
<br />
<pre><br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=&amp;lt;CustomCurve1{{nbsp|2}}&amp;gt;|<br />
line2=P1:{{nbsp|11}}2{{LCD/arrows|white}}|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
</pre><br />
<br />
Note that to insert a up/down arrow symbol a special template is used. Here's the syntax:<br />
<pre>{{LCD/arrows|color}}</pre><br />
where color can be: ''black'', ''blue'', ''red'', ''magenta'', ''green'', ''cyan'', ''yellow'' and ''white''. Please use the same color as you do for the LCD font.<br />
<br />
The result is as follows:<br />
<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2{{LCD/arrows|white}}|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Template:LCD&diff=96Template:LCD2010-07-24T18:56:00Z<p>Firelord: </p>
<hr />
<div><includeonly><br />
{{#css:<br />
div.lcd-container<br />
{<br />
margin: 0.5em 0.5em 0.5em 0.5em;<br />
padding: 0.5em;<br />
border: 1px solid #B0B0B0;<br />
background: #F9F9F9;<br />
text-align: center;<br />
width: 400px;<br />
}<br />
<br />
table.lcd-table<br />
{<br />
border: 5px #000000 solid;<br />
text-align: center;<br />
width: 250px;<br />
}<br />
<br />
td.lcd-row1, td.lcd-row2<br />
{<br />
letter-spacing:3px;<br />
font-family: 'Courier New', Courier, monospace;<br />
font-weight: bold;<br />
font-size: 20px;<br />
text-align: left;<br />
}<br />
<br />
td.lcd-row1<br />
{<br />
padding: 10px 10px 2px 10px;<br />
}<br />
<br />
td.lcd-row2<br />
{<br />
padding: 2px 10px 10px 10px;<br />
}<br />
}}<br />
<div class="lcd-container" align="center" style="float: {{{align|none}}};"><br />
<table class="lcd-table" align="center" summary="MegaDrum display" style="background: {{{bgcolor|#00FF00}}};"><br />
<tr><br />
<td class="lcd-row1" style="color: {{{color|#000000}}};">{{{line1|&lt;MegaDrum.info&nbsp;&gt;}}}</td><br />
</tr><br />
<tr><br />
<td class="lcd-row2" style="color: {{{color|#000000}}};">{{{line2|(c)D.Skachkov&nbsp;&nbsp;&nbsp;}}}</td><br />
</tr><br />
</table><br />
''{{{caption|MegaDrum display}}}''<br />
</div></includeonly><br />
<noinclude>{{documentation}}</noinclude></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Template:LCD/doc&diff=95Template:LCD/doc2010-07-24T18:53:20Z<p>Firelord: </p>
<hr />
<div>This template is used to illustrate various MegaDrum settings that a user can observe on the LCD screen. Here's how it works in a nutshell: you write the following code:<br />
<pre><br />
{{LCD|<br />
color=black|<br />
bgcolor=#00FF00|<br />
line1=&lt;MegaDrum.info &gt;|<br />
line2=(c)D.Skachkov{{nbsp|2}}{{LCD/arrows|black}}|<br />
caption=MegaDrum copyright screen and contrast adjust<br />
}}<br />
</pre><br />
<br />
And get this result:<br />
{{LCD|<br />
color=black|<br />
bgcolor=#00FF00|<br />
line1=&lt;MegaDrum.info&nbsp;&gt;|<br />
line2=(c)D.Skachkov{{nbsp|2}}{{LCD/arrows|black}}|<br />
caption=MegaDrum copyright screen and contrast adjust<br />
}}<br />
<br />
As you can see, there is 2 lines, 16 characters in each. This mimics the type of LCD currently used with MegaDrum.<br />
<br />
The format of the template is self-explanatory. Any parameter can be omitted. Defaults are: black characters on green background. The default text is the copyright screen and default caption is "MegaDrum display". Observe the main template to see how it looks.<br />
<br />
'''A note on text formatting: Please note that if a line contains more than a single whitespace character you will need to use the Nbsp template. For example, let's say you need 5 consecutive space characters in a string. You would write this as:'''<br />
<br />
<pre><br />
{{nbsp|5}}<br />
</pre><br />
<br />
Please consult the [[Template:Nbsp|documentation]] for more information.<br />
<br />
'''Also consider using &amp;lt; for the "&lt;" character and "&amp;gt;" for the "&gt;" character.'''<br />
<br />
Here's another example. Note that I used a different color/bgcolor here. You can also use standard RGB color representations such as &#35;00FF00.<br />
<pre><br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=█_______________|<br />
line2=________________|<br />
caption=MegaDrum VU Meter screen<br />
}}<br />
</pre><br />
<br />
Result:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=█_______________|<br />
line2=________________|<br />
caption=MegaDrum VU Meter screen<br />
}}<br />
<br />
Finally here is an example settings screen:<br />
<pre><br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=&amp;lt;CustomCurve1{{nbsp|2}}&amp;gt;|<br />
line2=P1:{{nbsp|11}}2{{LCD/arrows|white}}|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
</pre><br />
<br />
The result is as follows:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2{{LCD/arrows|white}}|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=File:ArrowsUpDown_white.gif&diff=94File:ArrowsUpDown white.gif2010-07-24T18:52:15Z<p>Firelord: </p>
<hr />
<div></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=File:ArrowsUpDown_yellow.gif&diff=93File:ArrowsUpDown yellow.gif2010-07-24T18:51:55Z<p>Firelord: </p>
<hr />
<div></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=File:ArrowsUpDown_cyan.gif&diff=92File:ArrowsUpDown cyan.gif2010-07-24T18:51:37Z<p>Firelord: </p>
<hr />
<div></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=File:ArrowsUpDown_green.gif&diff=91File:ArrowsUpDown green.gif2010-07-24T18:51:18Z<p>Firelord: </p>
<hr />
<div></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=File:ArrowsUpDown_magenta.gif&diff=90File:ArrowsUpDown magenta.gif2010-07-24T18:50:58Z<p>Firelord: </p>
<hr />
<div></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=File:ArrowsUpDown_red.gif&diff=89File:ArrowsUpDown red.gif2010-07-24T18:50:23Z<p>Firelord: </p>
<hr />
<div></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=File:ArrowsUpDown_blue.gif&diff=88File:ArrowsUpDown blue.gif2010-07-24T18:49:52Z<p>Firelord: </p>
<hr />
<div></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=File:ArrowsUpDown_black.gif&diff=87File:ArrowsUpDown black.gif2010-07-24T18:48:45Z<p>Firelord: uploaded a new version of "File:ArrowsUpDown black.gif"</p>
<hr />
<div>Template:LCD image</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Template:LCD/arrows/doc&diff=86Template:LCD/arrows/doc2010-07-24T18:47:55Z<p>Firelord: Created page with 'This is to be inserted into the LCD template to add the up/down arrows symbol (this symbol is displayed in the MegaDrum menu). Here is how it works: <pre>{{LCD/arrows}}</pre> Thi…'</p>
<hr />
<div>This is to be inserted into the LCD template to add the up/down arrows symbol (this symbol is displayed in the MegaDrum menu). Here is how it works:<br />
<pre>{{LCD/arrows}}</pre><br />
This will insert a black up/down arrows symbol by default: {{LCD/arrows}}. All standard colors are provided. Make sure you insert the symbol with the right color (i.e. it should be the same color as the LCD font). Here are all of the arrows:<br />
<br />
<nowiki>{{LCD/arrows|black}}</nowiki> : {{LCD/arrows|black}}<br />
<br />
<nowiki>{{LCD/arrows|blue}}</nowiki> : {{LCD/arrows|blue}}<br />
<br />
<nowiki>{{LCD/arrows|red}}</nowiki> : {{LCD/arrows|red}}<br />
<br />
<nowiki>{{LCD/arrows|magenta}}</nowiki> : {{LCD/arrows|magenta}}<br />
<br />
<nowiki>{{LCD/arrows|green}}</nowiki> : {{LCD/arrows|green}}<br />
<br />
<nowiki>{{LCD/arrows|cyan}}</nowiki> : {{LCD/arrows|cyan}}<br />
<br />
<span style="background: black; color: white;"><nowiki>{{LCD/arrows|yellow}}</nowiki> : {{LCD/arrows|yellow}}</span><br />
<br />
<span style="background: black; color: white;"><nowiki>{{LCD/arrows|white}}</nowiki> : {{LCD/arrows|white}}</span></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Template:LCD/arrows&diff=85Template:LCD/arrows2010-07-24T18:47:34Z<p>Firelord: Created page with 'link=<noinclude>{{documentation}}</noinclude>'</p>
<hr />
<div>[[File:ArrowsUpDown_{{{1|black}}}.gif|middle|link=]]<noinclude>{{documentation}}</noinclude></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=File:ArrowsUpDown_black.gif&diff=84File:ArrowsUpDown black.gif2010-07-24T17:55:49Z<p>Firelord: uploaded a new version of "File:ArrowsUpDown black.gif"</p>
<hr />
<div>Template:LCD image</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=File:ArrowsUpDown_black.gif&diff=83File:ArrowsUpDown black.gif2010-07-24T17:46:20Z<p>Firelord: Template:LCD image</p>
<hr />
<div>Template:LCD image</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=MIDI_drum_trigger&diff=82MIDI drum trigger2010-07-23T14:06:10Z<p>Firelord: </p>
<hr />
<div>'''MIDI drum trigger''' refers to an [[wikipedia:Electronic_drum_module|electronic drum module]] without built-in sounds. The module is only used to convert signals from electronic drum pads into [[wikipedia:MIDI|MIDI]] messages which are then used to trigger sounds on MIDI capable devices such as drum machines, samplers etc. Also known by the acronym 'TMI' (Trigger MIDI Interface).<br />
<br />
Examples of MIDI drum triggers include:<br />
* [[MegaDrum]]<br />
* [http://www.edrum.info/ eDrum] which gave an initial inspiration for the MegaDrum project <br />
* [[Alesis Trigger IO]]<br />
among others.<br />
<br />
There exists a multitude of PC based drum sampler applications (usually running as [[VST]] instruments) which can be effectively used with a MIDI drum trigger module. Examples of commercial samplers:<br />
* [[Addictive drums]]<br />
* [[BFD]]<br />
* [[EZDrummer]]<br />
* [[SuperiorDrummer]]</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Talk:Main_Page&diff=81Talk:Main Page2010-07-23T14:03:22Z<p>Firelord: </p>
<hr />
<div>I think that the main page should look something like this (for easy navigation): http://wiki.wxwidgets.org/Main_Page although the welcome text should remain. The table navigation could be implemented as a new section. [[User:Firelord|Firelord]] 20:26, 16 July 2010 (UTC)<br />
<br />
----<br />
<br />
Looks good, I would propose some specific categories as follows:<br />
* '''General Information''' (history of the project, legals etc)<br />
* '''MegaDrum hardware''' (the circuit, PCB, construction notes etc) <br />
* '''MegaDrum firmware''' (The existing doco / notes on how to update the firmware etc... anything about using the MegaDrum itself)<br />
* '''MegaDrum specific software''' (MCT and anything like it)<br />
* '''Related software''' (software to use with MegaDrum; Midi software, drum specific samplers, generic sampler software etc, how to setup megadrum for them, how they should be setup for MegaDrum etc)<br />
* '''Related Hardware''' (hardware to use with MegaDrum; notes on A2E conversion, DIY triggers, HH controllers etc, commercial hardware and how to use it with MegaDrum<br />
* '''Misc''' <br />
--[[User:Dm9876|Dm9876]] 23:01, 22 July 2010 (UTC)<br />
: I believe that more general categories would serve the reader better. E.g.: '''Tutorials''', '''Configuration''', '''Software''', '''Hardware''', '''Troubleshooting''', '''FAQs''' etc. First we need to create the content though :-) after adding a good wealth of articles it will be easier to create the main page [[User:Firelord|Firelord]] 14:03, 23 July 2010 (UTC)</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Help:Contents&diff=77Help:Contents2010-07-22T15:55:52Z<p>Firelord: /* Guidelines */</p>
<hr />
<div>'''Welcome to the {{SITENAME}} help section!''' This page currently contains:<br />
* General formatting documentation to help you get started writing articles;<br />
* Some guidelines on writing new/editing articles for {{SITENAME}}.<br />
<br />
'''Please read the following carefully especially if you haven't worked with MediaWiki based projects before.'''<br />
<br />
If you are looking for help with building/buying/troubleshooting MegaDrum, please refer to the [http://www.megadrum.info/ forums] for now.<br />
<br />
== MediaWiki markup ==<br />
<br />
=== Basic formatting ===<br />
The most important part of a MediaWiki article is meaningful plain text. However, formatting is required to deliver rich content. Basically, you enter text with special control characters/structures to get formatting effects. For example, to get '''bold''' text you would enter the following:<br />
<br />
<pre>'''This text is bold'''</pre><br />
<br />
This will render:<br />
<br />
'''This text is bold'''<br />
<br />
Please refer to the [http://www.mediawiki.org/wiki/Help:Formatting basic formatting documentation]. You can also learn the formatting rules from viewing the content of existing MediaWiki pages (e.g. [http://wikipedia.org/ Wikipedia] pages).<br />
<br />
=== Linking ===<br />
Linking to pages is explained in detail [http://www.mediawiki.org/wiki/Help:Links here]. Here is an example link to the MegaDrum article on {{SITENAME}} (this is an example of linking between {{SITENAME}} pages):<br />
<br />
<pre>[[MegaDrum]]</pre><br />
<br />
This will give the following output:<br />
<br />
[[MegaDrum]]<br />
<br />
Remember that it is bad practice to link every single word because this brings confusion to the reader.<br />
<br />
=== Article sections ===<br />
Dividing your article into sections is a good idea to separate different important parts of information from each other. To add a new section to the article use this code:<br />
<br />
<pre>==New section==</pre><br />
<br />
And if you need a subsection, type:<br />
<br />
<pre>===New section subsection===</pre><br />
<br />
More information can be obtained [http://meta.wikimedia.org/wiki/Help:Section here].<br />
<br />
If an article contains multiple sections, a table of contents will be automatically shown in the beginning of the page.<br />
<br />
=== Templates ===<br />
This is one of the most amazing features of MediaWiki. Templates are actually regular MediaWiki pages that can be inserted into other pages. However, parameters can be passed to templates that make them really flexible.<br />
<br />
To invoke an existing template you use the code<br />
<br />
<pre>{{Template_name}}</pre><br />
<br />
For example, here is the <nowiki>{{</nowiki>[[Template:LCD|LCD]]<nowiki>}}</nowiki> template without parameters. The code to invoke it is:<br />
<pre>{{LCD}}</pre><br />
<br />
This code will render:<br />
{{LCD}}<br />
<br />
And here is an example of the template with parameters:<br />
<pre>{{LCD|<br />
color=white|<br />
align=right|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2♦|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}</pre><br />
<br />
This renders the following:<br />
<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2♦|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
<br />
Templates usually come with documentation on how to use them. If you are making a new template please take some time to document its features. Do this by adding a '''doc''' subpage to your template. More info on this [[Template:Documentation|here]].<br />
<br />
=== Adding images ===<br />
This is neatly documented [http://www.mediawiki.org/wiki/Help:Images here]. Everything else falls under the [[#Guidelines|guidelines]] part of this page.<br />
<br />
=== Adding videos ===<br />
Currently there is two ways for doing this. One is invoking the video template, for example:<br />
<pre>{{video|<br />
url=http://www.youtube.com/watch?v=-7u4USyw0gU|<br />
desc=How to remove the ATmega MCU from its socket}}</pre><br />
<br />
This renders:<br />
<br />
{{video|<br />
url=http://www.youtube.com/watch?v=-7u4USyw0gU|<br />
desc=How to remove the ATMega MCU from its socket}}<br />
<br />
Another way is to insert a video directly into the page using this syntax:<br />
<br />
<pre>{{#ev:youtube|-7u4USyw0gU|250|right|How to remover the ATmega MCU from its socket}}</pre><br />
{{#ev:youtube|-7u4USyw0gU|250|right|How to remover the ATmega MCU from its socket}}<br />
<br />
You should see the result of this on the right of the page: it may appear outside of the parent section. Please note, that <nowiki>{{#ev:...}}</nowiki> is '''not''' a template but a special extension.<br />
<br />
=== References ===<br />
References can be used as footnotes. Here is an example.<br />
<br />
<pre>Here is some information that has an associated note.<ref group="notes">This is the note.</ref></pre><br />
<br />
This will render:<br />
Here is some information that has an associated note.<ref group="notes">This is the note.</ref><br />
<br />
Notes are usually added to the bottom of the page by using something like<br />
<br />
<pre>== Notes ==<br />
<references group="notes" /></pre><br />
<br />
More about references [http://www.mediawiki.org/wiki/Extension:Cite/Cite.php here].<br />
<br />
=== wikEd ===<br />
This extension can come in handy for simplifying editing articles. It can be installed for example as a Greasemonkey script in Firefox. Read more about it [http://www.mediawiki.org/wiki/Extension:WikEd here].<br />
<br />
== Guidelines ==<br />
This section contains some basic guidelines to help you get started writing (editing) articles.<br />
<br />
=== Writing ===<br />
The main goal of writing wiki articles is to provide the reader with required information. Writing quality material is the second goal. When writing articles periodically check that:<br />
* You maintain a good informative level of expression and provide enough (but not too much) links to pages with explanatory material. In other words, the article should be understandable by both beginners and advanced users;<br />
* Your writing/editing results in a quality article render. You should use the preview button.<br />
<br />
If you can, check pages with multiple applied CSS styles in a variety of browsers to determine display errors. If any exist, first post a report to the discussion page. However, if you are completely certain you can easily fix this, please do so.<br />
<br />
=== When to link to a main article? ===<br />
When the topic in question is important and requires detailed explanation. Invoke the <nowiki>{{</nowiki>[[Template:Main|Main]]<nowiki>}}</nowiki> template like so:<br />
<br />
<pre><br />
== Section title (or subsection, etc.) ==<br />
{{Main|Your_article}}<br />
</pre><br />
<br />
=== Linking ===<br />
When you link to a {{SITENAME}} page using the <nowiki>[[Some_page]]</nowiki> syntax the link will be displayed regardless of the page existence which gives the reader with editing rights the ability to create it. This is useful, however sometimes it is better to use a different type of linking, especially when a similar page exists in Wikipedia or any other wiki. Then there is simply no need to recreate it for {{SITENAME}}.<br />
<br />
Here is a concrete example. Suppose we want to let the reader know what DIY stands for. Instead of linking it to a {{SITENAME}} page we can link to Wikipedia using the following syntax:<br />
<pre>[[Wikipedia:do-it-yourself|DIY]]</pre><br />
Which gives the following output:<br />
[[Wikipedia:do-it-yourself|DIY]]<br />
<br />
=== Editing existing pages ===<br />
Only edit existing ''quality'' pages when:<br />
* You know what you are doing;<br />
* You've found a spelling or factual error that you know how to correct;<br />
* You can provide more useful information (i.e. expand an article).<br />
<br />
This is important because only registered wiki users are given editing rights. This means that an article will usually have few authors and sudden changes in an article may cause conflicts (may be in the form of so-called 'editing wars'). So the best thing you can do in case you think that the article is either severly outdated or needs to be rewritten is to go to the article talk page first (accessible by clicking the page discussion tab) and sharing your thoughts with the rest of the users.<br />
<br />
'''Always preview pages first'''. Also remember to check ''This is a minor edit'' checkbox before saving a page when making only a minor edit.<br />
<br />
Be especially careful when editing templates. These are used on multiple pages and thus must be handled with care.<br />
<br />
=== Inserting images ===<br />
It is good practice to insert images with secondary illustrative purpose as thumbnails. The width of those thumbnails should not exceed 250 pixels. This takes into account the variety of display settings used to view the wiki pages and should work for everyone. Also, these thumbnails should be aligned right (this is the default setting).<br />
<br />
=== Inserting videos ===<br />
When to insert videos as links within a box notification:<br />
* When the content of an article can be replaced by viewing the video<br />
* When the video is accompanied by quality annotations and/or comments<br />
<br />
When to embed videos into pages:<br />
* When the videos are used as accompanying material<br />
<br />
The same rule applies for embedded videos as for inserting image thumbnails: use max 250 pixel widths and keep the aligned to the right of the page.<br />
<br />
=== Unfinished articles ===<br />
If you think that the article suffers from too little informative quality you can insert the template <nowiki>{{</nowiki>[[Template:Stub|Stub]]<nowiki>}}</nowiki> at the top (or bottom) of the page. Please use this sparingly.<br />
<br />
=== Writing translations ===<br />
The preferred language for this wiki is English. In order to write a translation make a subpage for your language for the main page. E.g. for a Russian translation of the [[MegaDrum]] page, make a [[MegaDrum/ru]] subpage. After the translation is complete, insert the language bar on the top of the parent and child pages by invoking the <nowiki>{{</nowiki>[[Template:Languages|Languages]]<nowiki>}}</nowiki> template like so:<br />
<br />
<pre>{{Languages}}</pre><br />
<br />
This will render the language bar:<br />
<br />
{{Languages}}<br />
<br />
=== Conclusion ===<br />
Keep in mind that these are only general guidelines and that there may be exceptions. Thank you for taking your time reading this. We are looking forward to your contributions.<br />
<br />
== Notes ==<br />
<references group="notes" /></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=MegaDrum&diff=76MegaDrum2010-07-22T10:18:01Z<p>Firelord: </p>
<hr />
<div>[[File:ExampleAssembledMegaDrum.jpg|250px|thumb|An assembled MegaDrum module]]'''MegaDrum''' is a feature-rich [[MIDI drum trigger]] module developed by [[Dmitri Skachkov]]. It was made public as a [[wikipedia:Do_it_yourself|do-it-yourself]] project in the Internet on August&nbsp;1st,&nbsp;2007. Since then it has gained recognition from various drummers all over the world, from amateurs and hobbyists to professional drummers. Because of constant firmware and hardware improvement, MegaDrum has acquired support for a wide variety of drumpads from different manufacturers.<br />
<br />
As a [[wikipedia:MIDI|MIDI]] drum trigger MegaDrum does not have any built-in sounds. Its main purpose is to convert signals from commercial and do-it-yourself [[wikipedia:Electronic_drum|electronic drum pads]] into MIDI messages which are then fed to a [[wikipedia:Drum_machine|drum machine]]/[[wikipedia:Sampler_(musical_instrument)|sampler]] or a PC.<br />
<br />
The openness of the project allowed for community contributions. Among notable ones are a hardware design upgrade (courtesy of [[Synthex]]) which added plug-and-play [[wikipedia:USB|USB]] support and a multiplatform Java application to control MegaDrum from a PC — [[MegaDrum Config Tool]], written by [[Raúl Muñoz Benavente]]. The MegaDrum logo was made by forum member [http://www.megadrum.info/forums/memberlist.php?mode=viewprofile&u=97 duje07].<br />
<br />
Although MegaDrum is an open DIY-project, its firmware is not open-source. Commercial use (e.g. building a MegaDrum module and offering it for sale) requires Dmitri's explicit permission.<br />
<br />
== Features ==<br />
{{#ev:youtube|T8DWjfIUVbA|250|right|MegaDrum in action (courtesy of <a href="http://www.megadrum.info/forums/memberlist.php?mode=viewprofile&u=800">hchriste</a>)}}<br />
As a MIDI drum trigger MegaDrum offers the following features:<br />
<br />
<table cellpadding="0" cellspacing="0" border="0"><br />
<tr><br />
<td><br />
* 20/22/32/40/48/56 velocity-sensitive input channels;<br />
* 9 levels of input gain;<br />
* 10 different velocity curves and 4 custom adjustable curves;<br />
* Multilevel crosstalk suppression with 4 individual groups;<br />
* Threshold and retrigger settings;<br />
* Automatic high-level adjustment;<br />
* Velocity curves compression and shifting;<br />
* Positional sensing;<br />
* Support for simple switched and variable hi-hat controllers;<br />
</td><br />
<td style="padding-left: 20px;"><br />
* Support for for dual zone piezo-switch pads;<br />
* Support for 3 zone Roland style cymbals;<br />
* Support for 3 zone Yamaha style cymbals;<br />
* Firmware is software upgradable;<br />
* MIDI I/O with SysEx support;<br />
* USB powered with plug-n-play support and MIDI over USB;<br />
* Easy menu navigation and easy group settings adjustments;<br />
* 16x2 LCD with VU meters;<br />
* CC Choke support on every Dual Zone piezo/switch pad or 3 zone cymbals.<br />
</td><br />
</tr><br />
</table><br /><br />
<br />
As a do-it-yourself module:<br />
<br />
* Based on [[wikipedia:Atmel_AVR|ATmega]] microcontroller. Currently supported are ATmega 32/324P/644 running at 16, 20 and 24 MHz;<br />
* Uses widely available and mostly inexpensive components;<br />
* Potentiometer-free design;<br />
* ATmega/PIC chips can be programmed with simple programming cables/programmers.<ref>Initial programming of ATmega is now done by Dmitri, see [[#Legal_issues|why]].</ref><br />
<br />
== Building MegaDrum ==<br />
{{Main|Building MegaDrum}}<br />
You have the following options for building MegaDrum:<br />
* Build it yourself. Additionally you will have to order a chip from Dmitri;<br />
* Order a [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1139 Synthex kit] — using a kit greatly simplifies the assembly process;<br />
* [http://www.megadrum.info/content/i-can-build-it-you Ask Dmitri to build the module for you].<br />
<br />
Note that there are also other people who have Dmitri's permission to build and sell MegaDrum modules. See the [http://www.megadrum.info/forums/ forums] for more information.<br />
<br />
If you choose to build the module yourself you will need the following:<br />
* At least basic [[wikipedia:soldering|soldering]]/general [[wikipedia:electronics|electronics]] skills;<br />
* You have to know how to read a schematic;<br />
* You have to be able to tell one electronic part from another;<br />
* Tools are required to build MegaDrum, among them: a good soldering iron, pliers, wirecutters, a multimeter and so forth;<br />
* You need to know how to operate the aforementioned tools;<br />
* In case of making [[wikipedia:Printed_circuit_board|printed circuit boards]] at home using the toner transfer method you will need a good laser printer with quality toner, some photopaper and an etchant.<br />
<br />
It should be noted that MegaDrum is not a beginner's project and thus if you strongly feel that you're not up for the task of building it from scratch it is most likely so. Of course, if you're not afraid to learn and obtain the necessary DIY skills, you are probably capable of building MegaDrum. Otherwise, you might consider ordering a kit (it comes with quality PCB's) or simply buying the assembled module.<br />
<br />
== Updating MegaDrum firmware ==<br />
{{Main|Updating MegaDrum firmware}}<br />
<br />
== MegaDrum Configuration ==<br />
{{Main|MegaDrum Configuration}}<br />
<br />
== MegaDrum MIDI SySex support ==<br />
{{Main|MegaDrum MIDI SysEx support}}<br />
MegaDrum supports MIDI SySex messages. This allows to control/configure MegaDrum from a PC and load/store practically unlimited number of custom MegaDrum configs in addition to configs stored in built-in non-volatile memory. <br />
<br />
== Legal issues ==<br />
In spring 2010 [http://www.megadrum.info/forums/viewtopic.php?f=3&t=1245 it was discovered] that a person was building and selling MegaDrum modules without Dmitri's consent. Unfortunately, it was not possible to convince the person to cease his activities. It was then decided to encrypt future firmware releases to prevent abusive commercial use. This is why since June 2010 all new firmware files are encrypted. Updating MegaDrum with encrypted firmware requires a special type of secure bootloader which can only be programmed into the ATmega chip by Dmitri. There are two choices for obtaining a programmed chip:<br />
* Send Dmitri a compatible ATmega for programming;<br />
* Order a new chip from Dmitri.<br />
<br />
See [[ordering ATmega]] for details.<br />
<br />
== See also ==<br />
* [http://www.megadrum.info/forums/viewtopic.php?f=3&t=502 What is MegaDrum about?] forum post<br />
<br />
== Notes ==<br />
<references /></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Template:LCD/doc&diff=75Template:LCD/doc2010-07-19T16:08:04Z<p>Firelord: </p>
<hr />
<div>This template is used to illustrate various MegaDrum settings that a user can observe on the LCD screen. Here's how it works in a nutshell: you write the following code:<br />
<pre><br />
{{LCD|<br />
color=black|<br />
bgcolor=#00FF00|<br />
line1=&lt;MegaDrum.info &gt;|<br />
line2=(c)D.Skachkov{{nbsp|2}}♦|<br />
caption=MegaDrum copyright screen and contrast adjust<br />
}}<br />
</pre><br />
<br />
And get this result:<br />
{{LCD|<br />
color=black|<br />
bgcolor=#00FF00|<br />
line1=&lt;MegaDrum.info&nbsp;&gt;|<br />
line2=(c)D.Skachkov{{nbsp|2}}♦|<br />
caption=MegaDrum copyright screen and contrast adjust<br />
}}<br />
<br />
As you can see, there is 2 lines, 16 characters in each. This mimics the type of LCD currently used with MegaDrum.<br />
<br />
The format of the template is self-explanatory. Any parameter can be omitted. Defaults are: black characters on green background. The default text is the copyright screen and default caption is "MegaDrum display". Observe the main template to see how it looks.<br />
<br />
'''A note on text formatting: Please note that if a line contains more than a single whitespace character you will need to use the Nbsp template. For example, let's say you need 5 consecutive space characters in a string. You would write this as:'''<br />
<br />
<pre><br />
{{nbsp|5}}<br />
</pre><br />
<br />
Please consult the [[Template:Nbsp|documentation]] for more information.<br />
<br />
'''Also consider using &amp;lt; for the "&lt;" character and "&amp;gt;" for the "&gt;" character.'''<br />
<br />
Here's another example. Note that I used a different color/bgcolor here. You can also use standard RGB color representations such as &#35;00FF00.<br />
<pre><br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=█_______________|<br />
line2=________________|<br />
caption=MegaDrum VU Meter screen<br />
}}<br />
</pre><br />
<br />
Result:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=█_______________|<br />
line2=________________|<br />
caption=MegaDrum VU Meter screen<br />
}}<br />
<br />
Finally here is an example settings screen:<br />
<pre><br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=&amp;lt;CustomCurve1{{nbsp|2}}&amp;gt;|<br />
line2=P1:{{nbsp|11}}2♦|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
</pre><br />
<br />
The result is as follows:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2♦|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Template:LCD/doc&diff=74Template:LCD/doc2010-07-19T16:03:23Z<p>Firelord: </p>
<hr />
<div>This template is used to illustrate various MegaDrum settings that a user can observe on the LCD screen. Here's how it works in a nutshell: you write the following code:<br />
<pre><br />
{{LCD|<br />
color=black|<br />
bgcolor=#00FF00|<br />
line1=&lt;MegaDrum.info &gt;|<br />
line2=(c)D.Skachkov{{nbsp|2}}♦|<br />
caption=MegaDrum copyright screen and contrast adjust<br />
}}<br />
</pre><br />
<br />
Ang get this result:<br />
{{LCD|<br />
color=black|<br />
bgcolor=#00FF00|<br />
line1=&lt;MegaDrum.info&nbsp;&gt;|<br />
line2=(c)D.Skachkov{{nbsp|2}}♦|<br />
caption=MegaDrum copyright screen and contrast adjust<br />
}}<br />
<br />
As you can see, there is 2 lines, 16 characters in each. This mimics the type of LCD currently used with MegaDrum.<br />
<br />
The format of the template is self-explanatory. Any parameter can be omitted. Defaults are: black characters on green background. The default text is the copyright screen and default caption is "MegaDrum display". Observe the main template to see how it looks.<br />
<br />
'''A note on text formatting: Please note that if a line contains more than a single whitespace character you will need to use the Nbsp template. For example, let's say you need 5 consecutive space characters in a string. You would write this as:'''<br />
<br />
<pre><br />
{{nbsp|5}}<br />
</pre><br />
<br />
Please consult the [[Template:Nbsp|documentation]] for more information.<br />
<br />
'''Also consider using &amp;lt; for the "&lt;" character and "&amp;gt;" for the "&gt;" character.'''<br />
<br />
Here's another example. Note that I used a different color/bgcolor here. You can also use standard RGB color representations such as &#35;00FF00.<br />
<pre><br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=█_______________|<br />
line2=________________|<br />
caption=MegaDrum VU Meter screen<br />
}}<br />
</pre><br />
<br />
Result:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=█_______________|<br />
line2=________________|<br />
caption=MegaDrum VU Meter screen<br />
}}<br />
<br />
Finally here is an example settings screen:<br />
<pre><br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=&amp;lt;CustomCurve1{{nbsp|2}}&amp;gt;|<br />
line2=P1:{{nbsp|11}}2♦|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
</pre><br />
<br />
The result is as follows:<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2♦|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}</div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Template:LCD&diff=73Template:LCD2010-07-19T16:01:57Z<p>Firelord: </p>
<hr />
<div><includeonly><br />
{{#css:<br />
div.lcd-container<br />
{<br />
margin: 0.5em 0.5em 0.5em 0.5em;<br />
padding: 0.5em;<br />
border: 1px solid #B0B0B0;<br />
background: #F9F9F9;<br />
text-align: center;<br />
width: 400px;<br />
}<br />
<br />
table.lcd-table<br />
{<br />
border: 5px #000000 solid;<br />
text-align: center;<br />
width: 250px;<br />
}<br />
<br />
td.lcd-row1, td.lcd-row2<br />
{<br />
letter-spacing:3px;<br />
font-family: 'Courier New', Courier, monospace;<br />
font-weight: bold;<br />
font-size: 20px;<br />
}<br />
<br />
td.lcd-row1<br />
{<br />
padding: 10px 10px 2px 10px;<br />
}<br />
<br />
td.lcd-row2<br />
{<br />
padding: 2px 10px 10px 10px;<br />
}<br />
}}<br />
<div class="lcd-container" align="center" style="float: {{{align|none}}};"><br />
<table class="lcd-table" align="center" summary="MegaDrum display" style="background: {{{bgcolor|#00FF00}}};"><br />
<tr><br />
<td class="lcd-row1" style="color: {{{color|#000000}}};">{{{line1|&lt;MegaDrum.info&nbsp;&gt;}}}</td><br />
</tr><br />
<tr><br />
<td class="lcd-row2" style="color: {{{color|#000000}}};">{{{line2|(c)D.Skachkov&nbsp;&nbsp;&nbsp;}}}</td><br />
</tr><br />
</table><br />
''{{{caption|MegaDrum display}}}''<br />
</div></includeonly><br />
<noinclude>{{documentation}}</noinclude></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Help:Contents&diff=71Help:Contents2010-07-16T22:55:18Z<p>Firelord: </p>
<hr />
<div>'''Welcome to the {{SITENAME}} help section!''' This page currently contains:<br />
* General formatting documentation to help you get started writing articles;<br />
* Some guidelines on writing new/editing articles for {{SITENAME}}.<br />
<br />
'''Please read the following carefully especially if you haven't worked with MediaWiki based projects before.'''<br />
<br />
If you are looking for help with building/buying/troubleshooting MegaDrum, please refer to the [http://www.megadrum.info/ forums] for now.<br />
<br />
== MediaWiki markup ==<br />
<br />
=== Basic formatting ===<br />
The most important part of a MediaWiki article is meaningful plain text. However, formatting is required to deliver rich content. Basically, you enter text with special control characters/structures to get formatting effects. For example, to get '''bold''' text you would enter the following:<br />
<br />
<pre>'''This text is bold'''</pre><br />
<br />
This will render:<br />
<br />
'''This text is bold'''<br />
<br />
Please refer to the [http://www.mediawiki.org/wiki/Help:Formatting basic formatting documentation]. You can also learn the formatting rules from viewing the content of existing MediaWiki pages (e.g. [http://wikipedia.org/ Wikipedia] pages).<br />
<br />
=== Linking ===<br />
Linking to pages is explained in detail [http://www.mediawiki.org/wiki/Help:Links here]. Here is an example link to the MegaDrum article on {{SITENAME}} (this is an example of linking between {{SITENAME}} pages):<br />
<br />
<pre>[[MegaDrum]]</pre><br />
<br />
This will give the following output:<br />
<br />
[[MegaDrum]]<br />
<br />
Remember that it is bad practice to link every single word because this brings confusion to the reader.<br />
<br />
=== Article sections ===<br />
Dividing your article into sections is a good idea to separate different important parts of information from each other. To add a new section to the article use this code:<br />
<br />
<pre>==New section==</pre><br />
<br />
And if you need a subsection, type:<br />
<br />
<pre>===New section subsection===</pre><br />
<br />
More information can be obtained [http://meta.wikimedia.org/wiki/Help:Section here].<br />
<br />
If an article contains multiple sections, a table of contents will be automatically shown in the beginning of the page.<br />
<br />
=== Templates ===<br />
This is one of the most amazing features of MediaWiki. Templates are actually regular MediaWiki pages that can be inserted into other pages. However, parameters can be passed to templates that make them really flexible.<br />
<br />
To invoke an existing template you use the code<br />
<br />
<pre>{{Template_name}}</pre><br />
<br />
For example, here is the <nowiki>{{</nowiki>[[Template:LCD|LCD]]<nowiki>}}</nowiki> template without parameters. The code to invoke it is:<br />
<pre>{{LCD}}</pre><br />
<br />
This code will render:<br />
{{LCD}}<br />
<br />
And here is an example of the template with parameters:<br />
<pre>{{LCD|<br />
color=white|<br />
align=right|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2♦|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}</pre><br />
<br />
This renders the following:<br />
<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2♦|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
<br />
Templates usually come with documentation on how to use them. If you are making a new template please take some time to document its features. Do this by adding a '''doc''' subpage to your template. More info on this [[Template:Documentation|here]].<br />
<br />
=== Adding images ===<br />
This is neatly documented [http://www.mediawiki.org/wiki/Help:Images here]. Everything else falls under the [[#Guidelines|guidelines]] part of this page.<br />
<br />
=== Adding videos ===<br />
Currently there is two ways for doing this. One is invoking the video template, for example:<br />
<pre>{{video|<br />
url=http://www.youtube.com/watch?v=-7u4USyw0gU|<br />
desc=How to remove the ATmega MCU from its socket}}</pre><br />
<br />
This renders:<br />
<br />
{{video|<br />
url=http://www.youtube.com/watch?v=-7u4USyw0gU|<br />
desc=How to remove the ATMega MCU from its socket}}<br />
<br />
Another way is to insert a video directly into the page using this syntax:<br />
<br />
<pre>{{#ev:youtube|-7u4USyw0gU|250|right|How to remover the ATmega MCU from its socket}}</pre><br />
{{#ev:youtube|-7u4USyw0gU|250|right|How to remover the ATmega MCU from its socket}}<br />
<br />
You should see the result of this on the right of the page: it may appear outside of the parent section. Please note, that <nowiki>{{#ev:...}}</nowiki> is '''not''' a template but a special extension.<br />
<br />
=== References ===<br />
References can be used as footnotes. Here is an example.<br />
<br />
<pre>Here is some information that has an associated note.<ref group="notes">This is the note.</ref></pre><br />
<br />
This will render:<br />
Here is some information that has an associated note.<ref group="notes">This is the note.</ref><br />
<br />
Notes are usually added to the bottom of the page by using something like<br />
<br />
<pre>== Notes ==<br />
<references group="notes" /></pre><br />
<br />
More about references [http://www.mediawiki.org/wiki/Extension:Cite/Cite.php here].<br />
<br />
=== wikEd ===<br />
This extension can come in handy for simplifying editing articles. It can be installed for example as a Greasemonkey script in Firefox. Read more about it [http://www.mediawiki.org/wiki/Extension:WikEd here].<br />
<br />
== Guidelines ==<br />
This section contains some basic guidelines to help you get started writing (editing) articles.<br />
<br />
=== Linking ===<br />
When you link to a {{SITENAME}} page using the <nowiki>[[Some_page]]</nowiki> syntax the link will be displayed regardless of the page existence which gives the reader with editing rights the ability to create it. This is useful, however sometimes it is better to use a different type of linking, especially when a similar page exists in Wikipedia or any other wiki. Then there is simply no need to recreate it for {{SITENAME}}.<br />
<br />
Here is a concrete example. Suppose we want to let the reader know what DIY stands for. Instead of linking it to a {{SITENAME}} page we can link to Wikipedia using the following syntax:<br />
<pre>[[Wikipedia:do-it-yourself|DIY]]</pre><br />
Which gives the following output:<br />
[[Wikipedia:do-it-yourself|DIY]]<br />
<br />
=== Editing existing pages ===<br />
Only edit existing ''quality'' pages when:<br />
* You know what you are doing;<br />
* You've found a spelling or factual error that you know how to correct;<br />
* You can provide more useful information (i.e. expand an article).<br />
<br />
This is important because only registered wiki users are given editing rights. This means that an article will usually have few authors and sudden changes in an article may cause conflicts (may be in the form of so-called 'editing wars'). So the best thing you can do in case you think that the article is either severly outdated or needs to be rewritten is to go to the article talk page first (accessible by clicking the page discussion tab) and sharing your thoughts with the rest of the users.<br />
<br />
'''Always preview pages first'''. Also remember to check ''This is a minor edit'' checkbox before saving a page when making only a minor edit.<br />
<br />
Be especially careful when editing templates. These are used on multiple pages and thus must be handled with care.<br />
<br />
=== Inserting images ===<br />
It is good practice to insert images with secondary illustrative purpose as thumbnails. The width of those thumbnails should not exceed 250 pixels. This takes into account the variety of display settings used to view the wiki pages and should work for everyone. Also, these thumbnails should be aligned right (this is the default setting).<br />
<br />
=== Inserting videos ===<br />
When to insert videos as links within a box notification:<br />
* When the content of an article can be replaced by viewing the video<br />
* When the video is accompanied by quality annotations and/or comments<br />
<br />
When to embed videos into pages:<br />
* When the videos are used as accompanying material<br />
<br />
The same rule applies for embedded videos as for inserting image thumbnails: use max 250 pixel widths and keep the aligned to the right of the page.<br />
<br />
=== Unfinished articles ===<br />
If you think that the article suffers from too little informative quality you can insert the template <nowiki>{{</nowiki>[[Template:Stub|Stub]]<nowiki>}}</nowiki> at the top (or bottom) of the page. Please use this sparingly.<br />
<br />
=== Writing translations ===<br />
The preferred language for this wiki is English. In order to write a translation make a subpage for your language for the main page. E.g. for a Russian translation of the [[MegaDrum]] page, make a [[MegaDrum/ru]] subpage. After the translation is complete, insert the language bar on the top of the parent and child pages by invoking the <nowiki>{{</nowiki>[[Template:Languages|Languages]]<nowiki>}}</nowiki> template like so:<br />
<br />
<pre>{{Languages}}</pre><br />
<br />
This will render the language bar:<br />
<br />
{{Languages}}<br />
<br />
=== Conclusion ===<br />
Keep in mind that these are only general guidelines and that there may be exceptions. Thank you for taking your time reading this. We are looking forward to your contributions.<br />
<br />
== Notes ==<br />
<references group="notes" /></div>Firelordhttps://www.megadrum.info/wiki/index.php?title=Help:Contents&diff=70Help:Contents2010-07-16T22:54:34Z<p>Firelord: /* Templates */</p>
<hr />
<div>'''Welcome to the {{SITENAME}} help section!''' This page currently contains:<br />
* General formatting documentation to help you get started writing articles;<br />
* Some guidelines on writing new/editing articles for {{SITENAME}}.<br />
<br />
'''Please read the following carefully especially if you haven't worked with MediaWiki based projects before.'''<br />
<br />
If you are looking for help with building/buying/troubleshooting MegaDrum, please refer to the [http://www.megadrum.info/ forums] for now.<br />
<br />
== MediaWiki markup ==<br />
<br />
=== Basic formatting ===<br />
The most important part of a MediaWiki article is meaningful plain text. However, formatting is required to deliver rich content. Basically, you enter text with special control characters/structures to get formatting effects. For example, to get '''bold''' text you would enter the following:<br />
<br />
<pre>'''This text is bold'''</pre><br />
<br />
This will render:<br />
<br />
'''This text is bold'''<br />
<br />
Please refer to the [http://www.mediawiki.org/wiki/Help:Formatting basic formatting documentation]. You can also learn the formatting rules from viewing the content of existing MediaWiki pages (e.g. [http://wikipedia.org/ Wikipedia] pages).<br />
<br />
=== Linking ===<br />
Linking to pages is explained in detail [http://www.mediawiki.org/wiki/Help:Links here]. Here is an example link to the MegaDrum article on {{SITENAME}} (this is an example of linking between {{SITENAME}} pages):<br />
<br />
<pre>[[MegaDrum]]</pre><br />
<br />
This will give the following output:<br />
<br />
[[MegaDrum]]<br />
<br />
Remember that it is bad practice to link every single word because this brings confusion to the reader.<br />
<br />
=== Article sections ===<br />
Dividing your article into sections is a good idea to separate different important parts of information from each other. To add a new section to the article use this code:<br />
<br />
<pre>==New section==</pre><br />
<br />
And if you need a subsection, type:<br />
<br />
<pre>===New section subsection===</pre><br />
<br />
More information can be obtained [http://meta.wikimedia.org/wiki/Help:Section here].<br />
<br />
If an article contains multiple sections, a table of contents will be automatically shown in the beginning of the page.<br />
<br />
=== Templates ===<br />
This is one of the most amazing features of MediaWiki. Templates are actually regular MediaWiki pages that can be inserted into other pages. However, parameters can be passed to templates that make them really flexible.<br />
<br />
To invoke an existing template you use the code<br />
<br />
<pre>{{Template_name}}</pre><br />
<br />
For example, here is the <nowiki>{{</nowiki>[[Template:LCD|LCD]]<nowiki>}}</nowiki> template without parameters. The code to invoke it is:<br />
<pre>{{LCD}}</pre><br />
<br />
This code will render:<br />
{{LCD}}<br />
<br />
And here is an example of the template with parameters:<br />
<pre>{{LCD|<br />
color=white|<br />
align=right|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2♦|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}</pre><br />
<br />
This renders the following:<br />
<br />
{{LCD|<br />
color=white|<br />
bgcolor=blue|<br />
line1=&lt;CustomCurve1{{nbsp|2}}&gt;|<br />
line2=P1:{{nbsp|11}}2♦|<br />
caption=Custom curve '''CustomCurve1''' point '''P1''' value<br />
}}<br />
<br />
Templates usually come with documentation on how to use them. If you are making a new template please take some time to document its features. Do this by adding a '''doc''' subpage to your template. More info on this [[Template:Documentation|here]].<br />
<br />
=== Adding images ===<br />
This is neatly documented [http://www.mediawiki.org/wiki/Help:Images here]. Everything else falls under the [[#Guidelines|guidelines]] part of this page.<br />
<br />
=== Adding videos ===<br />
Currently there is two ways for doing this. One is invoking the video template, for example:<br />
<pre>{{video|<br />
url=http://www.youtube.com/watch?v=-7u4USyw0gU|<br />
desc=How to remove the ATmega MCU from its socket}}</pre><br />
<br />
This renders:<br />
<br />
{{video|<br />
url=http://www.youtube.com/watch?v=-7u4USyw0gU|<br />
desc=How to remove the ATMega MCU from its socket}}<br />
<br />
Another way is to insert a video directly into the page using this syntax:<br />
<br />
<pre>{{#ev:youtube|-7u4USyw0gU|250|right|How to remover the ATmega MCU from its socket}}</pre><br />
{{#ev:youtube|-7u4USyw0gU|250|right|How to remover the ATmega MCU from its socket}}<br />
<br />
You should see the result of this on the right of the page: it may appear outside of the parent section. Please note, that <nowiki>{{#ev:...}}</nowiki> is '''not''' a template but a special extension.<br />
<br />
=== References ===<br />
References can be used as footnotes. Here is an example.<br />
<br />
<pre>Here is some information that has an associated note.<ref group="notes">This is the note.</ref></pre><br />
<br />
This will render:<br />
Here is some information that has an associated note.<ref group="notes">This is the note.</ref><br />
<br />
Notes are usually added to the bottom of the page by using something like<br />
<br />
<pre>== Notes ==<br />
<references group="notes" /></pre><br />
<br />
More about references [http://www.mediawiki.org/wiki/Extension:Cite/Cite.php here].<br />
<br />
=== wikEd ===<br />
This extension can come in handy for simplifying editing articles. It can be installed for example as a Greasemonkey script in Firefox. Read more about it [http://www.mediawiki.org/wiki/Extension:WikEd here].<br />
<br />
== Guidelines ==<br />
This section contains some basic guidelines to help you get started writing (editing) articles.<br />
<br />
=== Linking ===<br />
When you link to a {{SITENAME}} page using the <nowiki>[[Some_page]]</nowiki> syntax the link will be displayed regardless of the page existence which gives the reader with editing rights the ability to create it. This is useful, however sometimes it is better to use a different type of linking, especially when a similar page exists in Wikipedia or any other wiki. Then there is simply no need to recreate it for {{SITENAME}}.<br />
<br />
Here is a concrete example. Suppose we want to let the reader know what DIY stands for. Instead of linking it to a {{SITENAME}} page we can link to Wikipedia using the following syntax:<br />
<pre>[[Wikipedia:do-it-yourself|DIY]]</pre><br />
Which gives the following output:<br />
[[Wikipedia:do-it-yourself|DIY]]<br />
<br />
=== Editing existing pages ===<br />
Only edit existing ''quality'' pages when:<br />
* You know what you are doing;<br />
* You've found a spelling or factual error that you know how to correct;<br />
* You can provide more useful information (i.e. expand an article).<br />
<br />
This is important because only registered wiki users are given editing rights. This means that an article will usually have few authors and sudden changes in an article may cause conflicts (may be in the form of so-called 'editing wars'). So the best thing you can do in case you think that the article is either severly outdated or needs to be rewritten is to go to the article talk page first (accessible by clicking the page discussion tab) and sharing your thoughts with the rest of the users.<br />
<br />
'''Always preview pages first'''. Also remember to check ''This is a minor edit'' checkbox before saving a page when making only a minor edit.<br />
<br />
Be especially careful when editing templates. These are used on multiple pages and thus must be handled with care.<br />
<br />
=== Inserting images ===<br />
It is good practice to insert images with secondary illustrative purpose as thumbnails. The width of those thumbnails should not exceed 250 pixels. This takes into account the variety of display settings used to view the wiki pages and should work for everyone. Also, these thumbnails should be aligned right (this is the default setting).<br />
<br />
=== Inserting videos ===<br />
When to insert videos as links within a box notification:<br />
* When the content of an article can be replaced by viewing the video<br />
* When the video is accompanied by quality annotations and/or comments<br />
<br />
When to embed videos into pages:<br />
* When the videos are used as accompanying material<br />
<br />
The same rule applies for embedded videos as for inserting image thumbnails: use max 250 pixel widths and keep the aligned to the right of the page.<br />
<br />
=== Unfinished articles ===<br />
If you think that the article suffers from too little informative quality you can insert the template <nowiki>{{</nowiki>[[Template:Stub]]<nowiki>}}</nowiki> at the top (or bottom) of the page. Please use this sparingly.<br />
<br />
=== Writing translations ===<br />
The preferred language for this wiki is English. In order to write a translation make a subpage for your language for the main page. E.g. for a Russian translation of the [[MegaDrum]] page, make a [[MegaDrum/ru]] subpage. After the translation is complete, insert the language bar on the top of the parent and child pages by invoking the <nowiki>{{</nowiki>[[Template:Languages]]<nowiki>}}</nowiki> template like so:<br />
<br />
<pre>{{Languages}}</pre><br />
<br />
This will render the language bar:<br />
<br />
{{Languages}}<br />
<br />
=== Conclusion ===<br />
Keep in mind that these are only general guidelines and that there may be exceptions. Thank you for taking your time reading this. We are looking forward to your contributions.<br />
<br />
== Notes ==<br />
<references group="notes" /></div>Firelord