Messages

I have also wondered this myself, so am curious to see if anyone does have an answer, or what you find out if you experiment with this. They're all supposed to be optimized for different types of pads, but I don't know what would happen if you used the wrong pad type, I imagine some of them might not change much and some would.

Something to do with 3-zone snare pads I would assume?

DSound Manager will extract all the samples in order, either loudest to softest, or softest to loudest, your choice, for all zones in as many dsnd files as you select. This is by far the easiest way to load 2Box samples into another module or software.

The dsnd file is a wav container with metadata inside that tells the 2Box which sample goes with which velocity. You can load the file in an audio editor and pitch it down to the correct tuning, but you'll have to separate every individual hit. Alternatively, just get DKit Manager and it will do all of this for you...

Were you ever able to figure this out?

If I get another 2Box it would definitely be the MKII, however I 100% would need MIDI to work as that is how I trigger the sounds, so this would be a huge dealbreaker.

It seems that since there are various rebranded DrumIt3 modules being sold now, 2Box may just be banking on those companies to develop the firmware. You'd think that they would still post the newest releases on their own website though...

Tech 21 MIDI Mouse is created for exactly this.

Ok, but are they set to "On" for all pads or just some of them? if they are all off he won't notice any latency/lag/stuttering, and if he is not playing SD2-3 exported kits he won't notice it either...

It is on for quite a few of the pads, unsure which ones though, would have to check with him.

So that is where I am confused. Many of these other sample sets have the absolute max number of layers. Why are SD kits the only ones that are affected by this? I wish I could look at the contents of a set of kit dsnd files and investigate, but that wouldn't be allowed to post here. Then I could compare it to the other library sets my friend has (Native Instruments, BFD, NDK, others) and see what could possibly be different. Normally I'd assume it was simply the card but if it is only SD and the size is irrelevant then it must be something else.

He has the latest official one, 1.36.3. So yes, those parameters are in there.

Interesting. 2Box has told me directly (as well as a few others) that MIDI cross stick would definitely be in the next official firmware. We will see. I don't know why this site has it posted before 2Box themselves or if it is even finished (I would assume not since they haven't posted it...)

If Cross stick is finally recognized by MIDI I will be very, very happy. This may not actually show up as a new option if it is tied to the main snare or rim note numbers; it may be one note further. I will have to test and see...

Good to know, now the only issue remaining is the latency/lag/stuttering with SD3 full kits

Do you have an average file size for an entire SD3 kit where this problem occurs? A friend has kits over 1 GB running with 0 glitches (not from SD, though.) Also, if you know about audio editing and such, you can save a lot of space by trimming the ends off each sample once SDSE creates them (or in cases of libraries where you can get into the raw data, after that is extracted.) Sometimes there are 2, 4 or even more seconds of silence at the ends of samples that can simply be chopped off.

Not sure what's going on but I don't see any mention of a software download on that page? I changed the language to English, can't imagine that would break it lol. Is there a direct link or any mention of what is changed?

Edit: Apparently changing the language did in fact hide the download. Very odd, but got it now.

I have similar desires for solutions providing note-off cymbal choke, hi-hat closed/open and related mute group capabilities (i.e. percussion hits and mutes). I use a Zendrum and other MIDI controllers, and while I love the 2Box samples and core philosophy, I end up sourcing the affected items across different modules. I know there are other pathways to this end but would like to see this implemented into the unit's core feature set as it is in other modules, especially software. I understand why manufacturers would want to design around their pads, but there is a significant slice of the market that is controller oriented. It would be great to offer this flexibility for an otherwise outstanding product.

Thanks for considering!

Nice to see I am not the only one wanting this functionality. In fact I was also testing this with a Zendrum. For the hi-hat, your best bet is to hook up a dedicated hi-hat pedal to the input on the module; unless you have found a workaround, the Zendrum will not behave correctly if you use an expression pedal or similar to morph from closed to open with the correct CC number assigned (1 or 4.) Someone found a device to extend the note-off messages to make cymbal chokes work, but I forget what it was...something from MIDI Solutions I think. In fact MIDI Solutions products are your best bet in general if you want to adjust things like this as they are extremely flexible.

Enabling real 3 zone snare support would be an excellent new feature.

They would need to code new midpoint thresholds in the unit settings however to allow us to calibrate it properly. Are we suggesting 2box no longer has a coder on their support team, which is why they cannot even approach these ideas? 

The 2Box does support 3-zone snares, at least from Yamaha...But the crossstick zone was never added in as a MIDI note. I use the 2Box played from MIDI percussion pads, so there is no way to get a cross stick sound other than removing a sound from another zone (or velocity switching, which I won't do as I want the full dynamics of all sounds.) This should, in theory, be a very easy thing to add to the code -- it's just one MIDI note, probably the empty one right after snare and snare rim, just like how cymbals take up 4 neighboring notes.