Audiofront

eDRUMin version 1.2 BETA is ready for testing. Please keep all discussion about this BETA in this thread. I will maintain updated links to the latest BETA version below. Feel free to share your thoughts and suggestions. As usual you can downgrade from the BETA by reinstalling version 1.1 and going to the firmware update section.

PC
http://www.audiofront.net/eDRUMin_Contr ... 2.0.12.zip

macOS
http://www.audiofront.net/eDRUMin_Contr ... 2.0.12.zip

New Features

• Factory / User Presets

Changes

• Max gain is bumped up from 8 to 12.
• Edge Sense and Bell sense are now available for cymbals when the input is set to Mono / Dual Mono (your mileage will vary)
• Improved switch processing

The manual hasn't been updated yet, however I wrote a short section about the Preset Manager and you can download it here.

Because I only have a limited number of pads to create presets from, I'm hoping other users who are comfortable with the eDRUMin UI can make presets for their commercially available pads and share them. I've created a new sub forum for sharing presets. Look in the section of the manual (linked above) for details on how to export / import user presets.

Regards,
Rob

Changes in Build 12

• The channel is now properly updated in the UI. Please note that the channel is stored along with the note banks

Changes in Build 10

• Fixed an issue that would allow a user to set input 4 as a Roland 3-Way Ride.
• For Roland 3-Way Ride, if both the bell and edge switches are activated, priority is given to the edge
• Replaced 'Slave' with 'Bell' to describe the second input.

Changes in Build 8

• Fixed flashing LED when input 2 is connected
• Includes firmware for ED10
• Fixed macOS Auto-Select state was not properly sent to the device issue.

Changes in Build 7

• A possible fix for reports of unintentional choking on cymbals
• Numerous UI improvements to reduce CPU usage.

Changes in Build 4

• When loading user presets, you can now choose what elements to load (trigger settings, velocity curve, note assignments).
• Fixed a bug for macOS that prevented user presets from being saved.
• Fixed UI updating issues, mostly apparent on macOS.

Changes in Build 3

• Added tooltips for export, edit, delete, update preset
• Exported file name is now based to preset title

[/list]

I have to ask... why are the notes not loaded from a preset? Are they saved?

The notes and banks are saved to a preset. The problem with loading the notes is that it doesn't really make sense for 'factory' presets. What should the notes be set to? I could see loading the notes and note banks for user presets perhaps.

How about for user presets, I make a new confirmation dialog checkboxes, one for 'Trigger Settings' and one for 'Notes'?

I see the logic for the factory pads. For user presets I’d like all of it saved if possible. My thoughts... if I decide I want to experiment and change a bunch of stuff I can easily get back to my “standard” setup (Notes and all) just by calling on my user presets.

That's totally reasonable. Do you think having check-boxes is useful, or is it safe to assume that the notes should always be loaded for user presets?

And you've got me thinking more about those factory presets. Perhaps when the user double clicks on a preset, the confirmation dialog could include the drum map functionality to allow the user to set the trigger settings and the notes all in one go.

I can imagine getting presets from some other user who uses SSD5 but I use SD3. In that scenario I wouldn’t want the other guy’s note mappings. So check boxes might be helpful. In fact, that would model SD3’s UI when you load a preset kit and get to pick and choose what you want loaded.

If one is using the VST's own drum settings, then there would be no need to add the MIDI notes to the presets, as it is easy to just go to the Drum Map, and select the pad in there.

Where it gets more complicated is when someone adds sounds to rims, or extra pads like cowbells, claps, etc... It's not the hard to shuffle through the notes inside the MIDI notes window of eDRUMin, sure, it would be more clicks than just bringing a preset back up, but not that hard indeed.

I think for User presets, having the notes saved within the preset is good for those special occasion of having extra pads not part of the regular default setup of the VST. The User Presets will never be as crowded as the Factory Presets... so it's fine to User save pads named "Cowbell", "Clap", etc...

For sharing presets, I wouldn't include note saving.

The drum map falls short for large kits. For instance, the drum map has four toms... I have six, so I have to manually map two toms. I have extra cymbals that aren’t in the drum map as well. Going through and setting up the notes manually seems painful. If they can be saved and be selected at load time like Rob suggested that feels like the best of both worlds.

I feel I will use User presets mostly for my own experiments. When I want to experiment with different notes and settings it will be nice, with just a single click, to go back to my normal setup.

As I mentioned, in your case, you would be using it as a dedicated drum map, and for your own use only... the MIDI notes would mean nothing to someone else.

That's the power of the User Presets, having MIDI notes saved for your personal kit.

But not for sharing to others.