MIDI Bindings, suggestions welcome!

edited March 12 in Development Blog
Hi all, i'm currently putting together the new MIDI binding settings for GTL. I suppose the main objective of this is to make GTL more customisable to suit as many different setups and workflows as possible.

So here are some of the functions i've got already. All questions/suggestions welcome.

Global

Transport:
• Play/Stop
• Play All
• Stop All
• Reset Session
• Divide Clock
• Times Clock
• CUE (Toggle)
• Count in (Toggle)
• Tempo (Adjust tempo via CC value)
• Set Tempo (Set a specific tempo)
• Tap Tempo
• Step Tempo (Increment tempo by given amount)
• Reset Tempo (Reset to original tempo)
• Switch Tempo Algorithm (Toggle Between pitch and time stretch tempo algorithms)

Session:
• Load Session (Load any session of choice)
• Load Previous Session
• Load Next Session

Audio:
• Set Audio Input (Change audio input to any available input)
• Next Audio Input
• Previous Audio Input
• Stereo Link (Toggle)
• Headphone Monitoring (Toggle)

Drummer:
• Drummer (Toggle)
• Select Next Drum Pattern
• Select Previous Drum Pattern
• Drummer Volume

Metronome:
• Metronome (Toggle)
• MetronomeVolume

Record Performance:
• Record Performance (Toggle)

Group
• Select Previous Group
• Select Next Group
• Select Group (User defines specific group)
• Play/Stop Selected Group
• Select Previous Loop
• Select Next Loop
• Group Volume
• Group Pan
• Fade Group
• Record Loop 1
• Record Loop 2
• Record Loop 3
• Record Loop 4
• Mute Loop 1
• Mute Loop 2
• Mute Loop 3
• Mute Loop 4
• Clear Loop 1
• Clear Loop 2
• Clear Loop 3
• Clear Loop 4
• Loop 1 Volume
• Loop 2 Volume
• Loop 3 Volume
• Loop 4 Volume
• Loop 1 Pan
• Loop 2 Pan
• Loop 3 Pan
• Loop 4 Pan
• Fade Loop 1
• Fade Loop 2
• Fade Loop 3
• Fade Loop 4
• Undo Loop 1
• Undo Loop 2
• Undo Loop 3
• Undo Loop 4
• Redo Loop 1
• Redo Loop 2
• Redo Loop 3
• Redo Loop 4

Loop
• Select Previous Loop (In session or selected group)
• Select Next Loop (In session or selected group)
• Select Loop (Specific loop defined by user)
• Record Selected Loop
• Mute Selected Loop
• Clear Selected Loop
• Selected Loop Volume
• Selected Loop Pan
• Fade Selected Loop
• Undo
• Redo


Effects: (Suggested by @dubbylabby)
• Effect parameter control
(Options include: loop number, insert slot, effect type, parameter to control, wether to add effect if it does not exist on loop already)

Comments

  • Aaawyeeeah!

    For each loop slot and audio input:
    Fx on/off
    Reverb/Delay Fx Amount/level, time
    Filter Fx Value
    Gate Fx thresold, attack, release, ratio

    Almost with default Fx until it could be possible with IAA ones...

    Enable/disable Ableton link
    Time Signature: set to... / toggle


    ;)


  • Ah yes effects control, thanks @dubbylabby. I will have to have a think about how this will work but good idea.
  • edited March 8
    Maybe making each group a different midi channel? Or almost numbering the fx by channel (FX1 Group1;FX2 Group1// FXn Groupn... FX1 GroupMain;FX2 GroupMain;FX3 GroupMain.

    It will be consistent with the Ableton export idea... AUM works in this way and gives you an idea to how to implement the menu and midi learn. :)
  • edited March 8
    Looks great! :smiley: I can't think of any extras off the top of my head.

    It like the way you have the "Step tempo" function so you can increase (or decrease I presume) the tempo by a set amount.

    I've often wished that many other apps had a similar step function assignable to volume - so that you can use a switch rather than an expression pedal / knob to change volumes - especially seeing as most apps/devices don't have any intelligence when it comes to receiving volume cc so that if you if you're trying to use one pedal/knob to control multiple tracks it's physical position won't match the virtual knoob/fader and you get those really nasty jumps in volume. Horrid! And makes using them live a bit of a no-no for me - you end up needing one knob per function meaning a huge control surface.

    I have seem some intelligent methods whereby when you move the physical fader/knob it has to reach it's current (virtual) position first before any changes become audible... this could be accompanied by a large transparent popup arrow(s) that would magically appear in front of the screen to tell you to increase (or decrease) the knob/fader to reach the current value before it gracefully disappears when you get there and the knob/fader becomes active
  • edited March 8
    This is what
    Maybe making each group a different midi channel? Or almost numbering the fx by channel (FX1 Group1;FX2 Group1// FXn Groupn... FX1 GroupMain;FX2 GroupMain;FX3 GroupMain.

    It will be consistent with the Ableton export idea... AUM works in this way and gives you an idea to how to implement the menu and midi learn. :)
    Yes it will have to be something like that. The problem at the moment is that MID bindings are global, i.e. do not change between sessions and it is likely that effect configurations will vary between sessions.

    I have a plan, see what you think when the beta comes out.
  • edited March 8
    Looks great! :smiley: I can't think of any extras off the top of my head.

    It like the way you have the "Step tempo" function so you can increase (or decrease I presume) the tempo by a set amount.

    I've often wished that many other apps had a similar step function assignable to volume - so that you can use a switch rather than an expression pedal / knob to change volumes - especially seeing as most apps/devices don't have any intelligence when it comes to receiving volume cc so that if you if you're trying to use one pedal/knob to control multiple tracks it's physical position won't match the virtual knoob/fader and you get those really nasty jumps in volume. Horrid! And makes using them live a bit of a no-no for me - you end up needing one knob per function meaning a huge control surface.
    Thanks @ricksteruk, you might be able to achieve a volume step with the 'Fade' MIDI function. Basically you will be able to set the volume 'end value' and the duration of the fade. The loop or group you are fading will begin from it's current position and fade to the defined 'end value'. If you wanted to switch volumes instantly then you could set the 'fade duration' to be really quick.


    I have seem some intelligent methods whereby when you move the physical fader/knob it has to reach it's current (virtual) position first before any changes become audible... this could be accompanied by a large transparent popup arrow(s) that would magically appear in front of the screen to tell you to increase (or decrease) the knob/fader to reach the current value before it gracefully disappears when you get there and the knob/fader becomes active
    Good point, I hadn't thought of this. There could be an option to set the volume binding to 'pickup' from the current value so you don't get any volume jumps. Like you said though it would ideally need some visual feedback.
  • @Jack you are awesome, dude!
  • This list is an embarrassment of riches.
  • Any chance you are working on tempo assign for groups? Fiddling with tempo via midi buttons in live setting is a drag. If each group had a tempo setting, it'd make tempo changes a snap!
  • Any chance you are working on tempo assign for groups? Fiddling with tempo via midi buttons in live setting is a drag. If each group had a tempo setting, it'd make tempo changes a snap!
    It's on the cards, not in the next update but I'd like to see it soon. It's technically possible already, just need to make it accessible to users. This involves creating the UI elements which is a fairly time consuming process. It will happen!
  • edited March 10
    @Jack said:
    It's on the cards, not in the next update but I'd like to see it soon. It's technically possible already, just need to make it accessible to users. This involves creating the UI elements which is a fairly time consuming process. It will happen!
    Cool, glad to hear it may be out there on the horizon.

Leave a Comment