eDRUMin version 2.3.2 BETA now available
-
- Posts: 32
- Joined: Tue May 18, 2021 3:08 pm
Re: eDRUMin version 2.3.2 BETA now available
Oh, I can see now that the "Input" = ALL is what is not working. If I set it to a specific input it seems to work. And when I set Input=ALL, when I come back to the pedal config it is represented as "11". I have 2 ED10R2 modules connected together, and I used to be able to do note bank switching across both ED10s with this pedal.
Re: eDRUMin version 2.3.2 BETA now available
It's work on my ED4 when set too ALL, although you are right, when I close the pedal editor and open again it's showing 5 instead of all. I will test with an ED10. Hmm. Indeed ALL is not working on an ED10. Thank-you.
Fixed for the next build.
Fixed for the next build.
-
- Posts: 32
- Joined: Tue May 18, 2021 3:08 pm
Re: eDRUMin version 2.3.2 BETA now available
Thanks so much for the quick fix Rob! You rock!
Re: eDRUMin version 2.3.2 BETA now available
Hi Rob.
I have an issue with 3 zone cymbals in 2.3.2.19. Hopefully reproducible as below (ED10)....
- Factory reset
- Click input 1 and change it to Roland 3-Zone cymbal or metal 3-zone
# second input changes to BELL
- Click on BELL
# icon changes to snare and settings are for snare
- Click another input, icon changes to sidestick, click it again icon changes back to snare (etc.)
Happy to dig further if above isn't reproducible.
I have an issue with 3 zone cymbals in 2.3.2.19. Hopefully reproducible as below (ED10)....
- Factory reset
- Click input 1 and change it to Roland 3-Zone cymbal or metal 3-zone
# second input changes to BELL
- Click on BELL
# icon changes to snare and settings are for snare
- Click another input, icon changes to sidestick, click it again icon changes back to snare (etc.)
Happy to dig further if above isn't reproducible.
Re: eDRUMin version 2.3.2 BETA now available
Thanks for your very clear description of the problem. The bug is the result of some experimental code that was accidently enabled for the build. The experimental code is to allow the ring connection of a dual mono pad to be processed as a separate switch (send CCs or bank changes, which something I need for me own needs). It's very trivial to remove that code to fix the bug, but I'll see if I can find a way to fix the UI issue without removing the code. Out of curiosity, I assume the pad / inputs still functioned properly as a 3 zone cymbal?
Update: I tested here and it appears this is only a display issue and I have implemented a work around so I can keep the experimental code. It will be fixed in the next build.
Update: I tested here and it appears this is only a display issue and I have implemented a work around so I can keep the experimental code. It will be fixed in the next build.
Re: eDRUMin version 2.3.2 BETA now available
Fixed in build 20 and I updated the download links.
-
- Posts: 32
- Joined: Tue May 18, 2021 3:08 pm
Re: eDRUMin version 2.3.2 BETA now available
Hi Rob - using both .19 and .20 builds, I can see the bank changes are working find for trigger inputs, but I'm seeing an issue with the HiHat pedal. For the note bank switch sustain pedal I have Input=ALL, and the hi-hat trigger cycles through the banks fine, but the associated pedal is having an issue with bank 3. The only difference between the banks are channel numbers (banks 1-4 have channel 10-13 across all triggers and pedals). For the hi-hat pedal, the channel number for bank 3 is 1+ that of the hi-hat trigger channel for bank 3 (banks 1, 2, and 4 are fine). I cannot manually override the pedal channel # (probably by design). Let me know if more information would help understand the issue.
Never mind - I kept fiddling with it and then it suddenly started working OK. I'll keep watching it, but for now the issue is gone.
Never mind - I kept fiddling with it and then it suddenly started working OK. I'll keep watching it, but for now the issue is gone.
Re: eDRUMin version 2.3.2 BETA now available
Apologies if this was covered in release notes somewhere, but is the threshold scaling different in 2.3.2 and is a new mapping used when importing old settings/presets?
When I upgraded from 2.3.1.35 to 2.3.2.20, the threshold value changed (quite a lot) for all inputs.
For example, input 1 is '0.9' with 2.3.1.35 (no false triggers), but it changes to '3.5' when upgrading to 2.3.2.20 (and lowering it to 0.9 results in loads of false triggers - suggesting the scale has changed?)
I've also noticed that setting the threshold value and then moving to another input and back again, it's quite common the value changes by a decimal or 2.
When I upgraded from 2.3.1.35 to 2.3.2.20, the threshold value changed (quite a lot) for all inputs.
For example, input 1 is '0.9' with 2.3.1.35 (no false triggers), but it changes to '3.5' when upgrading to 2.3.2.20 (and lowering it to 0.9 results in loads of false triggers - suggesting the scale has changed?)
I've also noticed that setting the threshold value and then moving to another input and back again, it's quite common the value changes by a decimal or 2.