404 slicer - what does it cut to?

[1_inch_punch]

Hi -

to cut a sample to pieces in time to your bpm -

will the slicer automatically cut to the pattern bpm set or -

does it divide the sample into divisions proportional to the sample length(?)

eg - to divide a sample in time to 90 bpm -

- does the sample have to be cut to exactly a single measure 90 bpm length - (i think this is the case(?)

or does the slicer cut to whatever the pattern bpm is set to?

thanks for any advice

[Dr Van Nostrand]

think its based off of the bpm when a pattern isn't playing but i'm not totally sure, but if you got a pattern playing and have the slicer on then its gonna slice to whatever the bpm of the pattern is

[wax inspektor]

if you play a pattern it syncs to the bpm of the pattern... if no pattern plays, it's the samples bpm... if you want to resample with a slicer on a sample but the sample bpm and pattern bpm don't match try this good ol trick: *replace 'delay' with 'slicer'

Also, the 404 applies the effect rhythm based on the highest BPM value when applied to multiple pads. So you want to run a pattern at 92 BPM, and let's say your drum loop is also 92 BPM, but you have a one-shot that's only 62 BPM. You want to resample the one-shot with delay at 92 BPM, so you simply apply the effect to your one-shot and the drum loop, even though you're not going to hit the drumloop pad. When you resample the one shot, the delay will be applied at 92 BPM, because the 404 can't run two separate delay times simultaneously. It defaults to the higher BPM. This is also the same way to set correct rhythmic timing on external sources.

And if your one-shot (or whatever) happens to be of higher BPM value than a pad with the correct timing, you simply change 62 BPM to 124 or 31 BPM so that it's count is less than the BPM you want. You'll have to adjust your delay settings though, since an old eighth beat will now be a quarter beat.

Genius. We should start collecting those major tricks in the SPI.

[kel]

^^^^this is why when i try to resample a pad with a slicer or delay, i usually can't get the resampled sound to match the tempo of the pattern? the tempo of my effect is being influenced by the tempo of the sample, not the pattern. thank you!!

[1_inch_punch]

gold in them thar hills - thanks for the info - I read in a mag if you get stuck for ideas and not feeling your samples to cut them up and then whack delays on the slices.

is it my imagination is the slicer performing a cleaner cut than doing one manually or moving marks using the start/end button(?)

i mean - it sounds like it's creating a zero crossing (?) no clicks - which is great if it is...

but it could be just the medication -

[wax inspektor]

good thinking on the "slicer = chopping thang" but keep in mind that you'll be missing some chops... let's say your sample looks like this: XXXXXXXX
so the slicer could chop it up in 1th,2th,4th or 8th notes, f.x. X_X_X_X_

The start and and end points can be smoother faded than chopping manually but I never had real success with this technique. mark button is real quick anyway...

[Beanz711]

Its cool that it can chop a loop up for you, but how would I get anything across the pads? I know there is not a feature like that but to me it seems that the mark button is still going to be heavily used. Only other way is for me to throw the sliced sample in logic and have it chop it by stripping the silence. I dunno...

[kel]

let's say your sample looks like this: XXXXXXXX
so the slicer could chop it up in 1th,2th,4th or 8th notes, f.x. X_X_X_X_

couldn't you just take the og sample and mark the start point a half step later, then do the slicer again? you'd capture the 2s and 4s instead of the 1s and 3s. but i agree, that would be a pain to resample, no matter how smooth the zero crossings, it may prove to be more a test of patience than progress... then again you could just throw a fat-ass kick/snare over the divide and disguise it when i chop phrases that, in raw form, are at slower tempos i record on the fly, the whole sample twice. the first time i chop the odds in real time, assigning to pads 1,3,5, etc. (cuz the 404 is quick like that) and the second time the evens: 2,4,6. no resampling needed, just fine tune the strt/ends. and no generation loss. same idea should apply i think to the slicer, but i never thought to do it that way, very interesting!!

[wax inspektor]

...I wouldn't call myself Inspektor if I wouldn't had tried that...
(X)_X_X you mean? Marks after (X)... I seriously tried that years ago but
the slicer acts too accurate (looking at the time of each slice).. it slices "mathematically"... but you know music loops there are never played really accurate on 1,2,3,4... you know what im trying to say...
slicing= imprecise fake autochop
... but works cool to get some random chops outta long notes and pads...