- Linux, fixed issue with updating firmware of devices connected to host port.
- Fixed an issue that could result in changes to the pedal input not being saved.
eDRUMin version 2.3.2 BETA now available
Re: eDRUMin version 2.3.2 BETA now available
I posted build 26.
-
- Posts: 33
- Joined: Tue May 18, 2021 3:08 pm
Re: eDRUMin version 2.3.2 BETA now available
OK I am still seeing an issue here - even with the latest .28 version. Specifically, when I change the channel value for a hi-hat pedal then click away and return to the pedal config, the channel number has increased by 1. I can get what I want by setting it to the value 1 below what I want it to be as the implicit +1 seems to stick. So not catastrophic, but might be a nuisance to users who do not see the pattern.pumpkinking wrote: ↑Mon Nov 25, 2024 2:57 amHi 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.
LMK if you need more details or want a config export. Thanks!
Re: eDRUMin version 2.3.2 BETA now available
I've seen and fixed this issue before, but obviously my fixes are missing the real source of the problem. I'll look into it today.
Re: eDRUMin version 2.3.2 BETA now available
It was a firmware issue. It'll be fixed in the next build.
Re: eDRUMin version 2.3.2 BETA now available
I posted build 29 with the fix.