#Using akai mpd 24 with pro tools how to#

As also a fellow 'Akai' user I was simply pointing out that I did not have to go to a command prompt at all before using midi learn to program the transport Exactly as you described in the 2nd paragraph.ДЇidelityMusic Second, understanding how a DAW handles controllers and how to set them up is always necessary, I know that, I have just mentioned that this takes most of the setup time and that is not SONAR fault. (Does the Steam installation add additional midi/act capability than the download? not understanding the connection). I am not a Steam user but I am running 64bit.

Do that until you've mapped all of the transport controls. Click on a parameter, press 'Learn', then press the button on your Akai controller. On the bottom right hand side you'll see 'Global Parameters'. Once you've followed the instructions sent to you by Akai open up the controller properties in Sonar. So what takes minutes to do in other DAWs took me two days in Sonar. Then you have to manually set up the transport. In my case I needed to activate the dll's for the Controller/Surface I wanted to use in the CMD, that's an issue on Sonar's part.

#Using akai mpd 24 with pro tools 64 Bit#

And The transport is working fine without any 'special' cmd.Д«ut are you a Steam user using the 64 bit version? If not then that explains why you didn't need that step.

#Using akai mpd 24 with pro tools software#

Just to clear things up if you didn't notice, I wasn't complaining, someone posted before me talking about Akai's software being a nightmare and I chimed in with my experience with Sonar being the nightmare.ДЇidelityMusic LunaTech I am using and Akai MPD 26 (hopefully that's about the same from a transport standpoint). My experiences with other DAW's gives reason behind my expectation for 'automatic' in regard to basic transport control. Second, understanding how a DAW handles controllers and how to set them up is always necessary, I know that, but if you think not having basic support for widely used controllers is the norm I'll be the first to tell you that's not the case. I'm talking hours mapping DAW functions (open windows, cut, copy, paste, jog, toggle options, etc.) to proper MIDI Channels with note assignments. First, I assure you I know exactly what it is to map a controller to a DAW, and I'm not talking about basic transport controls. I don't get what point you're trying to make here.В Are you trying to insinuate that I don't know the process behind mapping a controller to a DAW, along with saying that it didn't actually take me as long as I say it did searching for days to fix the issues I had with Sonar. It is still much less then a day, the relevant part in SONAR documentation is just several pages to read. What takes time is to understand why it is required and how to do it. The mapping itself takes ~5 sec per control, so several minutes in total for any device.

Someone always has to manually set up everything, the difference is who is doing that: 1) Cakewalk, in case there is some affiliation with hardware producer (previously Roland, so Roland keyboards had 'automatic' support) 2) The hardware producer, in case they want attract SONAR customers (Nektar Impact, Novation Automap, etc.) 3) The user, in case he/she has made a decision to use some arbitrary device. There is no magic in this world, there is no 'automatic' adaptation.

Do you mean this issue ? Then you have to manually set up the transport. FidelityMusic But are you a Steam user using the 64 bit version? If not then that explains why you didn't need that step.