Start/stop record selected clip from pedal? Overdub audio?

[cinematree]

1. Is it possible to assign a sustain pedal to trigger record on/off for a highlighted clip? (I understand how to assign a specific pedal to a specific clip, but I am hoping there is a way to assign one midi controller note to trigger recording on and off for the selected clip. So if, for example, I'm recording electric guitar into a clip and want my hands free, I can hit a pedal to start and stop recording the clip for any selected clip. Is that possible?

2. Also, it it possible to overdub audio? if not, it would be awesome if overdub worked for audio as well (like the way a looper works such as the program Mobius). Any plans to add that feature?

3. Say I want to use Live without a grid (like say I want to record a solo guitar piece without a grid but do it in different clips). I know I can record clips "wild" by setting global quantize to "none" while recording them. Is there a way to play back the clips in a track in order so that each clip starts playing right when the previous clip has been completed? To clarify, the clips are not to a click and so they end at places that are off the grid, so it doesn't work to assign how many bars to play the previous clip for.

[3dot...]

nope. audio clips don't overdub.
you use "looper" device for that.
assign the sustain pedal to the big button.
read up on it in the manual..

[cinematree]

The Big button is cool to have in the Looper, but I'd prefer to be able to start recording/end recording on any clip selected in the main Live Clip Window, without having to use the looper. Any one know how to do this?

And do you 3dot..., or any one else know the answer to #3 above?

[bartend7]

i was looking into something similar and found this on gearslutz

http://www.gearslutz.com/board/music-co ... -slot.html

[cinematree]

Thanks Bartend7 - I've done it that way, but that means that each time you want to stop recording a clip, the one below starts recording.

ShelLuser - thanks for the tip. I downloaded the demo of Max for Live and it seems awesome. I was able to play around with the demos and I found how to route midi into Max for live and how to make the "Fire Selected Scene/Clip" options and have them hooked up to the midi input. But I don't know now how to connect that "Fire Selected Clip" object to Live (if I could download some examples of controller Max for Live scripts, I could probably figure it out but the maxforlive.com seems to be down currently. Could you point me in the write direction?

Once I have that "Fire Selected Scene" object firing, how do I integrate that into Live?

And as for figuring out question 3 with Max for LIve, that seems daunting.

Thank you again for your help.

[wiffbi]

Without M4L you could also look at Selected Track Control. Under Session Control it offers a "Fire selected clip" – which is bound as default to Note #43, but can be customized to react to your foot pedal (usually CC 64) by editing settings.py inside the MIDI Remote Script.
http://stc.wiffbi.com/midi-implementati ... on-Control

+ On the plus side: it is automatically mapped in every Live Set.
- Drawbacks: 1. you need to edit a python file. 2. You have to bind the MIDI keyboard/controller, which your foot pedal is connected to, to the STC MIDI Control Surface Script, which makes it impossible to use another MIDI Remote Script with that controller. So if you e.g. have an APC40 and want to add that functionality to your foot pedal, then better use that M4L-device, because AFAIK there can only be one MIDI Remote Script bound to a device.

[bartend7]

Thanks Bartend7 - I've done it that way, but that means that each time you want to stop recording a clip, the one below starts recording.

if you turn "select next scene on launch" off in the preferences, and turn "start recording on scene launch" on, Live will record all enabled tracks in that scene and not jump to the next scene.

[cinematree]

Thank you for your replies.

ShelLuser. - that was very generous of you to share that script. It works, but for some reason, I have to hit my midi trigger a bunch of times before it triggers start or stop of the selected clip. Any idea what might be causing that?

Wiffbi - thank you for directing me to Selected Track Control. Triggering clip launch works perfectly with the keystroke (option plus return), but when I set up a midi note (G3 at 127), it doesn't do anything. I think I've got it all set up correctly in Live's midi preferences. Is there anything special I have to do to get midi commands to be seen by the STC script? Also, for some reason tracks aren't arming when I select them - it says that STC should do that. Any ideas? Also, if i can get the midi working, do you know where in the scripts I can change which midi note triggers the selected clip launch?

Bartend7- thank you. I just would prefer be able to jump to any clip slot with my Ipad and then hit a pedal to fire that clip slot.

[cinematree]

ShelLuser, when I click on that link and then try pasting the text into MAX MSP, nothing happens - MAXMSP won't accept it. When I go back to the code you posted above and paste that, it works fine and goes right in. Can you please post the text from the link directly on the forum here (or let me know if you have any other ideas of why it's not working)? I also tried putting it into Textedit and making it "plain text" but MAX MSP still won't accept it.

