Pressing the record button will record a new clip

[chapelier fou]

my last comment was in response to garyboozy.

That's so weird. Not related to M4L and im using the regular script. Thanks for trying to reproduce...

[siliconarc]

i know what you mean now, chap! can reproduce this here.
i assumed you meant that existing clips were being wiped and overwritten, hence i couldn't reproduce.

i just switched the "start transport with record" option off and can see what you mean now - the Push clip record button doesn't do the same as a mouse-click on the circle (circle stays lit but doesn't record).

thing is, like valium, i can't remember why this option is useful:

I thought this could be related to the "start transport with record" option... Why was this option was implemented ? I can't remember

a much bigger problem with this multi-rec-armed Push and rec button setup is, when you press the Push record button, record a midi clip on one track, then move to a diff track and record another midi clip, the midi notes for the second clip are recorded into all previously recorded clips in the scene. would be disastrous on stage!

instead of using Push's record button, you could use the Session view and record clips directly from the pads, and Push becomes an expensive Launchpad. but if you use the pads to records drums too, then you're having to switch between Note and Session mode while juggling your other instruments. not cool.

so you could just drop the 'multi-armed tracks' workflow and use Push's auto-arm (track-arm button turns pink) and switch tracks using either Push's arrow buttons or the track selector buttons on the Track page. again, its still awkward.

grow more hands?

[chapelier fou]

'behavior' confirmed by ableton.
No workaround.

[Valiumdupeuple]

Chapelier, this is how your setup looks like, right ?

[sporkles]

thing is, like valium, i can't remember why this option is useful:

I thought this could be related to the "start transport with record" option... Why was this option was implemented ? I can't remember

I don't see why people don't like this; I've completely integrated this in my workflow - in combination with count-in, of course. This frees up your hands in a way only a foot controller mapped to the play button could.

[Valiumdupeuple]

thing is, like valium, i can't remember why this option is useful:

I thought this could be related to the "start transport with record" option... Why was this option was implemented ? I can't remember

I don't see why people don't like this; I've completely integrated this in my workflow - in combination with count-in, of course. This frees up your hands in a way only a foot controller mapped to the play button could.

I didn't say I dislike it Sporkles, Garyboozy understood my words this way (maybe because of my approximative english), but it's not what I was saying. I was just asking for what, problematic, reason it was implemented. Because at that time I couldn't remember why, I just remember that it was a GOOD addition, actually.

[chapelier fou]

Chapelier, this is how your setup looks like, right ?

Yes, exactly.

[chapelier fou]

I don't see why people don't like this; I've completely integrated this in my workflow - in combination with count-in, of course. This frees up your hands in a way only a foot controller mapped to the play button could.

This is precisely because i am livelooping with a foot controller.
I don't have the time to arm another track or wait the count-in or whatever since i often record a loop straight after the other, as if i was directly overdubbing.

[Valiumdupeuple]

Chapelier, this is how your setup looks like, right ?

Yes, exactly.

Then, I can assure you, one more time, that it works with no problem for me, whatever the ableton support says.
I could make a video to demonstrate it, but would it change something ?
Does the problem also occur when you have only Push connected as a control surface ?
Talking about "foot live looping", when you say "the rec button on Push", you mean the actual rec button, not the footswitch input 2, right ?

[chapelier fou]

That's so weird, cause i got their confirmation... and you seem to get the problem without a doubt...
I will try disabling other control surfaces.
And yeah, i talk about the rec button on push, the red circle on top of the play sign.
i send you a pm.

[sporkles]

I don't see why people don't like this; I've completely integrated this in my workflow - in combination with count-in, of course. This frees up your hands in a way only a foot controller mapped to the play button could.

This is precisely because i am livelooping with a foot controller.
I don't have the time to arm another track or wait the count-in or whatever since i often record a loop straight after the other, as if i was directly overdubbing.

I see; I can indeed understand your frustration if switching this option off doesn't work as you'd expect.

[chapelier fou]

After a few tests i need to correct some stuff i said.
It doesn't record clips in every armed tracks.

Two scenarios :

A/ With "start transport on recording" DISABLED

CLICKING on session rec :
It will enable overdub in MIDI tracks and do nothing in Audio Track. (This is the behavior i need)

USING PUSH :
It will act the same EXCEPT that it will record a clip in the highlighted clip slot if the highlighted clip slot is armed and empty. (I absolutely need to avoid this)

B/ With "start transport on recording" ENABLED

CLICKING on session rec :
It will sometimes record clips in each armed track. Sometimes not. It seems just chaotic. Maybe some rule but i just don't get it.

USING PUSH :
It will act the same EXCEPT that it will record a clip in the highlighted clip slot if the highlighted clip slot is armed and empty. (Same behavior as above)


CONCLUSIONS :
- Push ignores the preferences settings
- The native behavior, using the GUI, is just weird
- The Push's behavior is not suitable for my use (it's just dangerous)