eDRUMin 1.5 BETA now available

[Rob]

First crash report. Happened when I tried adjusting one of the level controls on the new HiHat Levels screen.

(I'm still using a long USB repeater cable, so if this is related to that, let me know what to look for so I can only submit relevant crashes. This looked different though.)

The crash log points to an issue with my code. I'll look into it. Thanks.

[Rob]

I have two hi-hat controllers. The controller plugged into controller input 2 did not maintain my note and CC mappings. The CC was set to 62 instead of 8 and my foot and splash notes were wrong. It was easy enough to fix though.

For now, avoid making adjustments to that second hihat input. Some of the 2nd hihat's memory allocation is overlapping with the first trigger input's memory allocation. Could lead to triggering issues on that first input and undefined behavior including a full hardware crash (although this hasn't happened to me). It's fixed in the next build.

[Mylo]

I have two hi-hat controllers. The controller plugged into controller input 2 did not maintain my note and CC mappings. The CC was set to 62 instead of 8 and my foot and splash notes were wrong. It was easy enough to fix though.

For now, avoid making adjustments to that second hihat input. Some of the 2nd hihat's memory allocation is overlapping with the first trigger input's memory allocation. Could lead to triggering issues on that first input and undefined behavior including a full hardware crash (although this hasn't happened to me). It's fixed in the next build.

Too late... I changed input 2 to their proper CC and note values and everything seemed to work. Controller 1 and 2 are working fine. I guess I got lucky. But I won’t touch anything else until the next build.

[Rob]

I'm trying not to make too many builds, but that memory allocation issue is important to resolve.

https://www.audiofront.net/eDRUMin_Cont ... .5.0.1.zip
https://www.audiofront.net/eDRUMin_Cont ... .5.0.1.zip

Changes in build 1

• Fixed memory allocation issue.
• Fixed BT-1 sending out wrong note in sensor mode

[Mylo]

Changes in build 1

• Fixed memory allocation issue.

This one looks good.

[Dadwrshpdrum]

I installed 1.5.0.1. All of my pads seems to continue to operate as normal. I checked heads, rims, and rimshot plus bow and edge for cymbals. No issues.

Only issue I had was the pedals. Like the previous poster I have two HH pedals, but one (Alesis Pedal) I use to change note banks. I think with autosense on the VH10 and alesis pedal got messed up. First, the Alesis Pedal screen (input 2) did not show the note bank numbers changing, even though the note banks were changing (I could tell by hitting a pad with different notes). I reset that input, and maybe that messed up VH10 as well, to see if that would fix it. Ended up I had to setup all the pedals all over, even the VH10 even though I only reset the Alesis pedal. The VH10 I had to relink to cymbal, and setup up all four note banks again. I power cycled and with auto sense on the VH10 came back not as a HH pedal but like a boss FS-6 (which is the graphic for the Alesis pedal). So I had to set it up again. Then I turned autosense off. Power cycled and no more issues. Just power cycled again and again no issue.

I tested out the new BT-1 pad type. Starting condition was an input split with a stereo splitter. A KD10 was connected to the tip connector and the Bt-1 was connected to the ring connector. All TRS cables. When I selected the BT1 (was a rubber pad before) the input changed from dual mono to stereo. No big deal so I changed it back to dual mono. Reloaded preset for the KD10. The BT1 remained as a BT1 graphic and pad type on the tip (right hand side) of the input, and KD10 was a rubber pad on the ring (left hand side of input). Great. Looked awesome. The BT1 continued to operator in “sensor” mode. However I can’t link to my snare pad. The option is not available. I completely understand why there is no option to select sensor or xtalk when in dual mono (the stereo/normal BT1 pad type looked great by the way for the short period of time I saw it), but I was hoping I could still link to an input. Is there a way to not display the sensor/x-talk option, but keep the link to input?

Not sure the purpose of X-stick scaler for a BT1 pad. And as I was typing this I came across a weird artifact. If I hit the KD10, which has edge sense visible (but off since it is a kick) since it is a rubber pad. When I hit the BT1 pad, edge sense remains visible. I turned it on, hit around a bit and saw the needle move around. If I keep edge sense on it stays there as I hit around other pads. If I shut it off and hit around to other pads (not the KD10) then it goes away, and doesn’t reappear till I hit the KD10. I was about ready to type why is edge sense on a BT1 pad, but then I figured it wasn’t supposed to be there.

Preset manager looks good and easy to use. Looks like you added a green box around the pad you have selected while in preset manager, very nice. I only loaded one V1.4 preset and it was the KD10.

The auto save button worked the one time I tried it.

[monospace]

• Fixed BT-1 sending out wrong note in sensor mode

Confirmed.

[Rob]

I tested out the new BT-1 pad type. Starting condition was an input split with a stereo splitter. A KD10 was connected to the tip connector and the Bt-1 was connected to the ring connector. All TRS cables. When I selected the BT1 (was a rubber pad before) the input changed from dual mono to stereo. No big deal so I changed it back to dual mono. Reloaded preset for the KD10. The BT1 remained as a BT1 graphic and pad type on the tip (right hand side) of the input, and KD10 was a rubber pad on the ring (left hand side of input). Great. Looked awesome. The BT1 continued to operator in “sensor” mode. However I can’t link to my snare pad. The option is not available. I completely understand why there is no option to select sensor or xtalk when in dual mono (the stereo/normal BT1 pad type looked great by the way for the short period of time I saw it), but I was hoping I could still link to an input. Is there a way to not display the sensor/x-talk option, but keep the link to input?

Firstly, the BT-1 *must* be on a stereo input in order for its crosstalk cancellation feature to work. If it's on a split input, then is can only operate in sensor mode and showing it linked it with a snare pad would be misleading.

In testing this, I see that there is an issue with changing the 'ring' pad of a dual mono input. When you change it, the icon for both the tip and ring change (display bug) which I've now fixed for the next build. Also the x-stick scaler control and edge sense weren't properly being hidden, but that is now also fixed.

Only issue I had was the pedals. Like the previous poster I have two HH pedals, but one (Alesis Pedal) I use to change note banks. I think with autosense on the VH10 and alesis pedal got messed up. First, the Alesis Pedal screen (input 2) did not show the note bank numbers changing, even though the note banks were changing (I could tell by hitting a pad with different notes). I reset that input, and maybe that messed up VH10 as well, to see if that would fix it. Ended up I had to setup all the pedals all over, even the VH10 even though I only reset the Alesis pedal. The VH10 I had to relink to cymbal, and setup up all four note banks again. I power cycled and with auto sense on the VH10 came back not as a HH pedal but like a boss FS-6 (which is the graphic for the Alesis pedal). So I had to set it up again. Then I turned autosense off. Power cycled and no more issues. Just power cycled again and again no issue.

I will have to spend some tme trying to figure out what's going on here. Thanks for the report.

[Rob]

Only issue I had was the pedals. Like the previous poster I have two HH pedals, but one (Alesis Pedal) I use to change note banks. I think with autosense on the VH10 and alesis pedal got messed up. First, the Alesis Pedal screen (input 2) did not show the note bank numbers changing, even though the note banks were changing (I could tell by hitting a pad with different notes). I reset that input, and maybe that messed up VH10 as well, to see if that would fix it. Ended up I had to setup all the pedals all over, even the VH10 even though I only reset the Alesis pedal. The VH10 I had to relink to cymbal, and setup up all four note banks again. I power cycled and with auto sense on the VH10 came back not as a HH pedal but like a boss FS-6 (which is the graphic for the Alesis pedal). So I had to set it up again. Then I turned autosense off. Power cycled and no more issues. Just power cycled again and again no issue.

I found the issue... I'll post a fix soon.

[Rob]

https://www.audiofront.net/eDRUMin_Cont ... .5.0.2.zip
https://www.audiofront.net/eDRUMin_Cont ... .5.0.2.zip

If you previously updated an ED10 with build 0 or 1, you will need to reset your 2nd pedal input. Sorry.

Changes in build 1

• Fixed firmware update issue with 2nd pedal input.
• Fixed UI layout issues for BT-1 on a split input.
• UI fixes for split inputs