Looper Help please - a video tutorial anyone????

[chris vine]

bummer

[bodhi71]

So really , what did I upgrade for?
A limiter, collision which hasn't done much for me, groove pool( don't use), doesn't mean it's not good,
APC+1, what really sold me was looper

[outershpongolia]

@pepezabala

The thing I found about polarity is that if it is reversed you will have to press the pedal and it will start recording when you release.. then you can press and hold and then RELEASE to have it loop.. I found this too be almost more accurate than just pressing it.. but I don't use looper...

[stevewhite99]

Some Looper foot pedal success to report...

I spend a very frustrating time last night trying to get Looper to work using a Boss FC-50 footpedal (running through midipipe on a mac). This pedal board works fine for all other remote assignments in Live, but in Looper it was displaying all the symptoms described previously in this thread - mainly not staying in overdub.

Eventually I tried an old sustain type switch pedal (unbranded) through the footswitch jack on an Oxygen 8 and this seems to work as intended. I also have a Bespeco VM-20 (same kind of pedal) and this also seems to work when controlling Looper's big button. The only function not really happening is the 2 second hold for 'Undo/Clear' although it does Clear from stopped. The Bespeco has a polarity switch and when set the 'wrong' way it does the dropping out of Overdub thing.

One thing I've learnt the hard way is to make sure your song is not playing when you want to record a first loop to set the tempo. If you do it once, undo and try again without stopping the song, Looper will force your recording to the existing tempo. Seems obvious now, but it confused me for a while (it was late and I was losing all hope).

[Ball Sack]

wtf

[shamburglar]

Ok,

So i just got the APC40...Good stuff. has a few problems of its own.. Device On/off not behaving, sometimes track control section doesn't match what it should, but thats another topic...

Thought the new APC would solve this looper issue though...There are 2 foot switch slots on the rear, one transmits over Channel 1 CC64 and the other 67...

A double click on the pedal to stop and erase whats been recorded now doesn't work...Also, when it records back a loop, its plays back the first time with lets say, 8 blocks of a 2 bar cycle...Then the next cycle it just has 1 solid block playing back over and over and just does whatever it pleases....sometimes overdubs, sometimes plays back previous stuff in the loopers memory..(didn't know it had a memory)...I've tried both Footswitch slots and 2 different pedals...

Man this is just all so weird, things just simply not working...I'm going crazy!!! Anyone had any trouble???

Cheers!!!

Yup... same problem with looper footpedal and APC... its not right!

[LesC]

After much toiling I discovered if use Bome's Midi Translator to translate the footpedal to a Key Command instead of a MIDI message that it works fine. Dont know if this will work for all. I'm using Digitech Control 8, in Patch Change mode, translating the patch change message to a key command (the letter "L") which is mapped to the big button in Looper.

[chris vine]

Here is another update:

The multi function button started to play up yesterday - I am using an FCB1010 - anyway, I decided to assign pedals (midi notes) to the separate transport function buttons in Looper, and hmmmmm, transport problems went away..........

[sdmiddleton]

I'm really wondering if this will ever be addressed?

This was a quote in one of the forums about another fault.

Doesn't make a damn bit of difference how well it runs on my machine (and it does run well), running well on your machine is all that matters as far as you should be concerned. If it's crashed 3 times, you've got a problem and shouldn't plan on playing it out yet.

No disregard, but sorry, wrong.

Obviously Live 7 should only be his last fallback solution and what he should do now (as always) is reporting his problems to the support so that we can start finding a solution for him rocking the crowd using Live 8 - we're pretty good at this.
If he doesn't, chances are big that his particular problem, regardless of what is actually causing it, will exist for a long time.

This becomes more important after every single bugfix update as the remaining problems are more and more related to really special combinations of setup, usecase and workflow.

Cheers,
Dom

P.S.: and +1 to what TD just wrote, he sums it up pretty good.
For me it is always very sad to see that most of those who rant the most never wrote to support at all.

However this was my report to the support centre 5 weeks ago about this looper issue:

http://forum.ableton.com/viewtopic.php? ... 17&start=0

Can someone please let me know if i'm not reporting these bugs in the correct way because otherwise its hardly surprising people spend more time ranting than actually reporting bugs as its been 5 weeks without any acknowlegement and i don't feel we're getting our moneys worth so far.

Kind regards

S.

[mikemc]

I am curious and if I have a chance am going to try what you are trying, to see if the way I'm set up works the same.

I haven't had any problems using looper when it is set to follow the set's tempo, and I just happened to assign different pads (using a nanoPad) to the various transport functions, because I wanted to use them separately.

So your quantization is set to none, but your tempo control is what, and your bar # is what?

[edit] you set your tempo control to 'set and follow'. But not sure about your number of bars, you said 'variable length'. Is it "x"? And what it is set to do (overdub, play) after "x" bars?

[edit edit] a screen shot of your looper settings would be helpful, but I think you want to at least say what the above controls are set to, if not each and every control on the device is set to.

[mikemc]

here is what I did:

I used a Key map to map the "m" key to the big button.

Set looper to None quantization, x bars, and set and follow tempo.

Put an impulse into an adjacent track, and used the computer keyboard to hit quarter notes, with the audio routed into the looper.

Hit the 'm' key to start looper simultaneously with the first beat.

Hit the 'm' key again after 4 beats.

My timing was a little off, but it worked, went into overdub mode and stayed there, looping the 4 quarter notes at the tempo they were played.

The reason I used the computer keyboard was to eliminate device-related variables. Next I will try this with a midi switch sending notes, and if it works I will make a video.

[Kearley]

I'm with you guys on this... I can't seem to get the Looper under control.

I'm experimenting with an APC with footswitch, a sustain pedal on my RemoteSL, AND a Behringer Footpedal.
Right now, I don't thing anything is behaving as expected.

D

[Lazos]

I'm using 8.04 and have been able to loop various stringed instruments fine, even different beats and rimshots and things on a floor tom that I have. It all works fine (even in odd meters). But I'm sure it's seriously frustrating for folks that are experiencing problems with Looper.

I did notice awhile back that the multi-function pedal assignment on Looper likes midi notes and not midi control commands from my FCB 1010.

[Kearley]

That's interesting Lazos.. I wonder what the footswitches on the APC send out... I'll check if they are controllers, or notes.

D

[chris vine]

Hi Lazos,
I am pretty sure my FCB is sending midi notes. Glad it is working for you. Strange how inconsistent it seems to be in general though.

I have to admit that the pedals on the FCB do suck, IMO, in terms of action - maybe I need bigger boots?