Device Details

Device Overview

Name/Version: BiP - bounce in place 1.2
Author: Crampe  
Description: Everyone's waiting for a "bounce in place" feature in Ableton Live since ages.

Here's the one-click-only solution device, with easy Push implementation.

Place the device on your master track (you can put it anywhere actually), key/midi map its single button, save it in your default template and your done!

When you want to bounce something, just place your playhead on the desired track and press you key/midi mapped button - or Select+Rec on Push - done!

Also works with multiple tracks (just solo every desired tracks).

Automatic naming : your new bounced audio file will conveniently be named "[rsmpl] name-of-the-recorded-track".

NEW IN V1.2:



NEW IN V1.1:



Ableton Live 10 minimum.

Video demo here:

Device Details

Tags utility, push
Live Version Used: 10.0.1
Max Version Used: 8
Date Added: Jun 07 2018 22:06:49
Date Last Updated: Jun 24 2018 15:46:07
Device Type: audio_device
Download URL (report link)
License (more info): Commercial


Love it! This device has quickly become my new favorite man.

The only issue I'm running into is that I've added this to my main template & every time I open up Ableton it seems like the device is automatically getting activated somehow as it immediately starts to do it BIP thing. However, it doesn't solo & rename the track tho like it does during normal use.

I'm on Live v10.0.2 (2018-05-11_f78673c6cd) on Mac OS X 10.13.5 (17F77)

Hey Broah,
I could look at the device initialisation and timing things, but I've never experienced this and you're the first and only reporting this.
Do you have any other M4L device that could interact with in your template?

I do have a number of other Max devices. Let me re-save the template with each one deleted one by one and I'll try to identify the culprit. I'll report back.

Is there a way I can open up Max and see what device may be causing it? I have a number of Max devices in my template and doing this one-by-one would be really time consuming.

OK, so that didn't take as long as I thought it would. I deleted every Max device I had in my project and left only the BiP device and re-saved the template. Same behavior happened tho. :/

I Initially thought it was the Futility 2 device (which I had forgotten was also yours btw!), but it wasn't that device causing the issue.

After leaving only the BiP device and having it still happen I think it's safe to say this is what's causing it. Also, I don't think there'd be any other device that could create a new track, set it to Resample mode and click the Arrangement Record Button.

OK, so I went one step further and made a brand new template with only one MIDI track with a drum and a 2 bar pattern and BiP on the master, but it is doing the same thing when I either open open Ableton for the first time or just create a new project with cmd+n

Alright, upon further testing I seemed to have figured *something* out. I had key-mapped Shift+B to the resample button & Shift+N to the Post-FX button. I deleted both key-mappings, deleted the device completely from my machine and re-downloaded from Gumroad, then re-mapped resample button to alt+z and Post-FX button to alt+x and everything seems to be working wonderfully.

Not sure if it was the key-mapping causing the issue or if I just need to do a clean install of the device, but either way it is working now!

Ha ha, omg this is getting ridiculous. I actually just found the culprit device causing the issue. After my last post I re-added this device which I thought I had ruled out, but it immediately triggered the behavior after I re-saved my template and re-opened it.

It's called Arm-Me (MIDI version):

Think you can take a look at this and see if there is a work around? I use this to keep Cthulu armed so that I can have it ready to play.

Hey Broah,
I suppose having you Cthulu track monitoring set to On isn't an option?
Unfortunately I can't guarantee that this kind of interaction with other M4L devices won't happen.
I'll have a look though, but not in the upcoming days as I'm on a tight deadline.
For the time being I suppose you'll have to live with this annoying Live start up issue.
Coming back to you asap.

Right on, no worries. I'm sure I'll make do!

Couple of questions.

1. Is it possible to add a toggle box to either add / not add the "[rsmpl]" text in front of the new audio track? I've found my workflow is simply renaming it to what the source group / track was and then immediately deleting the source group / track afterwards. i.e. Group of 3 clap tracks in a group names "Claps" > BiP > new tracks named "Claps"

2. Would it be possible to auto-enable the Loop switch? Using BiP I've found my workflow to be 1.) Select the region. 2.) Toggle Punch-In & Punch-Out switches. 3.) trigger BiP. So, the resulting audio file is already the correct length, but then I just need to enable the Loop switch virtually every time. Speaking of, auto enabling / disabling the Punch-In/Out switches would also save a step.

Freaking LOVE this device already. Been using it literally non-stop. It saves so much time it's ridiculous.

Good idea about the punch in/out.
Yeah I probably could make the [rsmpl] optional.
Let's wait for the next update.

Right on!

I'm in live 10 - the device doesn't seem to solo the track with either button. Im just getting a full resample of the whole track. Any ideas?

Sorry, I haven't notice your message earlier. Is it solved for you?
Do you have exclusive solo activated in your preferences?

your device is essential for electronic/experimental music, thank you!!

Just a question/request: is it possible to implement a "MIDI bounce" feature? the two "O" are for audio and maybe the "I" for the MIDI.
I keep thinking about it because with arps and complex sequencers I need to route MIDI everytime if I want to save a sequence and keep experimenting, or simply to duplicate for another layer and modify it.
Mapping a button could be veeeery handy!

Any chance?
Thank you

Bug: resampling starts on load! As soon as I open a saved project it starts resampling all tracks.
I don't know if it is related to the bug on your other device Futility II that turns on muted tracks when I reopen a project.....

More testing: if I save the project with the device deactivated, there is no resampling on load. But as soon as I reactivate the device the resampling starts even if I don't do anything else.
FYI: the two buttons are mapped to keyboard's keys.

Yeah, this is an issue with computer keyboard mapping and the way the live.button behaves. I have to patch something to hack this behaviour.

Login to comment on this device.

[ browse device library ]