This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
getting_dgedit [2015/03/16 20:41] – created muldjord | getting_dgedit [2015/03/17 14:31] – [But how does it work?] muldjord | ||
---|---|---|---|
Line 1: | Line 1: | ||
===== DGEdit, the DrumGizmo drumkit editor ===== | ===== DGEdit, the DrumGizmo drumkit editor ===== | ||
- | First things first. The DrumGizmo drumkit editor is currently in a functioning, | + | First things first: The DrumGizmo drumkit editor |
- | This page is under construction. | + | All of the drumkits you can download from this site was made using the editor. But keep in mind that it is not as simple as firing up the editor, clicking a bunch of buttons, and then you have a new drumkit. To get a functioning kit, you'll have to get your hands dirty. Specifically you'll need to create the drumkit and midimap xml files manually. |
+ | |||
+ | With that said, the editor is certainly a huge help when creating the individual drumkit instruments (snare, kickdrum, toms, crashes and so on). The entire process of taking a bunch of wav files that you've recorded using, for instance, 16 microphones and then converting them into working instruments with hit energy levels is fully supported. | ||
+ | |||
+ | Not long ago DGEdit was split up into its own project. We don't currently have a fixed release of the editor, but if you know a thing or two about compiling, you shouldn' | ||
+ | |||
+ | ===== Getting DGEdit ===== | ||
+ | ==== Clone from git ==== | ||
+ | === Pre-requisites === | ||
+ | You might have to install some missing libraries, specifically " | ||
+ | |||
+ | === Clone and compile === | ||
+ | Fire up a terminal and cd into your favorite programming projects folder. Then run the following command: | ||
+ | $ git clone http:// | ||
+ | |||
+ | Now run autogen.sh: | ||
+ | $ ./ | ||
+ | |||
+ | Configure it: | ||
+ | $ ./ | ||
+ | |||
+ | And finally, make it: | ||
+ | $ make | ||
+ | |||
+ | If all went well, you now have a fully working version of DGEdit located in the " | ||
+ | $ cd src | ||
+ | $ ./dgedit | ||
+ | |||
+ | ==== But how does it work? ==== | ||
+ | We're planning on doing some video tutorials. But since the editor is in such an early state, and the DrumGizmo file format still isn't finalized, we haven' | ||
+ | |||
+ | Small disclaimer before we begin: All of the following is written from memory. I might have missed something or something is working slightly different than what I describe. It should be quite accurate though, but please let me know if you find any errors so I can correct them. - Lars Muldjord | ||
+ | |||
+ | For now, I will try to briefly explain the entire process below: | ||
+ | * Mic up your drumkit with as many microphones as you like | ||
+ | * Record varying hits of each drum ranging from very light to very hard hits. Be sure to get at least 30 hits in there per drum | ||
+ | * Create a folder called " | ||
+ | * Export all of the tracks for each drum as wav into its own folder in the " | ||
+ | * Fire up DGEdit | ||
+ | * Click "Add files..." | ||
+ | * Doubleclick the " | ||
+ | * Now click the " | ||
+ | * In the waveform view, click and drag the threshold lines towards 0 until all hits are detected. You WILL need to use the zoom sliders to get this right. They are a bit weird right now, but they work. | ||
+ | * Fiddle around with the settings in the " | ||
+ | * Pay attention to the "hit spread" | ||
+ | * When you are satisfied, click " | ||
+ | * Have a quick gander at the " | ||
+ | * Below the "Play samples" | ||
+ | * Click the "Play samples" | ||
+ | * If there are any hits in the VERY TOP and VERY BOTTOM that seem to be out of place, then click them and click " | ||
+ | * When you are satisfied, click the " | ||
+ | * Type in a prefix such as " | ||
+ | * Now click the " | ||
+ | * Now click the " | ||
+ | * Now check that all files are there (an xml file + one wav file for each channel) and quit the editor | ||
+ | * Now relaunch the editor and complete all steps again for each of the other instruments | ||
+ | |||
+ | Done? Phew! That was quite a bit of hard work, right? Naaah, not so bad. The editor is actually quite useful :) | ||
+ | |||
+ | Next up you need to create the drumkit and midimap xml files that will bind all of the instrument xml together into one single drumkit. We usually do this by simply downloading one of the current kits and use it as a template. It's quite simple really: | ||
+ | |||
+ | * Copy one of the drumkit xml files from one of the current kits into your own kit folder. Rename it to [mykit].xml | ||
+ | * Copy one of the midimap.xml files into your own kit folder. No need to rename this one. | ||
+ | * Fire up Emacs or whatever text editor you usually use. Using one with xml syntax highlighting is recommended | ||
+ | * Load the drumkit xml file and adjust everything as needed. I will not go into details with this at this point, you'll figure it out, or go ask us on irc, we'll gladly help you out :) | ||
+ | * Same goes for the midimap file. Should be quite self explanatory. It's basically a map of the drums to certain midi notes. | ||
+ | |||
+ | Ok, so that's it! I know this howto is quite undercooked, | ||
+ | |||
+ | Questions? Join us on IRC, Freenode network, #drumgizmo channel. :) Happy drumming! |