SIMUL & Note Decay Issue

Here's a bit of a strange thing I ran into last night.

I chopped a one-measure break into 4 pieces. The first beat had two kicks in it. I wanted to layer a filtered version of that piece under it to add extra bass to those kicks.

I pitched that sample down a whole octave, filtered it down to about 10 and set the decay so that only the first kick came through. That was on pad 5 let's say. Then I set that sample to play when I hit the original piece of the break on pad 1.

What happened was that anytime I hit pad 1, the decay setting that I put on the filtered sample on pad 5 just did not work. Since it was pitched down an octave and playing at half speed, the second kick of that sample was happening after the regular sample finished (technically where beat 2 of the full break would be).

Reading this back it seems extremely detailed, particular and possibly confusing I can imagine.

Has anyone had this happen?

Mabye try setting the decay to "from start" instead of the default "from end"?

m56p87 wrote:Mabye try setting the decay to "from start" instead of the default "from end"?

Good point...however I already had it set from start, so only the first kick would come through. I'm thinking the decay is getting hijacked by the decay of the sample on pad 1 for some glitchy reason.

GrumpTruck wrote:

m56p87 wrote:Mabye try setting the decay to "from start" instead of the default "from end"?

Good point...however I already had it set from start, so only the first kick would come through. I'm thinking the decay is getting hijacked by the decay of the sample on pad 1 for some glitchy reason.

that is very odd & glitchy... and you dont accidently have the simultanious trigger retriggering the initial pad? (internal midi feedback loop). Im just trying to think of all possibilities.. If it is a glitch mabye trying copying the sample itself so there are two different copies?

m56p87 wrote:

GrumpTruck wrote:

m56p87 wrote:Mabye try setting the decay to "from start" instead of the default "from end"?

Good point...however I already had it set from start, so only the first kick would come through. I'm thinking the decay is getting hijacked by the decay of the sample on pad 1 for some glitchy reason.

that is very odd & glitchy... and you dont accidently have the simultanious trigger retriggering the initial pad? (internal midi feedback loop). Im just trying to think of all possibilities.. If it is a glitch mabye trying copying the sample itself so there are two different copies?

From what I see the triggered pad doesn't have anything else connected to it with SIMUL. I might try copying it over to another pad to see if the problem repeats.

Something very similar to this happens to me all the time when layering drums. Lets say i have KICK on pad 1 and on pad 2. I use simult on pad one to layer pad 2. Now if i mess around with the decay settings on the first pad it will effect pad 2 decay on playback. Always thought that was normal until i read this thread.

KidProcrass wrote:Something very similar to this happens to me all the time when layering drums. Lets say i have KICK on pad 1 and on pad 2. I use simult on pad one to layer pad 2. Now if i mess around with the decay settings on the first pad it will effect pad 2 decay on playback. Always thought that was normal until i read this thread.

I didn't think it was a normal thing...seems strange that it would be. I haven't messed with it any further because it didn't really hamper my workflow all that much.