Looper misbehaves when triggered with a Footswitch..

[raze]

I would have thought that behringer would be more compatible, have you tried programming it to send notes instead of CC messages? (if possible?)

oh yes, right, it could be a note too. it might work without the polarity hassle
as of Behringer,:
you can have a note , two CC#s and 4 PCc for every button

[n13]

Same problem here. Can´t use my yamaha fc5 footswitch with the apc40 for using it with looper. I think it´s the polarity problem, so why can´t it be switched with the apc40? If I use the fc5 with my ozone m-audio keyboard it´s fine, because you can change polarity there, if you plugin the footswitch while it´s pressed. unfortunateyl this doesn´t work on the apc40.

Andre

[raze]

which again brings me to the quest if Live couldn't do the job.
?

[[mid]]

Hi,

in this case you need to make use of a midi translator to convert the pedal message to something 'useful'.

http://www.bome.com/midi/translator/
http://homepage.mac.com/nicowald/SubtleSoft/

Best,
Michael
Ableton HQ

[n13]

Thx for the info. Tried to do it with midipipe. But no luck in understanding. Anyone can help? What are the settings in midipipe to invert the polarity of a footswitch on midi message cc64?

Thx!!
Andre.

[[mid]]

Hi,

check which exact message you get by using a midi monitor (http://www.snoize.com/MIDIMonitor/).

Then try to invert the message so that you get a CC, velocity 127 (press pedal) , velocity 0 (release pedal).

... hope that helps.


Best,
Michael
Ableton HQ

[sdmiddleton]

Hi,

check which exact message you get by using a midi monitor (http://www.snoize.com/MIDIMonitor/).

Then try to invert the message so that you get a CC, velocity 127 (press pedal) , velocity 0 (release pedal).

... hope that helps.


Best,
Michael
Ableton HQ

Hi Thanks for this, Midi Monitor is Great and very useful, and i have installed MidiPipe ok, but get as far as selecting the message converter option but then have no idea what to change on the 'In' side of the screen or the 'Out' side... same as N13, Have you got any ideas on this also???

[[mid]]

Hi,

what is the message you get in from the pedal? What did the MidiMonitor spit out?

Best,
Michael
Ableton HQ

[sdmiddleton]

Hi,

what is the message you get in from the pedal? What did the MidiMonitor spit out?

Best,
Michael
Ableton HQ

Hi, i'm away from home till tonight but pretty sure it was the exact inversion of what you said it needed TO be, the first press was Velocity 0, then unpress was Velocity 127. on CC channel 64...

[n13]

Hey friends,

midipipe does the work. use the following setup:
midi input: apc40
control split: cc64 invert
midi out: midipipe out 1 (passthrough)

then in live use midipipe out 1

unfortunately I didn´t get this to work with my nativeKontrol (apC-CL1 preset) and just bought a super simple switchable sustain pedal. Now this works beautiful.

Conclusion: loopers misbehaviour is related to the footswitch polarity. It only works with:
pedal not pressed: cc64=0
pedal pressed: cc64=127

Hope that helps.
Andre.

[bagginz]

I must say I'm a little disappointed by the lack of flexibility/configurability with the footswitch sockets on the APC40.

It's essentially two holes which works with some footswsitches but not with others.

By contrast the Behringer BCR2000 automatically recognizes the switch polarity and adjusts accordingly. It also automatically recognises a stereo jack as a dual footswitch, as well as being 3 way programmable ( toggle on / toggle off / increment )

Are there any plans to make the footswitch sockets on the APC programmable or auto recognize the footswitch's polarity?

It would be very useful if we could configure at least the polarity of the APC40 footswitches without adding 3rd party software bodges.

bagginz

[sdmiddleton]

Hey friends,

midipipe does the work. use the following setup:
midi input: apc40
control split: cc64 invert
midi out: midipipe out 1 (passthrough)

then in live use midipipe out 1

unfortunately I didn´t get this to work with my nativeKontrol (apC-CL1 preset) and just bought a super simple switchable sustain pedal. Now this works beautiful.

Conclusion: loopers misbehaviour is related to the footswitch polarity. It only works with:
pedal not pressed: cc64=0
pedal pressed: cc64=127

Hope that helps.
Andre.

Thanks mate, i'll try this tonight, its control split is it! Ah, that was where i was getting confused, i was hacking about with message converter etc...I'll let you know how i get on! Cheers Buddy!

[kfoo]

I tried various settings now and still have the same problem. Looper automatically switches to playback a few beats later after i hit the footswitch to record something (footswitch assigned to big button).

My setup:

Behringer BCR 2000 + some cheap dual footswitch (no name).

The BCR allows various settings for the footswitch. I tried CC# and Note (always toggle mode off). The only useful setting seems to me, to use the footswitch as a CC# with maximum and minimum valuse 127, because when i hit the switch once it sends the minimum value and with the second click it sends the maximum value.
The problem with that is: Live seems to expect a 0 value immediately following the maximum value, i.e. when i use a normal push-button of my BCR it works fine. If i use the footswitch (wich doesn't send a 0 value after i hit it) the Looper records a while and then goes back to playback after a few beats.

You can try this if you assign a note (keyboard key) to the big button. If you recorded something and the looper is on playback, press the key to record something new into the looper. This behaves normally. Now do the same (in playback mode) again, but this time keep the key pressed! After a few beats the Looper will stop recording, because it didn't receive the note off message.

My question to Ableton-Support: is this really necessary? I don't see the point in expecting the note-off/zero-CC-value to function normally. I don't know if my BCR is just a bad controller and its footswitch settings suck (i mean a push button in non-toggle-mode sends a zero immediately after i pushed it), but i if that's normal footswitch behaviour it would recommend to change the Live settings because using the Big Button with a footswitch is essential. I don't want to press my foot switch twice just to record something.

[ovorigin]

so many posts from so long ago about looper not working and then nothing. I guess they like me got sick of getting nowhere with it.

I too have done the whole round trip and arrived at abletons looper sucks no matter what you do.

Ive even tried using an external keyboard as a foot switch and that did improve things but its still unusably unreliable.

lift your game ableton, its been nearly a year now

[Paul440]

Hi,
I have been having similar problems with specific equipment and thought I would report my findings here so others can learn - if they have the same equipment (am using Live 8.1.3). My findings dont add anything new, but confirm the exact problems and provide details on how to remedy on a Novation Remote LE keyboard with a cheapie sustain pedal.

Below are some key quotes from this thread - all of which were relevant to my situation.

"the looper bars turn orange (i.e. overdub mode) but then randomly switches back to playback mode halfway through the loop"
"the first press was Velocity 0, then unpress was Velocity 127. on CC channel 64..."
"If i use the footswitch (wich doesn't send a 0 value after i hit it) the Looper records a while and then goes back to playback after a few beats"
"I don't see the point in expecting the note-off/zero-CC-value to function normally"

By default I found all the LE's templates were setup in the following way in relation to the sustain pedal:
Type = Normal
Value = 0

Now this means that when the sustain is pressed a midi value of 0 is sent and when its released nothing happens. This then lands you in the exact random behaviour as per the quotes above.

I needed to do two things specific to the LE to get around this.

1) Change the Type from 'Normal' to 'Momentary'. This now causes the pedal to send 0 when pressed and 127 when released.
2) Invert the range, so that it sends 127 when pressed and 0 when released.
Bingo - it now works perfectly!

These are easily acomplished on the LE itself or via the easy to use editing software that comes with it.

As per other posters I am perplexed as to why Looper freaks out if it doesnt get the equivalent of the 'release' midi data. But if it doesnt it will randomly go back to play while it should be in overdub.