Jump to content

Mapping Midi to transport controls?


Lawrence

Recommended Posts

Hi all, 

I have a query that I am hoping someone can help me with. I have looked at many videos and the general help but I am getting a bit stuck.

I am  trying to simplify an editing workflow/buttons for some long podcasts. Currently using keyboard shortcats for splice and markers etc. I had an idea that I may be able ot ues my Akai MPK mini (old one) and map the "pads" of which there are eight off, to do some basic functions for me.

such as, pad 1 = rewind. pad 2 = play. pad 3 = marker.  pad 4 = cut. That sort of thing. I could then listen through and split whilst playing and press just a few buttons in front of me.

I have tried mapping keyboard to do global commands and the pads correlate to a note (starting at G#3) however that doesnt seem to work.

I had some luck mapping buttons using ACT via a generic controller but before I spent another 4 hours trying I thought I would come and ask if anyone has experience with this. some keyboard even have stop/play/record so how do people map those to do global functions?

Many thanks in advance

 

Link to comment
Share on other sites

"Cakewalk ACT" / "Generic surface" / (AZ Controller...) can do that. But in any case you need to "prepare" your Akai using its configuration utility.

I recommend "CC" mode of pads instead of notes.  If you use, make sure pads generate "unused" CC number which don't clash with knobs. F.e. assign "undefined" from the table https://www.midi.org/specifications-old/item/table-3-control-change-messages-data-bytes-2

Fo the plug-in to use. If all actions you want are in "Generic surface", it is the simplest to understand and use. Otherwise use "Cakewalk ACT". Both are well described in Cakewalk documentation (any many videos). If you want something unusual (f.e. LEDs under pads show current transport status,  tricky sequences of operations not available as a single "command", etc.), you will need AZ Controller (and long time to configure it...).

 

 

Link to comment
Share on other sites

If you want a bullet proof solution try the https://stealthswitch3.com/   I use this for both my live rig and Cakewalk. Super easy to assign 5 foot pedals to what ever your heart desires. You're using your feet which allows you to keep your hands on your guitar. It uses standard sustain type keyboard pedals

 

If thats to pricey for you I also use one of those cheap Chinese pedals you get on Amazon for around $20 to $40 bucks. https://www.amazon.ca/iKKEGOL-Triple-Keyboard-Control-Hospital/dp/B0753CSGTK  The software is not as solid as the Stealth. 

Also this is a good quality- https://www.quietpc.com/usb-footswitch 

 

71P5TZ4uhnL._AC_SL1500_.jpg

images?q=tbn:ANd9GcSXIl8KHheJ9XJRDJwievh

 

usb-footswitch.jpg

 

Edited by John Vere
Link to comment
Share on other sites

10 hours ago, azslow3 said:

"Cakewalk ACT" / "Generic surface" / (AZ Controller...) can do that. But in any case you need to "prepare" your Akai using its configuration utility.

I recommend "CC" mode of pads instead of notes.  If you use, make sure pads generate "unused" CC number which don't clash with knobs. F.e. assign "undefined" from the table https://www.midi.org/specifications-old/item/table-3-control-change-messages-data-bytes-2

Fo the plug-in to use. If all actions you want are in "Generic surface", it is the simplest to understand and use. Otherwise use "Cakewalk ACT". Both are well described in Cakewalk documentation (any many videos). If you want something unusual (f.e. LEDs under pads show current transport status,  tricky sequences of operations not available as a single "command", etc.), you will need AZ Controller (and long time to configure it...).

 

 

Hi there

This has worked very well thank you for the guidance, using the Cakewalk ACT to map the buttons number 1 to 8. the mappign was easy to force the buttons on the controllers tab to be mapped to B1 to B8. 

Then in the options tab I have mapped each of those buttons to a command. And for future for those that are interested:

B1 - go to start of this measure or start of prior measure. (this helps skip backwards a few steps to re-listen to a vocal piece)

B2 - start/stop rewind

B3 - play/stop

B4 - start/stop fast forward (helps with skipping over quite bits if you see a visual long gap)

B5 - previous marker

B6 - project | insert marker

B7 - split clips at now time

B8 - next marker

And thanks John I tihnk some pedals would also help and I will investigate more.

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...