Many thanks.

[wiffbi]

Wiffbi - thank you for directing me to Selected Track Control. Triggering clip launch works perfectly with the keystroke (option plus return), but when I set up a midi note (G3 at 127), it doesn't do anything. I think I've got it all set up correctly in Live's midi preferences. Is there anything special I have to do to get midi commands to be seen by the STC script? Also, for some reason tracks aren't arming when I select them - it says that STC should do that. Any ideas? Also, if i can get the midi working, do you know where in the scripts I can change which midi note triggers the selected clip launch?

Hey, for STC to react to your MIDI controller, you have to select the MIDI In from your MIDI controller in preferences under the Control Surface section for STC.
The auto-arm feature only works if you select "STC Virtual Out" under the MIDI Output port in preferences under Control Surfaces. I have not updated the documentation yet -sorry! I will double check when I am back at the computer, currently I am smartphone only.
To customize STC you need to edit settings.py - this is a Python script, so if you know some Python it should not be to hard. There is also some documentation at the top of settings.py. At some point I'd like to have some webform where you can customize STC to your liking but currently editing settings.py is the only way. Or let me know, what notes/cc you want to be mapped and I change settings.py for you.

[cinematree]

Wiffbi - thank you. (by the way, I didn't realize that you were the creator of STC - I posted the same questions in the STC thread - sorry for the redundancy). STC is incredibly useful to me. Thanks so much. I figured out how to assign other midi numbers using the settings.py. And I've got the auto-arm feature working - awesome. I notice sometimes that when I hit "stop" (either remotely or with the mouse), playback doesn't stop and just starts again from zero. Is that a bug in Live? Or something that STC is doing? Or a preference I'm missing somewhere?

ShelLuser - thanks for the clarification. I didn't understand to "right-click and save the linked file". I was able to install it but the behavior was the same as the other script - it takes 2-4 clicks to get it to register for some reason.

[wiffbi]

@cinematree: no prob re. redundancy and sorry for my shameless, not-attributed self-promotion …

I am glad you like STC and found your way around the settings.py! Regarding your playback/stop-problems: to me this does not sound like STC is causing that behaviour, especially since you can produce that error with clicking with your mouse – STC does not react to clicks nor does it listen to any start/stop-behaviour in Live. But to make really sure, have you tried to deactivate STC and see if your problem still exists?

[cinematree]

No problem for the non-attributed self-promotion. Humility is a good thing and it was very helpful to me.

I did try disabling STC and the problem was still there - i just didn't know if by installing scripts it alters anything about Live's coding, but i understand from your reply that it does not.

When using Live yesterday, I thought of a feature that would be hugely helpful and that maybe STC could implement - in the same assignment as "Fire selected clip", could there be another option that if you hold down a controller for a given interval (say like 1 second), the selected clip is undone/deleted? I use a looper called Mobius and someone developed a script called "Luiloops" which has this feature - one click does record/overdub, a double-click does multiply, and a long press deletes. Is that a possibility for a future update? Or do you know a program that currently implements this?

[wiffbi]

Okay, good for me to hear that your problem is not STC-related. But I am sorry, that the problem still persits for you.

Regarding "Delete Clip": that is a great idea and I actually experimented with timed commands (press and hold) with another MIDI Remote Script I am working on. The problem is though: Live’s API does not allow to delete a clip. You could try some software that translates MIDI into keystrokes (on Mac OS X there is midiStroke) and map your controller to "DELETE". Beware though what has focus in Live’s GUI! E.g. if you launch a scene, Live selects the whole scene – so if you now press DELETE it will delete the whole scene! So currently, delete is not an especially safe operation other than through the GUI …

[3dot...]

you can use 'clyphx' to delete specific slots..
better than nothing...

I can think of another method involving Bomes' MIDI translator..
where you can make sure that it's not gonna delete anything other than the chosen clip..