The APC40 is very odd...but I wouldn't so quickly cross it off for Traktor use. I've been working around with my own mapping with 4 decks (transport, cues, beatjump, loops, beatgrids) and mixer (volume, EQs, gain, filters, no FX) for a month or so and it's really grown on me.
The issue with the APC40 and Traktor is that Traktor's layout doesn't naturally map to the APC40 like it does for the VCI-100 or any other midi controller that mimics a decks + mixer control layout; this is both an advantage and a disadvantage.
The advantage is that mapping out the APC40 really makes you think abstractly about your workflow. Mapping the APC40 is really like mapping out a midi keyboard controller like the Oxygen 8 or the Novation SLs...except that you get colored LEDs on your keys for feedback and the rectangular grid layout gives you an opportunity to group functionality in two dimensions. Moreover, the sheer number of buttons means you can map damn near everything in Traktor for 4 decks without a lot of confusion.
The disadvantage is that now you've got to think a bit harder about your workflow because the decks + mixer concept isn't made plain. This means you have to make a choice about what parts of your workflow to prioritize.
The real problems that I've found with the APC40 are that a) the default midi operation really sucks. In the default mode, some of the buttons have hard-coded behaviors that can't be overridden. To fix this, I've used ChucK to initialize the APC40 into a different state (though you could use Bome's, Midi Patch Bay, Max, Pd, etc to do the same) b) The fader section is really cramped if you have large hands or don't have the most delicate touch; it's pretty easy to thwack on the wrong fader down there if you're doing quick movements (at least for me).
Outside of not having a lot of time lately, the only thing holding me up from posting my tsi has been its dependence on an external midi app to get the APC40 in a reasonable state.
Bookmarks