Rob wrote: ↑Thu Nov 25, 2021 5:06 am
Sounds like I'm ready to take requests for version 1.7.
Since the eDRUMin is the front end of any given eDRUM equation, the ease of faster cross-over re-assign-ability between more than one Drum environment (soft or hard) could/should be a way forward - since it seems like much of the basic trigger assignment has been covered in versions to date.
I am now using two eDRUMin10's and a TMC-6, utilising 4 foot controls (HH pedal, Roland KD-120 Kick and two other Roland KT-10 kicks), 11 mesh or rubber pads (incl. two snares with 3 zone heads plus rims), VH-12 HH, 7 Roland / 1 Yamaha cymbals (all have bow/edge/bell), 2 BT-1's (sidestick on snare, cowbell etc on a tom).
So it is a lot to account for all of these MIDI channel/note assignments, nevermind all the other specifically tweaked parameters per trigger. Simple math for 2 or 3 notes per trigger (x's 22 inputs for the two eDRUMin's), plus HH, is easily 50+ MIDI note assignments per BANK.
I originally assigned the eDRUMins to a TD-10 and a TD-20, then graduated to the various SD3 libraries using Roland mapping, but focused on really just one SD3 set while trying to figure out many of the aspects of the eDRUMin world and the SD3 'midi mapping towards many articulations' world. Finally I am getting a better grasp on re-mapping the many SD3 kits within their various libraries (to the eDRUMin map) but that is a large endeavor in itself, plus trying to figure out file management save variations (kit level, map level, SD3 file level, DAW host file level).
A lot of SD3 libraries look nothing like my hardware trigger set-up - it's like re-cutting pieces for a wacky jigsaw puzzle for note re-assignment sake.
And I'd like to still use the TD-10/20 but it's not an easy re-assignment backwards, without picking through all the individual triggers.
After using this eDRUMin setup for 10 months for two eDRUMin10's, I have a few update or new feature suggestions...
Save device preset(s) to somewhere other than desktop (a default folder somewhere)
Device snapshots - they don't have to be instant, but they'd be nice to just recall inside the control app, rather than having to do the assorted computer file management routines.
Bank snapshot dumps, to copy elsewhere or store away, without the 3 other banks involved
Bank snapshot names and/or...
Note Bank labelling - name, date, description
Trigger swapping or copying would be cool without saving somewhere and re-loading
Input naming (maybe more helpful across two or three devices - especially if input swapping is implemented and one doesn't have to literally hit the hardware to ID the 'current focused' on-screen input, to act upon some file management routine)
Bank copy/swap - like 1 to 4, or 3 to 2
File Dump of bank(s) of inputs with assigned note names - output to columnated browser or a text file (comma or tab separated or whatever might open in a spreadsheet) - this could be very handy for checking assignment/re-assignment for bank copy/swap
Implement an auto-firmware update function - like 'two devices detected - firmware will be updated' when a new app version is opened for the first time. Is there a reason for us to know that the firmware needs updating?
Great product - I really enjoy using it!