Good afternoon all
Still getting to know my 2Box (day 17) but absolutely loving it. My only real gripe so far is that it seems far too easy to trigger an unwanted and very loud edge crash sound on both the ride and the crash cymbals. The bow sounds are generally nice and dynamics are reproduced quite well but it seems that unwanted edge sounds come along too easily. I'm not sure if this is something which others have found and would be grateful for any suggestions as to how it might be overcome by altering the module setup.
Thanks in advance.
Tim
It's rather quiet on here.
Anyone any ideas?
You could try to lift the rubber edge and take a look for the plastic edge trim It could be slipped off.
Thanks drum2, I'll check that out.
Hi all, I'm not using the stock 2Box cymbals (using a Jman hybrid) and have also noticed a very major inconsistency with the cymbals from kit to kit. Its especially noticeable with the rides. I could have the exact same dsnd in 2 different kits and there will be triggering/response differences. I have also had the occurance of hitting a crash and it not being there at first hit.
I'm experimenting with the possibility that the issue may be with the module not accurately interpreting the 32gb Lexar Pro memory (from the approved list).
I previously posted a question regarding the long (relative) load time when switching from kit to kit and have since found that it is much faster when experimenting with the original 4gb card. I am next going to try an 8gb card to see the results.
Anyone want to chime in on this?
Thanks. Tony G
Wow, I had the exact opposite experience with Jman's 32 gig card and cymbal triggers. If anything, they trigger better than with the 4 gig card if you can get better triggering than perfect. I couldn't be any happier and so glad I didn't mess around with the 2 box cymbals and hi hat and went right to Jman's! No lag, no inconsistencies from kit to kit, everything working fine! Sorry to hear you guys are having some issues. Hope your modules are okay!
Quote from: StudioG4 on June 21, 2014, 01:54:21 AM
I'm experimenting with the possibility that the issue may be with the module not accurately interpreting the 32gb Lexar Pro memory (from the approved list).
I previously posted a question regarding the long (relative) load time when switching from kit to kit and have since found that it is much faster when experimenting with the original 4gb card. I am next going to try an 8gb card to see the results.
Anyone want to chime in on this?
Thanks. Tony G
I wonder if the Lexar card you picked up is genuine? There have been a lot of fake cards out there. I bought one once and posted on it here: http://www.2box-forum.com/index.php?topic=1136.90
The problem you describe does seem like it is related to the card. Especially if the symptoms are not present when using the 4GB original card.
I have been using genuine 32GB Lexar Professional 133X cards for years as well as the genuine PNY 32GB Professional card from that thread and have never experienced anything like that. One thing I am careful about is buying only in a sealed factory package.
Quote from: Jman on June 21, 2014, 05:57:29 AM
I wonder if the Lexar card you picked up is genuine? There have been a lot of fake cards out there. I bought one once and posted on it here: http://www.2box-forum.com/index.php?topic=1136.90
The problem you describe does seem like it is related to the card. Especially if the symptoms are not present when using the 4GB original card.
I have been using genuine 32GB Lexar Professional 133X cards for years as well as the genuine PNY 32GB Professional card from that thread and have never experienced anything like that. One thing I am careful about is buying only in a sealed factory package.
Yes, all my Lexar cards are genuine (all came in sealed packaging) per recommendation. I have 3 of the 32GB Lexar Professional 133X cards and now an 8GB of the same type. My findings at boot up are that my original 2Box 4GB Kingston (with 3.29GB material) boots at 4.8 seconds, the 8GB Lexar (with 7GB material) boots at 5.2 seconds (and both of these 2 change and load kits very quickly) and 2 of the 32GB cards (with 11GB of material) boot at 8 seconds and 1 of the 32GB cards (with 3.29GBmaterial) boots at 7 sec.
So what does this all mean? The smaller size cards boot much faster and load a kit faster when dialed in although, I still have drop outs (hitting a cymbal sometimes produces nothing and then it does on the next consecutive hit) but I have not noticed any latency thus far. I'm next going to try a 16GB card.
Quote from: StudioG4 on June 26, 2014, 03:40:23 PM
Yes, all my Lexar cards are genuine (all came in sealed packaging) per recommendation. I have 3 of the 32GB Lexar Professional 133X cards and now an 8GB of the same type. My findings at boot up are that my original 2Box 4GB Kingston (with 3.29GB material) boots at 4.8 seconds, the 8GB Lexar (with 7GB material) boots at 5.2 seconds (and both of these 2 change and load kits very quickly) and 2 of the 32GB cards (with 11GB of material) boot at 8 seconds and 1 of the 32GB cards (with 3.29GBmaterial) boots at 7 sec.
So what does this all mean? The smaller size cards boot much faster and load a kit faster when dialed in although, I still have drop outs (hitting a cymbal sometimes produces nothing and then it does on the next consecutive hit) but I have not noticed any latency thus far. I'm next going to try a 16GB card.
Hi Tony: Yes, boot time will prolly be a second or 2 faster with the smaller cards but I have a bunch of the PNY and the Lexar cards loaded to full capacity or very close to full capacity and they still play without latency, over months/years of using them.
I doubt the drop out you mention is because of the card. You might want to check your crosstalk settings to start with, and look at and listen to every hit/sample on your dsnd (examine the dsnd in DSoundTool) to be sure you don't have muted or empty hit samples in it. I have seen dsnds that had double hits in them and also silent hits before, that can happen when building them. When that happens, it feels like your hardware is having problems, but really it is problems with the instrument sample. Beyond that, if it is just one of the cymbals, switch it with another to check if the result is the same.
So here's an update. I've been gigging every weekend since my last post and here's latest.
Tried the Lexar pro cards (32g, 16g, and 8gig) and behavior is consistent from card to card. Problem is still with cymbals. In the practice studio I rarely lose the cymbal crash hits or the ride but when I'm at a gig, it happens regularly. I have swapped out the cymbals and the problem does not follow the cymbals so its apparently NOT a hardware problem. My Cym1 always performs flawlessly but Cym2(ride) and Cym3 have the drop outs. I'm thinking this must be a vibration problem since last night we played on a portable stage which was fairly bouncy and I was left with one functional cymbal (Cym1). I do not have any crosstalk suppression on any of my trigger inputs. Could there be something that I am missing? I am so frustrated with this situation that I am considering the Gen16's although the expense and sound quality (wish I could find someplace to demo them here in NY but...)doesn't really appeal to me. Sending the 2box unit in for repairs is also not an option since I can't be without it due to my active calendar.
Any/all suggestions would be greatly appreciated.
Tony G
Quote from: StudioG4 on August 10, 2014, 05:35:07 PM
So here's an update. I've been gigging every weekend since my last post and here's latest.
Tried the Lexar pro cards (32g, 16g, and 8gig) and behavior is consistent from card to card. Problem is still with cymbals. In the practice studio I rarely lose the cymbal crash hits or the ride but when I'm at a gig, it happens regularly. I have swapped out the cymbals and the problem does not follow the cymbals so its apparently NOT a hardware problem. My Cym1 always performs flawlessly but Cym2(ride) and Cym3 have the drop outs. I'm thinking this must be a vibration problem since last night we played on a portable stage which was fairly bouncy and I was left with one functional cymbal (Cym1). I do not have any crosstalk suppression on any of my trigger inputs. Could there be something that I am missing? I am so frustrated with this situation that I am considering the Gen16's although the expense and sound quality (wish I could find someplace to demo them here in NY but...)doesn't really appeal to me. Sending the 2box unit in for repairs is also not an option since I can't be without it due to my active calendar.
Any/all suggestions would be greatly appreciated.
Tony G
Try new cables between 2Box and cymbals, might solve the issues.
Murgen, I wish it could be that easy. I've made all my cables for years and it was one of the first things I checked but thanks for your suggestion.
Quote from: StudioG4 on August 10, 2014, 05:35:07 PM
So here's an update. I've been gigging every weekend since my last post and here's latest.
Tried the Lexar pro cards (32g, 16g, and 8gig) and behavior is consistent from card to card. Problem is still with cymbals. In the practice studio I rarely lose the cymbal crash hits or the ride but when I'm at a gig, it happens regularly. I have swapped out the cymbals and the problem does not follow the cymbals so its apparently NOT a hardware problem. My Cym1 always performs flawlessly but Cym2(ride) and Cym3 have the drop outs. I'm thinking this must be a vibration problem since last night we played on a portable stage which was fairly bouncy and I was left with one functional cymbal (Cym1). I do not have any crosstalk suppression on any of my trigger inputs. Could there be something that I am missing? Tony G
I think you are right about vibration causing the problem. This is very likely a crosstalk problem. Since this is rarely happening at rehearsal no doubt there is more vibration/crosstalk occurring at gigs. Your experience with the bigger problem on the wobbling stage probably confirms this. Since you say you have no crosstalk set on any input I would guess cymbal 2 is getting cut out because something nearby is getting so much vibration it is cancelling out your ride hits. If you can figure out what drum or drums is causing this you should be able to solve the problem. Since it is at gigs it is a little harder to determine quickly, but one way would be to raise the crosstalk setting very high on everything except the cymbal 2, then test. Drop the crosstalk back down to 0 on each instrument one at a time until you find the culprit. Also you might want to go back through each of your drums, and check your Gain and Threshold. You only want the Gain high enough so your hardest hits peak the velocity meter. Threshold you want to raise as much as you can so that your lowest hits are still detected, but if the threshold is TOO low every stage vibration will be detected. So you want threshold only as low as needed for your light hits. Raise the threshold on a drum little by little until your light hits are not detected, then lower it a little at a time till they are detected again, and leave it at that.
The threshold, gain and crosstalk settings are most likely the key to this. Hope it helps, Jerry
Thanks Jman, I will give this a try and report.
As I mentioned above: Too high of gain and/or too low of threshold on one or more of the pads would be something to look into. The lowest threshold setting is -48, the highest is -18. If you have pads close to the lowest setting you might want to look at those first. From the manual:
Low Threshold
The lower you set this value, the higher is the risk of double-trigger impulses and crosstalk.
Hello everyone,
I know it's an old topic but I have the same issue and it seems to be cymbal-related. I have 3 original 2Box cymbals and one particularly meets this issue. I reach 0dB (max hit level) as soon as I hit it just a little bit, even with gain and curve to the lowest. It's very annoying. Even my other 2 cymbals have this issue, but much less.
So I'm thinking about buying some Yamaha PCY-155 cymbals as they seem to be the best (about feeling, triggering, durability, right?) and one of the cheapest e-cymbal on the market.
docadiddle > Have you solved your issue? If so, how?
Thanks a lot.
Quote from: StudioG4 on August 10, 2014, 07:11:53 PM
Thanks Jman, I will give this a try and report.
This is an old topic but I wondered if you ever got it sorted. I notice latency when playing live, at home in a quiet setting, never, or almost never as I cannot be 100% about it. Live, it happens frequently. So I wondered if you got it figured out.
Interestingly, I have experienced more latency in live situations. I thought I was going mad (quite possible!) but I am sure I have had more latency live than at home. I had some theories about positioning of my monitor - could that be somehow interfering or triggering something. I've noticed it on my snare too, which is close to the monitor, which promoted my random theory - which is probably absolute nonsense. Through headphones though, I rarely have issues. It's live, unfortunately, where things get troubling for me.
hi
in live situation you described , it s normal you have more latency than with headphones...
- Distance from monitor : if the monitor is 1 meter far , you'll get 3ms ...
- if it s a digital mixer you will get additional latency ... between 2ms and 10ms depending if it s an old desk , or if you have a lot processing on the chanels ... A recent midas pro2 for example , can have a max latency 9ms if you insert all plugins available ..
That s why i allways recommand E-drummers to have a small analog mixer for their own use ..
You plug your drum in it , and on another channel you can recieve a line from the monitor desk with a mix of the other musicians ...
I notice latency but only on certain channels, snare or ride most notably. But it could be argued that its that which is being played when the desk delays the sound.
I will try on the next gig by having drums in the headphone mix of the module from the module, filter out and drums down the auxes which plug into the aux in of the module and see if that makes a difference. We do have a digital mixer, a Behringer X18 air.
I don't listen to the drums from the desk, those channels are muted in my monitor (on the desk). I use my headphone socket on the module to listen to my drums directly which is mixed with a mono monitor send from the desk. We use a digital Mackie and I can control my monitor settings with my iphone (it's very useful for individual monitor setups when everyone has the Mackie app on their phone).
One thing to watch... if your house electrics are not great, I am 75-85% convinced that this can cause latency issues on the D5. I am not sure why yet, but I have noticed it with a spare PSU I built for the practice room which is on the limit for supply current. I forgot my 2box PSU once before a live session, lesson learned - I built another one and keep the original in my suitcase at all times!
Hi!
If running the Drumit Five on 1.3.0.3 version it is extremely important to keep it in the "kit" mode...not unit mode. (Which occasionally could cause latency)
I have also noticed if any trigger is wrong configured...like a two zone cymbal is running in the 2box 3 zone cymbal. Or a 2 zone piezo/piezo drum pad is running in a piezo/switch setting...this could also cause nice latency.
I think also the 2box cymbals generally are too hot!
Interesting about the PSU issue...and weak power on stage.
Best Regards
Anders / www.zourman.com / hi-hat conversion modules for 2box
Quote from: ANGR77 on April 13, 2017, 07:09:06 PM
If running the Drumit Five on 1.3.0.3 version it is extremely important to keep it in the "kit" mode...not unit mode. (Which occasionally could cause latency)
Interesting. I sometime run on the unit page but not often because I sometimes need to change kits in a set. But, sometimes when I'm not confident in the hi-hat, I leave it set on hi-hat hped page so I can see what the module thinks my foot position is.
QuoteI have also noticed if any trigger is wrong configured...like a two zone cymbal is running in the 2box 3 zone cymbal. Or a 2 zone piezo/piezo drum pad is running in a piezo/switch setting...this could also cause nice latency.
Interesting 2. From the beginning I've been running DIY brass with a single piezo in the bell for 1z crashes and splashes and 2z rides. While the splashes and crashes are set up as CyEdge the Ride's always been set up as a Cym14, which has enabled me to have bow/bell with a single piezo. I wonder now, if this has caused the odd latency issue, especially as these large rides are hard to dampen and often retrigger the long decaying sounds. I added an edge switch yesterday so I can crash it, so I'll have to pay more attention to latency.