Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
getting_dgedit [2015/03/16 21:33] – [But how does it work?] muldjordgetting_dgedit [2015/03/18 14:31] (current) – [But how does it work?] muldjord
Line 1: Line 1:
-This page is under construction. 
- 
 ===== DGEdit, the DrumGizmo drumkit editor ===== ===== DGEdit, the DrumGizmo drumkit editor =====
 First things first: The DrumGizmo drumkit editor DGEdit is currently in a functioning, but very early phase of development. All of the essentials for importing, editing and exporting the raw drumkit recordings are there - but it is not exactly user friendly. First things first: The DrumGizmo drumkit editor DGEdit is currently in a functioning, but very early phase of development. All of the essentials for importing, editing and exporting the raw drumkit recordings are there - but it is not exactly user friendly.
Line 35: Line 33:
 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't put too much effort into it yet. This will change when we get a bit further along with the development. 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't put too much effort into it yet. This will change when we get a bit further along with the development.
  
-Small disclaimer before we being: All of the below 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+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: For now, I will try to briefly explain the entire process below:
   * Mic up your drumkit with as many microphones as you like   * 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   * 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
-  * Export all of the tracks for each drum as wav into its own folder with the filenames being the channel names (overhead_l, overhead_r, snare_top and so on)+  * Create a folder called "[kitname]_raw_files" 
 +  * Export all of the tracks for each drum as wav into its own folder in the "[kitname]_raw_files" folder ("snare", "tom1" and so on) with the filenames being the channel names (overhead_l, overhead_r, snare_top and so on)
   * Fire up DGEdit   * Fire up DGEdit
   * Click "Add files..." and select ALL 16 wav files for ONE drum (or however many microphones you recorded it with, 16 is just an example)   * Click "Add files..." and select ALL 16 wav files for ONE drum (or however many microphones you recorded it with, 16 is just an example)
Line 54: Line 53:
   * If there are any hits in the VERY TOP and VERY BOTTOM that seem to be out of place, then click them and click "Delete" on the keyboard. The hits will now realign so that the next top or bottom hit is equal to the highest or lowest hit.   * If there are any hits in the VERY TOP and VERY BOTTOM that seem to be out of place, then click them and click "Delete" on the keyboard. The hits will now realign so that the next top or bottom hit is equal to the highest or lowest hit.
   * When you are satisfied, click the "Export" tab   * When you are satisfied, click the "Export" tab
-  * Type in a prefix such as "snare_top" or whatever instrument you are currently working with. As good practice, DON'T USE SPACES or SPECIAL CHARACTERS! You might be able to, but it's not a good idea. We haven't tested it. Just keep it simple, lowercase letters and underscores+  * Type in a prefix such as "snare_top" or whatever instrument you are currently working with. As good practice, DON'T USE SPACES or SPECIAL CHARACTERS! You might be able to, but it's not a good idea. We haven't tested it. Just keep it simple letters and underscores
   * Now click the "..." button and choose where to export the instrument. We suggest making a toplevel folder named after your drumkit. In that folder, create folders for each instrument. If in doubt, download one of the drumkits we already made and see how we did it.   * Now click the "..." button and choose where to export the instrument. We suggest making a toplevel folder named after your drumkit. In that folder, create folders for each instrument. If in doubt, download one of the drumkits we already made and see how we did it.
   * Now click the "Export" button and wait for all of the files to be generated. Shouldn't take long.   * Now click the "Export" button and wait for all of the files to be generated. Shouldn't take long.
-  * Now check that all files seem to be there and quit the editor+  * Now check that all files are there (an xml file + one wav file for each hit velocity) and quit the editor
   * Now relaunch the editor and complete all steps again for each of the other instruments   * 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 :) 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:+Next up you need to create the drumkit and midimap xml files that will bind all of the instrument xml files 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 drumkit xml files from one of the current kits into your own kit folder. Rename it to [mykit].xml
getting_dgedit.1426538023.txt.gz · Last modified: 2015/03/16 21:33 by muldjord
Trace:
GNU Free Documentation License 1.3
Valid CSS Driven by DokuWiki Recent changes RSS feed Valid XHTML 1.0