I’m guessing that the extremely poor management of Acid software during the last years under Sony has made it so that it’s not on the list when compatibility to other soft/hardware is given in the ads. But most midi-controllers will work in my experience. For some though you might need to know a little about how to assign them manually. Personally I use an Akai MPK mini 2, it works as plug&play, but some of the knobs will require manual assigning. Not a problem for me as I rarely even use them :)
Thanks Grambler for your answer, I'm not scared of the "midi learn" thing what I'm afraid of is that usually user mapping results clumbsy and slow compared to propietary scripts and HID, I'm looking at a Nektar controller that happens to have built-in integration with most current daws but no mention to ACID anywere:)
Hope more people will join this conversation and tell us what they use and how it works.
midi is midi, so if a device is using purely midi it should work just fine. Some surfaces use DAW specific things, or things that only work in supplied plugins, which of course need to be supported by the DAW.
if in doubt, contact the support for the device you're interested in and ask them to verify if it works okay with Acid.
I'm just using some crappy old Evolution USB midi keyboard, it's nothing fancy but it works just fine :)
I bought a Nektar Impact LX25+ a few months back but just getting around to playing with it. Jumped in to Acid Pro 10 to figure out what is what and have been digging in and seeing what I can actually map to a useable workflow. The pads,keys and knobs work as expected so off the bat, I was trying to map the Transport buttons to toggle PLAY/REC/Toggle Automation.. I assumed I had to create a custom Generic Controller and 'Learns' mapping easily enough. They just don't work. Acid never gets signals from these buttons.
It's late and I'm tired, any insight would be great!