Bounce in place - M+

I'm trying to figure out the difference between the bounce-in-place feature implemented in the latest M+ update and resampling the old-fashioned way. Is the result the same, or am I wrong? Can someone more knowledgeable explain the possible differences and/or conveniences of the much-vaunted bounce feature? Thanks a lot.

Find more posts tagged with

Maschine Plus

Comments

PK The DJ

The manuals have not been updated yet (probably it will be "soon" 😁) but there's a little bit of info HERE

Carosone

Thanks, but it doesn't add much, in the sense that apart from replacing and doing it with a single operation, the result is the same as an internal resampling, right?

LostInFoundation

https://community.native-instruments.com/discussion/comment/239720#Comment_239720

We had that discussion somewhere else and the guy who asked the question was also not completely convinced by the answers.

At one point I wrote this and it seemed to click with him a little more. Maybe it can be useful also for you:

”Let's put it like this:
I want to resample a short extract (5-10 sec) and have all the components as a single wav file? I'll probably continue with the old resample method.
I want to render a full arrangement (3-5 min) in multiple wav files just to avoid the CPU to be taxed? Probably the new bounce in place can be useful.
To do the same thing with resample, you should "manually" record every single pad, waiting for the whole duration to be "live played" and recorded, maybe 16x times if all Sounds contain material. Let's say 16x 5 min... quite an amount of time... And that only bouncing one single Group. As already said, M+ can't access the drag and drop functionality.
The 2 functions can serve different use cases. This is why I think it can be positive to have both choices”

Carosone

Clear! thank's

LostInFoundation

https://community.native-instruments.com/discussion/comment/240136#Comment_240136

You’re very welcome 👍🏼

Quick links

Unanswered questions