|
Post by sam(otacon28) on Oct 9, 2010 3:25:34 GMT -5
Uploading samples using the M-Audio Uno - 1-In 1-Out USB Bus-Powered MIDI InterfaceAs stated in the owners manual on page 32 the readout on the module should be showing a countdown as the samples are downloading using the ddrum tool . Also be aware that the file size for any new sample uploading can't be larger than the available space left in the module . If you need to remove sounds to make room for new ones there's a step by step method on pages 27 - 30 of the SE 1.5x manual . When removing any samples from a ddrum module they need to be removed a certain way and the manual walks you through it quite well actually . Here's the way I ran everything using the M-Audio Uno - 1-In/1-Out USB Bus-Powered MIDI Interface . I have tested this on both Windows XP and on Windows 7 . It worked on both and it seems to be compatable with both Windows O.S.'s without any issues . With the ddrum module " not " connected to the UNO interface or your PC , just install the M-Audio software in your PC . Once the software is installed remove the M-Audio CD from you PC and then turn off your PC . With your PC still powered off , next you're going to connect the M-Audio UNO to your PC via USB port , and also with the ddrum module still powered off connect the midi ends to the following midi jacks on the backside of the ddrum module . Midi in on cable to Midi in on the module Midi out on cable to Midi out on the moduleThen turn on your PC and let it fully boot up . When your PC has been booted back up , next power on the ddrum module , and leave it on PAL ( while the module is booting up the screen will briefly show the O.S. version and then go right to PAL mode ) . Without doing anything to the ddrum module and with everything connected as described above Windows will recognize it . Next find and open the ddrum4 tool file within the ddrum4 sample library or download it here : ddrum4 sample uploading tool - www.4shared.com/file/ZWapNzhu/ddrum4Tool.html And then set the following settings : When you open the ddrum tool you will see ( File , Setup , Help ) on the top of the box . Click on Set-up and set the boxes to the following settings . Set the Midi In Device box to " no device "
Set the Midi Out Device box to " Usb Audio device " ^ ( it's either that setting or no device setting that you will have to choose from ) Also change the Setup Audio boxes to the following : Audio in devices : No in device Audio out devices : This should be set to whatever the soundcard that is installed on your PC , if the midi cables are connected right it should be in the choices . To upload sound samples have the ddrum tool open and you will see ( File , Setup , Help ) on the top of the box . Click on " File " and click on " Open " and then find the samples you want to upload either on the CD or if you store them on your hard drive and select the sample/samples that you want . You will then see your selected samples in the ddrum tool screen . If you have your speakers enabled you can click on the sample name in the ddrum tool and you will hear what it sounds like . Next click on the " Select One " tab , or the " Select All " tab if you selected more than one sample and then click on " Send files " tab . You will then see a box in the top right corner of the ddrum tool window that is labeled " Total Blocks " which will show the total file size of what all you're uploading into your ddrum module . You should also see the readout screen on the ddrum module showing a countdown as the samples are downloading as well . sam(otacon28)
|
|
|
Post by timinounoir on Apr 1, 2011 11:11:00 GMT -5
Hi, I just bought a used DDRUM4 yesterday, so I'm very n00b. Here is my question: When you upload sounds in the brain, where does it go? Does it go in the first available spot? Let's say I erase P5 and then I upload, does it go on P5?
|
|
|
Post by sam(otacon28) on Apr 1, 2011 16:25:02 GMT -5
Hi, I just bought a used DDRUM4 yesterday, so I'm very n00b. Here is my question: When you upload sounds in the brain, where does it go? Does it go in the first available spot? Let's say I erase P5 and then I upload, does it go on P5? Welcome to the forum , When you remove sound samples from the ddrum4 modules you remove them from an area within the module where the samples are stored ( access to the samples stored is done by pressing the sound button on the module ) The Fxx and Pxx areas of the module are more pertaining to the kits themselves and not just a particular sound sample , so when a sound is removed it is removed from the kits that it's assigned to within the module also . Once that sound is uploaded again into the module it becomes available again for whatever kits that it has been assigned to in the factory settings . But as far as sound samples themselves go the software within the ddrum4 module is allready setup to recognize and automatically file any of the sounds within the ddrum4 sample library into the proper category once they are loaded into the module . sam(otacon28)
|
|
|
Post by timinounoir on Apr 1, 2011 17:08:44 GMT -5
Thanks for your quick answer!
So if I understand this correctly, I will upload the sounds into the brain, then I can access these while building my kits and I can save these kits in the Pxx area. Am I right?
|
|
|
Post by sam(otacon28) on Apr 1, 2011 19:09:37 GMT -5
Thanks for your quick answer! So if I understand this correctly, I will upload the sounds into the brain, then I can access these while building my kits and I can save these kits in the Pxx area. Am I right? Yes that's correct . All you need to do is either hit the pad that you want to change a sound on or even the button on the module for the channel of the pad that you want to change the sound of . Then hit the sound button and select the sound you want by turning the larger dial knob . Once you change things just store the kit ( shift+store , select kit number you want to store it to , then shift+store again ) . That's one of the many great things about the sample interface within the ddrum4 module . Whenever you remove sound samples it just removes the sample itself but not the location , so all anyone needs to do is upload any samples back into the module again and they will appear right back in their location automatically . Yes any kits that you build can be saved in any of the Pxx kits area . The Fxx are all of the factory kits that are pre-arranged with the samples . If you browse the factory kits and find one that you like but want to switch a few sounds out , you can edit what you want of the kit , but to save any edits that you made you have to select a kit within the Pxx kits area to save it to . sam(otacon28)
|
|
|
Post by timinounoir on Apr 1, 2011 21:27:13 GMT -5
It didn't work! It took like an hour to upload the sounds, I have the same mem left than before I started. I saw the midi-usb cable working (it's a Supra MD100 and there doesnt seem to be any software related to this product) but when I browse around the sounds, there is no new sound. Or, the question is, how do I retrieve these sounds?
|
|
|
Post by timinounoir on Apr 1, 2011 21:49:39 GMT -5
Ok so this is what I did. I setup exactly like you said. I loaded the sounds I wanted to add in the ddrum4tool, then press send files. I saw the block count down until 0. Then I browsed the sounds and it was exactly the same than before. Memory left was 1.41 by the way... and I don't really care for the sounds stored in the brain right now. I'd rather load signature series sounds.
|
|
|
Post by sam(otacon28) on Apr 2, 2011 21:27:49 GMT -5
Ok so this is what I did. I setup exactly like you said. I loaded the sounds I wanted to add in the ddrum4tool, then press send files. I saw the block count down until 0. Then I browsed the sounds and it was exactly the same than before. Memory left was 1.41 by the way... and I don't really care for the sounds stored in the brain right now. I'd rather load signature series sounds. Just want to clarify this , so I can try more acurately to pin point where the problem your having is with uploading . When you say you saw the block count down to zero , Was the countdown also shown on the read out of the ddrum module itself as well or just the block area on the ddrum tool screen ? If you're not seeing the countdown happening on both , then there is a communication error happening and the sounds aren't getting uploaded into the module . Also did you make sure to set the midi in & midi out device settings ( like shown in the original post ) when your midi interface is hooked up and working you should have it to choose from for the midi out box I've run into quite a bit of different problems in the past with loading samples and the ddrum tool isn't always easy to work with , but with some tweaking we should be able to figure this out for yours . sam(otacon28)
|
|
|
Post by timinounoir on Apr 3, 2011 9:17:00 GMT -5
I didn't see the countdown on the module though. How much space is 1.41? I wanted to upload 32 samples with a total of 9099 blocks. I hope this doesn't mean 9 MB or I'll have to delete all the samples already in. let me try again. If this works, the sample will be available at the same place, i.e. when I push SOUNDS and turn the dial?
|
|
|
Post by timinounoir on Apr 3, 2011 9:47:38 GMT -5
I tried with 1 sound only, double checked the settings like in the original post, I have a countdown on the ddrum tool, my USB cable is flashing "midi out" during the process, so it is sending stuff, but there is no countdown on the module. My cables are hooked right, I really don't understand. I just hope I'm not stuck with these sounds.
|
|
|
Post by timinounoir on Apr 3, 2011 14:19:22 GMT -5
picture of my midi cable Attachments:
|
|
|
Post by sam(otacon28) on Apr 3, 2011 21:32:27 GMT -5
I didn't see the countdown on the module though. How much space is 1.41? I wanted to upload 32 samples with a total of 9099 blocks. I hope this doesn't mean 9 MB or I'll have to delete all the samples already in. let me try again. If this works, the sample will be available at the same place, i.e. when I push SOUNDS and turn the dial? The total amount of blocks that the ddrum4 module is able to store at one time is 8128 blocks . One block is pretty close to the size of a kilobyte . 1.41 on your module would pretty much be equivalent to 1410 blocks , so you would have eliminate some of the internal sound samples to make room for newer ones . The signature series samples are quite a bit larger files , so they require quite a bit of the storage space per sample file . Any of the sounds within ddrum4's library are automatically categorized for what type of sound sample they are ( ex. snare , bass drum , percussion , cymbal , etc . ) the name tag of any of the sound files are allready assigned in the same naming system that the ddrum4 module recognizes them as . So regardless of what sample library ( factory 3.0 , Signature Series , Mega drumkits , etc . ) that you upload a sample from within the entire ddrum4 library the module allready knows where to store it when it's uploaded into the drum module . The number in the title of each sample file is what number you will find it under once it's uploaded into the drum module . I tried with 1 sound only, double checked the settings like in the original post, I have a countdown on the ddrum tool, my USB cable is flashing "midi out" during the process, so it is sending stuff, but there is no countdown on the module. My cables are hooked right, I really don't understand. I just hope I'm not stuck with these sounds. If you're not recieving a count down on the screen on the module then there's a communication problem within the midi stream recognizing the ddrum module as the location for the midi transfer . Did you set the midi settings within the module accordingly to allow it to be able to recieve midi transfers ? Lights on the midi interface will flash as long as your PC recognizes it being connected . The ddrum module has to be set to recieve the midi transfer though . I would double check those settings to make sure that your module is set to recieve the transfer of the samples into it . sam(otacon28)
|
|
|
Post by timinounoir on Apr 3, 2011 22:01:52 GMT -5
ok, and how do you set the module? thanks for all the info by the way!
|
|
|
Post by sam(otacon28) on Apr 4, 2011 0:00:33 GMT -5
ok, and how do you set the module? thanks for all the info by the way! On the module you will see a button that is named system , which is right up by the red readout screen and the volume knob . Press that button and you will see the lighted system indicator bar keep rising . You will get to the top bar where it is marked midi , Once you're there keep pushing the button until you will see L.On , L.Pd , or L.Of . You want to set this spot to L.On if it's not allready there ( L= Local Midi control function ) . You also want to check the other 2 midi functions and make sure they are both turned off . ( P= Midi Program Change , & A= Midi Aftertouch ) I'm not sure if these make a difference being turned on or off , but I just actually tested an upload and confirmed that these were both turned off , and sent 3 files to my module without any problems . There's actually 6 midi & control selections that are made within the midi/dump section that are accessed by continuing to press the system button . They are : C1-16 P.On P.Of P.Th L.On L.Of L.Pd A.On A.Of D.AL , D.SY , D.PA , D.1 - D.26 F.-- , F.AL , F.SY , F.PA , F.1 - F.26 One thing I do want to also mention is that you should confirm that your particular interface cable you're using is connected to the module correctly . My midi cable ends are marked Midi Out & Midi In on the UNO interface . It doesn't work if the cables are run the other way . So the midi end stamped In on the interface connects to In input on the module , and the midi end stamped Out on the interface connects to the Out input on the module . No problem on the info , that's one of the great things about having a ddrum user forum again for this kind of stuff . sam(otacon28)
|
|
|
Post by timinounoir on Apr 4, 2011 10:38:29 GMT -5
I made the last changes but unfortunately, still no results. My cable is connected correctly, I put Lon, Pof and Aof, there is still no countdown on the module. When the manual says it's simple... I mean, it's not that simple...
|
|