Messages

Have you tried re-calibrating the hi-hat and checked that the selected trigger type is correct? Sometimes there may be a software glitch or bug that loses the current settings.

It's also possible that there is some physical issue with the hi-hat pad or the controller. You could try plugging the hi-hat pad to another input or another pad to the hi-hat input and see if you can reproduce the problem.

I found a hidden menu in 1.40 OS (that doesn't exist on 1.36.30)

Accessed by going to KIT - ENV page, select UNIT, hold MORE + KIT

ENV2 page is displayed with a single parameter to adjust per trigger called TRIGP (options are RIM and CROSS) it's unclear what the effect this has from my testing so far. 

Something to do with rimshots and cross-sticks maybe?

I had one more thought about the glitching issue. I have lately been using only 2box samples just so that I could play without having to worry about the module's performance. However, I now had a chance to try out some VST samples exported by someone else and there was no stuttering at all. Now, there are two clear differences to my previous experiments: 1) the VST samples are only for snare, bass and toms so the cymbal samples are all 2box, and 2) the tom samples have only one sound, so just head, no rim.

My thought is this: if the toms have no rim sample included, would it mean less processing for the module and hence smaller chance of glitching? Also, would splitting the tom inputs have the same effect? Those of you who use VST kits without issues: are you using the rims of your toms (for rim sounds or something else) or are they split to extend your kit? Does the rim make any difference?

I've just upgraded my Pearl E-Pro Live with centred trigger for the snare and side triggers for the toms (both types are Jobeky triggers). I have no issues at all with the cross-talk. One thing you can try is to turn up the threshold setting so the rim trigger will be less sensitive to any normal hits. I use the rim on the snare to get a cross-stick sound and on the toms to add cymbals. I don't need them to be super sensitive so it's ok for me.

Unfortunately, raising the threshold doesn't help. Even if the threshold on the rim is so high that the cross-stick is practically unplayable, hits on the head are still getting cancelled.

I'm beginning to believe that there is a curse upon my unit because I have all these issues that others have never experienced...

I've been having a bit of an issue with cross-talk between head and rim. Basically, I have to use the X-TRG setting on all my snare and tom pads to prevent rim sound triggering when playing the head. This is not a problem with my tom pads which have center-mounted triggers, but on the snare some of the hits on the head get cancelled because the X-TRG function seems to think that they are cross-talk from a rim hit. The same thing happens both with a Roland PDX-12 and my recent DIY conversion which is a 14" snare with a Stealth ISM6 side-mounted trigger set. I've been experimenting with trigger settings and head tension but haven't been able to find a good balance. I can live with it if I'm very careful to always hit the exact center of the snare, but it is a bit annoying. It seems like the X-TRG algorithm is designed for center-mounted triggers. Has anybody else experienced this?

Well, I think you lose nothing if you try another SD card. If the original card is corrupted and cannot be read anymore, you can download the initial card content from 2box-drums.com.

[Mix]

Sorry for my ignorance.. How Can I do that? On the 2 box module..

Read the manual.

Go to UNIT -> OUT and set OUT1-2 to "Mix!".

From the manual:

Mix The entire sum signal of the internal mixer (see also page 41) (all
instruments, metronome, line in and the song player).
Mix! Like "Mix", only with a fixed volume. The output volume no longer depends
on  the  LEVEL  control.  The  control  can  thus  be  used  exclusively  for  the 
headphone output.

Just to get the obvious stuff out of the way: have you checked that your audio cable is ok? Another thing, have you tried setting the output mode to "line", i.e. that the output volume is not affected by the module's volume knob?

Buy Drumit Manager by Lustark and use the DSound Manager part of it to increase the volume of the bell sample.

I think what I would need is having some expert with me in person to go through my pads, my module settings and my playing style to find out what is different with my kit that is causing these problems while others happily bash away with huge VST kits. I don't see that kind of scenario happening any time soon, though, so in the mean time, I'm only using 2box samples so I don't have to worry about the glitching. They are OK for my purposes, but it's just a bit frustrating to be unable to use the full potential of the module.

OK, enough of my ranting which has been going on in several threads already Hopefully Busa's issue will get solved.

Yeah... I experienced the glitching with my original SD card on all samples. After changing the card, the 2box-provided samples play well, but I haven't been able to fully get rid of the problem with VST exports. You didn't mention if you use just built-in samples or custom samples, but in the case of built-in samples only, the SD card is a likely cause.

What made a significant improvement for me (even though it's still not perfect) was setting Mask = 2 to all pads, and for the kick pad, Voice = Mono in the Unit menu. Setting Decay to 10 instead of Infinite in the Kit menu may also help.

The module has a hi-hat controller type setting for Alesis Crimson. Unfortunately I'm not familiar with any Alesis gear so I don't know if Crimson and Strike use the same kind of hi-hat.

I don't have personal experience with any of the mentioned components, but based on what I've read, here's my two cents.

The DrumIt 5 Mk1 requires the Zourman box if you want to use any other hi-hat controller than the 2box one.

Other pads should be compatible with the module directly. Although I remember reading something about 3-zone Yamaha cymbals requiring some modification? Maybe it's not a valid issue anymore.

DrumIt 5 Mk1 is still a relevant module in 2021 in my opinion, the only downside is the hi-hat compatibility. The module uses the same operating system as the newer models so I don't think the internals are very different. Paying $3000 NZD which translates to about 1800€ seems a bit steep for the kit though. I might consider the Speedlight kit despite the smaller pads.

So installing the Fame OS on a DrumIt works, but not the other way round. It makes sense because the current DrumIt OS is older than the Fame OS, i.e. the Fame support was added to the latest version(s) of the OS.

Anyway, good to know you're happy with your kit!

I tried the scripts supplied above - and actually none of them did work on my systems. Anybody that really succeeded with these scripts?

The wget command by emilianoheyns seems to work on my Linux desktop. I would guess that on a Windows machine, you need to check at least that wget is installed and maybe change "wget" to "wget.exe" if using PowerShell.

The original script is a bit problematic because it has all individual file paths hard-coded in it. If any new files have appeared after it was created, you would need to manually find them and then add them to the script. The regex approach is more elegant even though it has the small annoyance that it also downloads other stuff than just the sound files.