Impulse as REX player (.zip file inside)

mosca · Post by **mosca** » Mon Aug 01, 2005 12:00 am

So i was messing about with a drum loop and then did the following...

1. Sliced the audio up in SF
2. Loaded the slices into Impulse
3. Wrote 4 variations (Pattern 1 is the original loop, 2,3 & 4 are variations)
4. Did some follow action madness (FA1 -FA4)

here are the results - not perfect but it's a start

Impulse test zip file

i should add that its a 170Bpm drum and bass loop that i used

mosca

mosca · Post by **mosca** » Mon Aug 01, 2005 12:10 am

you can add a beatrepeat for more madness of course

mosca

Michael-SW · Post by **Michael-SW** » Mon Aug 01, 2005 12:28 am

Just a tip:

No need to go to SF to slice. Just slice the beat in arrangement view, consolidate each clip and then drag and drop each part into an Impulse slot.

(I really like to use arrangement view as a "workbench". Slice, reorder, consolidate, render if you spread out your slices over multiple channels etc)

helixx · Post by **helixx** » Mon Aug 01, 2005 12:30 am

great idea michael.

mosca, what's sf?

mosca · Post by **mosca** » Mon Aug 01, 2005 12:32 am

Michael - good idea - i'll try that (until they fix the impulse bug)

Helixx - Sound Forge (PC audio editor)

mosca

astar · Post by **astar** » Mon Aug 01, 2005 12:38 am

it'd be nice if there was an option to automatically slice a clip into 1/16 note sections and then drag em all at once into impuslse.. that'd be beautiful

nebulae · Post by **nebulae** » Mon Aug 01, 2005 2:39 am

Michael-SW wrote:Just a tip:

No need to go to SF to slice. Just slice the beat in arrangement view, consolidate each clip and then drag and drop each part into an Impulse slot.

(I really like to use arrangement view as a "workbench". Slice, reorder, consolidate, render if you spread out your slices over multiple channels etc)

This is a great method. Just wanted to confirm - when I learned about this, the step to consolidate wasn't necessary...Impulse should be able to read regions. Am i wrong on this?

mosca · Post by **mosca** » Mon Aug 01, 2005 2:42 am

It does - but it adds an artefact to the end of the slice

the Abe's know about this bug and hopefully we should see a fix sometime soon (then no need for Sound Forge)

m

Per Boysen · Post by **Per Boysen** » Mon Aug 01, 2005 9:34 am

Guys, what a great trick!!!!

zekrab · Post by **zekrab** » Mon Aug 01, 2005 9:37 am

Michael-SW wrote:Just slice the beat in arrangement view, consolidate each clip and then drag and drop each part into an Impulse slot.

I don't think you even need to consolidate, set your slice in the clip, drag it in impulse, adjust start and end time in impulse...

Emissary · Post by **Emissary** » Mon Aug 01, 2005 10:08 am

even easier , just get a sample , adjust the loop points in the clip view and then drop it in,

TrackTeam Audio · Post by **TrackTeam Audio** » Mon Aug 01, 2005 11:44 am

Our Beatbox and Travelbox LiveFill collections feature this as what we call "Slice Kits". This technique is a great way to get a lot of extra mileage out of your drum loops. Check ours out when you have time, the Travelbox ones are especially interesting as they are made from ethnic percussion loops. Fun stuff.

TrackTeam

Michael-SW · Post by **Michael-SW** » Mon Aug 01, 2005 11:48 am

You don't need to consolidate to use the sample in an Impulse slot.

Machinate · Post by **Machinate** » Mon Aug 01, 2005 11:56 am

Yeah, I've heard of ... other... people doing that to their drum loops...

I don't know if the trackteam dudes can elaborate on this, but there is an easy workaround to the impulse bug... by my measurements the impulse leaves 29.5ms too much of the sample in there*. So just adjust by that amount and your edits will be spotless.

*: This has only been measured on one (1) sample, so this does not take into account any possible differences when using other samples.

mosca · Post by **mosca** » Mon Aug 01, 2005 12:04 pm

Ableton should fix the impulse bug soon

i posted about it in the beta forum a while back and they acknowledged it's exsistance but said it would be unlikely to be fixed for Live 5 release

maybe in Live 5.1

mosca