unofficial 2box forum

2Box Drumit 5 Forum => DrumIt 5 Hardware => Topic started by: Wilbo on February 13, 2020, 03:54:40 PM

Title: VH11 bow-edge problem
Post by: Wilbo on February 13, 2020, 03:54:40 PM
Hi all, I don’t know if this is a specific hardware question…
I’m playing with a VH11 hi-hat on the 2box right now (with Zourman converter). I find the edge area of the cymbal a bit wide for my liking (it’s 3 cm) and the sound of the edge is way too ‘open’ for my taste. I know I shouldn’t compare, but it’s so far off from how a real hi-hat reacts when it’s played at the same spot. I’ve tried all the hi-hats on the 2box (and some extras from the 2box website), but no edge sound comes close to acceptable for me. So I think I would prefer to have the bow sound on the edge as well. Is there a way to achieve that (without creating own sounds)?
Thanks!
Title: Re: VH11 bow-edge problem
Post by: ANGR77 on February 13, 2020, 09:09:05 PM
Hi!

Easy:  :)
1. Pick the kit
2. Hit the hi-hat
3. Press page down twice...until you reach the ENV page.
4. Press the data button on the field with +++ signs...
5. To you only see one + - - e.g only one plus in the first position...

What will happen now is that only the bow sound will sound regardsless if you hit the edge or bow hihat trigger.

6. Save if you want to keep it.

Best regards

Anders / www.zourman.com
Title: Re: VH11 bow-edge problem
Post by: Wilbo on February 14, 2020, 11:36:32 AM
Thanks Anders! I had come across the ENV page, but hadn’t realised that.
The only problem with this setting is that the closing of the hi-hat with the foot is now louder than the bow/edge sound played with the stick. This is probably because the splash is now active. Is there any way to adjust the volume of the splash only?
Title: Re: VH11 bow-edge problem
Post by: ANGR77 on February 15, 2020, 11:28:50 AM
You could try and use + - + setting...or do the following trick:

Go into unit mode
Select the hi-hat
Go to the hset page
Set the sens to -6 and the curve to neg2.

I think the Vh11 hihat will become more natural...

Best regards

Anders / www.zourman.com
Title: Re: VH11 bow-edge problem
Post by: Wilbo on February 16, 2020, 05:18:46 PM
Okay, thanks. I have the sens to -3 and the curve to normal, and that sounds sort of acceptable, but not ideal. The hi-hat chick keeps sounding weird. But I guess that comes with the splash mode. I’d rather have both the bow sound on the egde and the normal chick without the splash ( I don’t use the splash in my new band, but I do use the chick a lot during fills.) But I see there’s no setting for that.
Thinking out loud: Probably the only way around this would be to import a new hi-hat sound and assign the bow sound to the edge as well. Then I can use +++ mode so I will keep the normal hi-hat chick. Am I right, or is there another way?
Title: Re: VH11 bow-edge problem
Post by: ANGR77 on February 16, 2020, 08:49:58 PM
Hi!
You can easily take one of the hh sounds on your 2box which you like - use the DSound Tool to export the sounds from DSND to wave. (all layers will exported to separate files.) You can then just use the DrumIt Editor and drag the bow sounds to both the bow and edge trigger + pedal sounds - plus maybe adjust the volume. Then you export the whole thing as a new DSND file.

Best Regards

Anders / www.zourman.com
Title: Re: VH11 bow-edge problem
Post by: Wilbo on February 17, 2020, 12:44:17 PM
Okay, after a bit of Java trouble I downloaded the DSound Tool and it works. I'll experiment with that. Thanks!
Title: Re: VH11 bow-edge problem
Post by: Wilbo on March 02, 2020, 02:10:41 PM
Exporting to wave files with the DSound tool worked fine, but I now have a bit of trouble with the Editor. I can import the wave files to the hi-hat zones, but it only works when  I import every little file seperately. Let’s say I want to import the folder ‘Bow 60% open’, that doesn’t work. I first have to open the folder and then drag every little file into the zone. ‘Select all’ doesn’t work either, so it takes quite some time to finish the job. Not to mention the fact that half way the editor gets slower and slower. Is there a way to simplify this, or does it just work this way?