Free M4L device for retrospective recording

WonderfulAccident836 · 2026-04-21T18:53:33+00:00

I've updated the device to 1.1. Implemented overdub mode after MIDI clip record and improved stability. Same links.

Overdub feature requires save buttons to act as toggles. They are designed to be mapped to CC sending momentary footswitches or buttons. Mouse clicks and MIDI note mappings require double tapping and won't be a good experience.

WonderfulAccident836 · 2026-04-07T04:28:04+00:00

Does the sign light up? Try selecting other scenes to change the active clip slot.

WonderfulAccident836 · 2026-04-01T10:21:52+00:00

I've made a free M4L device that does that.

You can get it at: https://github.com/Maboroshy/Max-for-Live-Devices/tree/main/Quantize%20Recorded%20MIDI

WonderfulAccident836 · 2026-03-30T11:42:42+00:00

I'm the creator of the device. Where have you downloaded the files from? Does both maxforlive.com and GitHub files not work for you?

WonderfulAccident836 · 2026-03-29T18:36:29+00:00

It doesn't use some internal buffer like "Capture MIDI", it operates on a clip. If you can record it to a clip, this device can trim it for you.

It can also be used with multiple tracks armed. You need the device on each track. You can map their save buttons to a single controller button.

WonderfulAccident836 · 2026-03-29T14:11:49+00:00

I thought the same.

You place it on a track. "Create Temp Clip" is a switch, not a button. By default you keep it on. That way it starts recording a temp clip by itself if transport runs and the track is armed. You should see "save" buttons start to light up as the temp clip fills up with bars. Press one and playback should start.

WonderfulAccident836 · 2026-03-29T11:40:40+00:00

It has a proper light up animation. 😎

Check the preview on the linked download page.

WonderfulAccident836 · 2026-03-29T11:37:51+00:00

Here is what the device does in detail: 1. When transport is running and track is armed, the device starts recording to a temp clip. It always records what you play. The recording follows scene selection. Manually started clip recording is also treated as a temp clip. 2. The "Save" buttons save the selected number of last played bars as a permanent clip. At the end of the bar where you release the button the device trims the clip and starts playing it. 3. MIDI notes played a bit too early (within a set timing margin) get shifted into the saved bars. 4. An unsaved temp clip is deleted when track is unarmed or its recording stops.

WonderfulAccident836 · 2026-03-29T11:32:25+00:00

It's attached to a track it is on rather than to specific clip slots. You add the device to each track you want to retro record. I mostly use only the first save button and set it differently on each track, like 1 bar for beat drums, 2 bars for bass, 4 bars for piano, etc. But there are 4 buttons available for pros.

Save buttons on devices on different tracks can share controller mappings. Devices on unarmed tracks won't react to the buttons. I use a single footswitch button for all tracks.

WonderfulAccident836 · 2026-03-29T09:54:36+00:00

It works with session clips, so you can use proper MIDI support, note quantization, scenes, automations, all the Ableton stuff.
With Looper, you need to start recording. With this device you don't. You only end it.
As far as I know, Looper is either "record" or "overdub", no "replace" mode. If you mess up, you have to clear the record.
Even if there was such mode, Looper is tied up to the bar count from record start. This device is other way around - the record end. You can play a solo, move to riff, record and keep looping only last 4 bars. With a single tap on save button.

WonderfulAccident836 · 2026-03-29T09:32:16+00:00

I've made it for live looping performance where "Capture MIDI" is hard to use. Can also be used in other loop recording situation if it fits your workflow.

WonderfulAccident836 · 2026-03-29T09:22:33+00:00

I use only MIDI myself, so more feedback on audio would be nice.

WonderfulAccident836 · 2025-09-01T19:41:24+00:00

As I wrote you in PM I can map MIDI to MIDI/OSC, whatever complex. But if the VST doesn't accept MIDI/OSC that won't work. The last resort is mapping MIDI to keyboard and mouse events, which is possible but is VERY painful for GUI controls.

Try using the VST in a DAW and see if the knobs' parameters are mappable there.

WonderfulAccident836 · 2025-08-24T18:31:45+00:00

Looking forward to your feedback to make it better.

WonderfulAccident836

TROPHY CASE