Messages

I have noticed that I have a slight issue with cross-talk between the head and the rim on my PDX-12. If X-TRG is off, hitting the head triggers the rim quite easily. However, if I turn on X-TRG, the module sometimes cancels hits on the head that should not be canceled. The X-TRG ON/HP and ON/LP options or XTALK seem to have no effect. The general rule seems to be that the head should be tight, so I have it quite cranked up. Now, I can live with this when I'm very strict about hitting exactly on the center of the head every time, but it is a little annoying. I suspect this might be the behaviour that welshsteve described earlier in this thread because the trigger type is set to PadPP. Would it make sense to use PadPS even though the rim trigger is not a switch?

If your new card is 32GB or less, it should be quite easy. You just need to make sure the card is in FAT32 format and then you can just copy everything from the old card to the new one. Unfortunately I don't use Mac so I can't give detailed instructions on formatting.

If it's a 64GB card, things get a bit more complicated because you need to create an image file of the original card and then extend it after writing to the new card. This was discussed on the general DrumIt 5 forum recently. Again, I don't know how it is done with Mac, but I'm sure similar software exists there.

I wonder if it's a bug or just a limitation of the algorithm, based on Deve Loper's comment in this old thread... https://www.2box-forum.com/index.php?topic=3950.0

Some improvements. Halftime, What kind of triggers do you use? (I can't see any of this info in the thread - Just as reference for this post).

I think I can recall an issue from the past - have maybe nothing to do with this issue but I would like to mention it any way...I was once using a Cymbal without any edge trigger...but the settings in 2box was set to a Piezo/Switch implementation ...and the result was just some fantastic latency...and glitches...

It's all Roland at the moment. KD-85, PDX-12, 2xPD-85, PD-105, VH-10, CY-15R, CY-12R/C, CY-8 + CY-5. I have seen your comment before about invalid trigger type selection causing issues and have tried to select the correct trigger types for each pad, but of course I could have missed something. The types for the minimum set of pads that I tried (bass, snare, HH, ride) are Kick1, PadPP, HiHat and CyPSB respectively.

Yeah, with Karbonfaiba's assistance I got some improvement by setting Mask = 3 on all pads. The glitching now appears mostly when I play a beat with both the ride and the hi-hat involved. If I leave either one out, the latency is barely noticeable.

It does seem like it has to do with the trigger settings after all, but I don't really know what more I can do because all my gains & thresholds are quite moderate IMO and I only use a bit of XTalk/X-Trg on the toms. It's the same if I unplug everything except bass, snare, hi-hat and ride. Maybe one of those pads has something faulty that's sending extra trigger data, I don't know.

I totally agree with Karbonfaiba, hopefully the next generation of 2Box (if they ever get there) is a bit more forgiving.

Thanks Karbonfaiba, I'll send you a PM.

for me the search was over 1 year ago after the drumit5 mk2 release, after many sleepless nights and trying everything, an SD3 Kit from Death and Darkness simply wasn't playable, sorry but if you want to play SD2, EZD2,  BFD3, SD3 kits you will be disappointed.
It's true the latest OS X-Talk settings have a huge impact on this, if your pads need these settings on you will be disappointed too.
2box reached their Peak, no more to add with that obsolete hardware, 2Box won't move a finger because the stock kits work perfectly without any glitch, any other imported kit is like "import at own risk".

It was fun with 2box, but I moved on to an edrumin and a module from another manufacturer.
Take care.

Yeah, it doesn't really seem like 2Box is making a lot of innovations at the moment. The DrumIt 3 and 5 Mk2 are basically just tweaked versions of the original module that is already 15 years old or so. It must be a tough business for them though, so I kind of understand if they don't have enough resources for proper R&D.

I've said before that 2Box is a bit like the Linux of e-drums - if you know the internals really well, you can do some great things with it, but on the other hand, an average user might run into some weird problems that are just impossible to solve.

Personally, I can manage with the stock samples and I think they still sound a lot better than my old TD-12. Working VST exports would be a very nice bonus, but I can live without them for now.

I think we have discussed this before somewhere...the SD2 issue and the experienced latency or that particular sounds seems to eat up all system resources are related to something else than the memory card.

Here's what you can try to solve latency: (if you have not seen it previously)
- try changing the Decay from "infinite" to 10 for all pieces in your kit, it was found to help a lot.
- try setting "Max tune up" to 4 in SDSE Options > Convert to get smaller dsnd files.

Yeah... we tried all of this with Lustar, but we were unable to solve the problem completely. The set becomes playable with shortened samples and max tune +4, but at that point the cymbal samples are so short that it sounds unnatural.

One suggestion was that the XTALK/X-TRG settings contribute to the glitching and I have to use X-TRG with my PD-85 pads to prevent x-talk between the head and the rim. However, the glitching persists even if I unplug the toms, so I don't know if that can be the issue.

The search continues.

Ah well, still no silver bullet for me with the Kingston Canvas Go Plus 64 GB A2. Latency persists with the SD2 export kit.

There is this very old thread in the DIY section discussing the 2Box bass drum pad. Unfortunately the attached pictures have been lost at some point so we don't know exactly what the mods look like. https://www.2box-forum.com/index.php?topic=395.0

One thing to note about the A1/A2 classification is that apparently in some cases A2 may not be faster than A1 despite the specifications. I came by this discussion when googling what this is all about. I don't know if it matters with 2Box.

Just so that things wouldn't be too simple

That's some valuable information. Thanks for sharing, Karbonfaiba!

I've been struggling with latency when trying to use SD2 exports as I've written before. At the moment, I'm suspecting it's the combination of a not-entirely-optimal memory card and having to use the XTALK and X-TRG settings with my pads. I wonder if this new performance rating could be the key to solving the problem. Maybe I'll try to find one more card and see if it makes a difference.

You can't really edit the sounds on the module. You can control how long a sample will play, but that's about it. With 2Box, you're expected to create your sounds elsewhere, like in a VST instrument, from start to finish, and then just transfer them to the SD card of the module. I guess 2Box wouldn't be very different for you in that regard.

The module has some electronic sounds pre-installed and they are also available for download on 2Box's site: https://2box-drums.com/sounds/ (unfortunately they have removed the possibility to filter by category, so browsing through is a bit slow) - I don't know if they are of any use to you.

2Box does support triggering loops and some loops are included in the pre-installed kits.

You can adjust the bell sensitivity in the UNIT menu using MORE+DATA on the ride trigger as described in the manual. However, that setting only has three fixed values (low, medium, high) in relation to the main trigger GAIN value. If that's not enough, you could edit the ride sample file with DrumIt Manager (by Lustar) and increase the bell zone volume.

I'm wondering if it's not the X-Talk setting in itself but the amount of cross-talk that the module has to handle that affects the performance. Most of my pads are on a very basic Roland rack that is not the sturdiest and I have to use some cross-talk cancel to prevent unwanted triggering. Maybe the latency doesn't appear so easily with people who use more separate stands or a strong rack?