Before I forget about them – I have four issues with Addictive Drums in Podium. They’re rather nitpicky, but maybe you’d like to take a look at them some time when you’re bored. 😉
1. Only found out about this yesterday: Apparently, AD somehow distributes names for its output channels to the host. In Reaper, you’re asked if you want to create additional tracks for each output channel, and they’re named “AD Drums Master”, “AD Drums Kick”, “AD Drums Snare”, and so on… This could save time renaming the mappings yourself, if you choose to do that at all (and then it’s probably a one-time thing).
2. Events created from drag-and-dropped MIDI files should get the same name the pattern has in AD instead of “MIDI channel x”. Also applies to any MIDI files dropped in an arrangement from the browser. I guess there’s metadata inside MIDI files that conveys information like this.
3. Almost every UI element in AD can be controlled with the mouse-wheel. The wheel action is still caught by Podium if AD’s window doesn’t have focus, though, so in addition to “clicking” a button in AD, I also inadvertently end up scrolling the arrangement, for example. This doesn’t happen in other hosts.
4. This probably applies to all multi-timbral instruments: is there any way to tie specific parameters to a track?
Right now, all parameter automation is recorded on the first track that’s record armed. Alternatively, is there a way to disable MIDI input for the output mappings? I’m only assuming this would prevent parameter automation being recorded on tracks these mappings are assigned to… If so, at least automation lanes would end up as children of the MIDI track(s).
.