I have a simple problem: I want to record on my OT long loops of guitar chords (more than 64 steps), or other real instruments, without using a pedal, with the click or some arrangements (so without the OT change the tempo at the end of the loop), and then use them to jam and to produce full songs.
I’ve read lot of topics, and the manual, but I can’t figure how to do that without editing.
To resume clearly: I want to trig 128 or 256 steps recordings that will stop and then playback automatically at the end. I don’t really care using pickup or flex machines.
Yes maybe the 1024 steps possibility is my number one feature request. 512 if limited to 3 digits, or maybe at least the possibility to use track scale…which is not respected by RLEN. Track scale 1/8 would make 512 steps.
@Open_Mike uses longer recordings for guitar a lot, with REC SETUP 2 > QREC (start / stop quantize to pattern length, or 1 / 2 / 4 / 8 /… /128 /256 steps) and buttons presses AFAIK. Maybe he can give you more advices about his method. IIRC he uses 64, 128 or 256 steps quantize.
If QREC is set to 64, you can start recording beginning with a one shot trig, and quantize end when you press rec buttons, so you can record 64 /128 / 192 /256 etc length.
With guitar I’d personally prefer a midi foot controller for longer recordings, using qrec too, with a defined length preferably.
You can also use a midi track to send a midi note that stops recording at the right length, preferably with QREC. You have to plug a midi cable between midi in and out, use the right midi channel to control the recorder.
Never tried, but theorically even with a 1 bar pattern you can record up to 1024 steps with that method, sending a rec note once (1st Trig Condition), that would be quantized…
You can also use Arranger with pattern that stops recording with a midi note.
Yes, it is my number one bugbear that we have to jump through so many hoops to record long samples for use as static files, I sent it in on a feature request again a few months back, the Elektron guy who replied said that he agreed it would make sense, so we can live in hope.
To be able to record stems in the record setup by setting RLEN to precise bar/beat multiples beyond 64 steps would add so much functionality, both for live set preparations but also for studio production.
Obviously as we all know the memory constraints might render some RLEN values impossible, so some reference to the memory reserve would have to be used to govern the maximum displayed value in RLEN, I’d personally like more than 64 bars (1024 steps) as a maximum, 128 bars would be nice, and still leave some room for flex samples in the memory.
Failing this being implemented even if the HALT command in the arranger could stop recording then we could more easily record long samples by use of one shot record, I’d be happy with that but ideally it would be nice to have both options.
Yep, game changer. And, since OS 1.30X, the fact that there’s a new bug to stop recordings started with one shot rec trigs don’t help : you have to press rec buttons twice to stop the recording! Too anxiogenic to use in live conditions, errors risk.
While playing guitar I just quickly reach over and press the button during the last pattern cycle of the loop while holding a note or whatever I got to do, using one2 mode usually with qrec : 64…
Somehow these types of things don’t bother me, I’m willing to adapt my playing for ease of working with the machines… One day I’ll get a midi foot pedal and I’m sure it’ll be great but for now I don’t seem to mind, I’ll certainly +1 the higher rlen request though.
Thanks for responding @olle what about the HALT issue? As it is at present we can use a 1 shot record trig to start recording, and transport STOP to stop recording, unfortunately though HALT in arranger does not stop record buffer, however if it could then making long automatic length recordings would be a lot simpler. Just put a 1 shot rec containing pattern in row 1 of arranger set REP to desired length then on row 2 put HALT command, provided the rec settings and buffer allocations are set up appropriately then effectively we’d have the same idea as being requested but possibly in a much simpler to implement way from a code perspective?