eDRUMin version 2 BETA

[Rob]

I'm pretty sure I fixed that issue a couple of builds ago.

[monospace]

I'm pretty sure I fixed that issue a couple of builds ago.

I've still been seeing it with every new update.
Next update I'll try starting with the ED10 first again, see what happens.

[Rob]

It's still hanging the control application?

[monospace]

Yes, although the Update always seems to go through regardless.

[hb1980]

I posted build 5

• Fixed sending wrong aftertouch message for bell when releasing choke.
• Fixed an issue properly loading pedal input settings after loading a device preset.

That's brilliant Rob. Can confirm the pedal fix. May take a few days but I'll keep an eye out for the choke fix.
Cheers!

Can confirm the choke fix works!

Same, thanks for the super quick turnaround Rob

[mrmbira]

Hi Rob, is there any way to know which snapshot you have loaded? It would be so helpful to have the program show which snapshot you are working from. If I haven't worked with edrumin in a while I can't remember where I left off. Could the last loaded snapshot be highlighted or a different color? Or is there already a way to tell? thanks for your help, Mbira

[Dadwrshpdrum]

Bug to report.

1) Loaded a Drum Map, and the pedal editor shows the correct pedal and splash MIDI notes, but as you can see in the MIDI monitor the MIDI notes transmitted are different. Those MIDI notes are the ones for SD3 and I'm trying to play on TD-17.

2) Same time loading a drum map, all of the pads updated correctly except for input 1 (extra cymbal 1) on the red ED4. Strangely all of the other inputs on all other devices correctly updated the first time. I corrected the issue by reloading the same drum map when I had the red ED4 selected. Previously I think I was on the ED10 and sent drum map to all devices from ED10.

[Rob]

I'm guessing you're not using version 2.0.1.5. I'm pretty sure this issue was fixed a couple builds back.

[Rob]

Hi Rob, is there any way to know which snapshot you have loaded?

Not reliably.

[Dadwrshpdrum]

I'm guessing you're not using version 2.0.1.5. I'm pretty sure this issue was fixed a couple builds back.

All three devices are at this build.