What do you do when resampling?

[dansheep13]

What do you do when you resample a riff over and over again until you get a wicked sound and that gives rise to some serious inspiration. You then get an idea of a wicked riff that would go well with it, but by this time most of the resampling stages and midi parts have been deleted to save cpu. What do you do when/if this happens?
What if this riff is too complex to simply repitch the sample and manipulate it into place?

[Turnipish_Thoughts]

It's situational. try your best to squeeze the riff out of it through a number of different approaches.

In future don't delete any stage of the development process, keep EVERYTHING offline but saved for exactly this reason. It's a common thing in any kind of digital production called 'non-destructive'. In other words, never delete anything. In visual shit, use masks, not the eraser. In music, never delete anything, just offline and hide e.t.c.

Midi files sitting in a DAW take up absolutely no CPU, same goes for bounced Audio and offlined FX chains. I don't see why you would actually delete them 'to save CPU'.

take it as a lesson i guess.

[dbaxx]

before you delete the deeply resampled riff you DEFINITELY stop and 'save as' (trackname version #) so you can avoid this kind of mess.

also, if youre using massive, throw a bunch of crazy different automations into the performer, like 16-32 bars worth, then you have PLENTY of shit to dig through for riffs etc and you wont have to worry about going back

[lowpass]

By nature I'm a very perfectionist ocd type person. So when it comes to songs the thought of bouncing something down and not being able to make changes was a really difficult thing to move on to (seriously)

In the end it comes down to gut instant, get the sound how you want it, get it bounced and get tweaking without looking back. If it messes up then start again and you can bet you are gonna be doing it a helluva lot better next time round