Looper goes haywire when triggering via midi

When I set looper operations to be activated via midi all attempts to loop after the initial loop goes very, very wrong.  It's like to records in halfspeed or something.  If I map all the same looper functions to (computer) keyboard keys all works as expected every time.  Currently, I have to use Bomes Midi Translator to change my midi footpedal to keyboard key strokes to get looper to function correctly.  I'm pretty sure this is a bug within Ableton since it happens or my PC or Mac.  Anyone else experiencing looper midi map issues?

13 followers

MrMicahBiggs 5 years ago | 1 comment

11 answers

  • misteralan
    contribution
    1 answer
    3 votes received
    3 votes

    I have rediscovered the way to get the MIDI commands to play nicely with Looper.

    With any button actuation on your controller the MIDI command either notes or cc's need to be sent with a high value followed by a low value...i.e. MIDI cc 40 value 127,0 or MIDI note 60 velocity 127,0.

    Live doesn't respond well to what would be similar to stuck MIDI notes or control changes...or said differently an on command without its off command immediately following.

    Good Luck!

    AL

     

    2 years ago | 0 comments
  • wackMC
    contribution
    1 answer
    2 votes received
    2 votes

    Just want to point out that this issue still plagues Live 9.1.7. I have the same problem as the OP: using the midi map functionality on the looper's 'Multi-Purpose Transport Button' produces strange behavior, but using the mouse or keyboard to control it works fine. This is extremely frustrating and I'm surprised this problem hasn't been addressed yet!

    3 years ago | 0 comments
  • bdj
    contribution
    3 answers
    3 votes received
    1 vote

    I'm having the same Problem!!  though I have the looper rec/play toggle mapped via max for live to param 1 of the device. It's happening on all tracks where I have a looper.

    5 years ago | 0 comments
  • bdj
    contribution
    3 answers
    3 votes received
    1 vote

    sooooooooo

    I discovered the ctlout object in max (having completely overlooked it in my excitement over the max for live api .___. ) and midimapping from max DOESN'T glitch the pitch like using the api. . .  

     

    I'm interested to know if others have had problems with either M4L or midi control of the looper.  If you find theis threrd looking for an answer, make a post!

    5 years ago | 0 comments
  • bdj
    contribution
    3 answers
    3 votes received
    1 vote

    Today the loopers are playing back an octave too high again.  

    5 years ago | 0 comments
  • altmuse
    contribution
    5 answers
    8 votes received
    1 vote

    Have you made sure to assign the correct settings in Song control and Tempo control Pull down menus? If you explain to me your scenario I can help you with the correct settings. i.e., if you are looping to an other clips tempo or to a click OR if you are setting the tempo with an initial live loop...the settings will need to be different. I'm working on an hour long looping piece and it's working so far for me.

    xoxo, AK

    5 years ago | 0 comments
  • altmuse
    contribution
    5 answers
    8 votes received
    1 vote

    Could you give me more detail on how you used the ctlout and specifically routing to MIDI learn the looper, I'm stuck on that one...

     

    xoxo, aK

    5 years ago | 0 comments
  • taylortronic
    contribution
    1 answer
    1 vote received
    1 vote

    this is a horrible horrible glitch that renders ableton almost useless for my purposes

    3 years ago | 1 comment
  • obscured
    contribution
    2 answers
    2 votes received
    1 vote

    thanks misteralan!

    2 years ago | 1 comment
  • aaronjamesandtheblackwater
    contribution
    3 answers
    4 votes received
    1 vote

    I'm having issues with the looper where if I record anything larger than an 8 bar loop... it skips entire bars of the loop... I should also mention that this is only if I use midi to start and stop the looper... if I do it manually it has no issues... 

    For example... I've played a 12 bar loop and it's playing back through the first 4 and then skips to the last two... and repeats that way...

    My Settings are as follows:

    Quantization: NONE
    Record: X BARS (then play)
    Song Control: NONE
    Tempo Control: Follow Song Tempo
    Speed: 0.00
    Reverse: OFF
    Feedback: 100%
    input -> Output: Always

    I was operating with 0 issues what so ever and then out of nowhere it just started not working... 

    halp! :(



     

    8 months ago | 0 comments
  • GRX
    contribution
    1 answer
    1 vote received
    1 vote

    Hey Everybody!

    I've been having the exact same issue with Looper and my MIDI controllers, and Misteralan's solution is working perfect (so far) for me.

    I am using a Traktor F1 to grab audio loops on the fly from MIDI tracks, I found that when I looped a synth it would play back for a bar and then inexplicably jump back to whatever I had previously recorded. After minor fandangling (thanks to Misteralan) the problem appears to be fixed:

    in the NI Controller Editor, the button trigger WAS set to

    TYPE: Control Change

    MODE: Trigger

    VALUE: 127

       and everything was going haywire.

    I changed it to

    TYPE: Control Change (same as before)

    MODE : Gate

    Value: OFF=0, ON=127

        now things seem to be working like they're supposed to. I hope the solution continues, and thanks again Misteralan for the tip!! You saved my life, as my whole live setup is based around grabbing audio loops.

     

    3 months ago | 0 comments

You need to be logged in, have a Live license, and have a username set in your account to be able to answer questions.

Answers is a new product and we'd like to hear your wishes, problems or ideas.