[REQUEST] Pad Cycle mode work with pre-recorded sequences

ok. i've just tried the new PAD CYCLE feature but i've found it does NOT work with previously recorded sequences.

example: if you have a sequence with pad 1 hits recorded on it and turn the new PAD CYCLE mode on, the sequence will still continue to play only pad 1. the cycle effect will only happen if you physically hit the pad with your finger.

pad cycling can only be recorded after the fact into a sequence (if you have cycle switched on and record a sequence, the grid will show the different pads being recorded as they cycle thru).

i would really like JJ to add the ability for cycle mode to work 'live' with pre-recorded sequences. anyone else? this was actually the main reason i wanted to use it. with cycle set up with your old sequences you could add a lot of variety and movement, especially with cycle set to 'random'. you could have your sequence running and never have it play exactly the same way twice, but still have it controlled so it doesn't get too crazy, similar to how a live band or drummer would actually play with a natural looseness and variety in timing and sound.

+1

+1

I ve also noticed that LOOP&HOLD and CYCLE are incompatible but I guess it 's impossible to improve this.

le rat wrote:+1

I ve also noticed that LOOP&HOLD and CYCLE are incompatible but I guess it 's impossible to improve this.

Yeah, I'd rather have what you're sayin than a chord track or smthin

how bout just a "CYCLE2" similar to the way SIMULT2 works?
where the "mother" pad is the only one triggered and recorded.
would that solve your problem?

Nym wrote:how bout just a "CYCLE2" similar to the way SIMULT2 works?
where the "mother" pad is the only one triggered and recorded.
would that solve your problem?

yep. i sent this exact request to Murai last night & he forwarded it to JJ, so i hope this is doable.
here is what i sent:

the purpose of PAD CYCLE (the reason for the original request) is to create variation. to give a looser, more natural sound like a human drummer.
if the pad event (the cycling) is recorded, on playback it does not change anymore and once again sounds 'mechanical'. repetitive. the variation is lost.

this is why PAD CYCLE should be 'live' only. it only works in realtime and should not be recorded.
so when a sequence is played back, it is still cycling live and the variation is kept.

a user can then choose if they want the effect or not by turning PAD CYCLE on or off. even in realtime.
this gives many more creative options.
(example: by changing PROGRAMS while a sequence plays back, one can turn variation on or off, or change the pads assigned to the cycle.)


however, another option is to add another mode like with SIMULT1 & SIMULT2.
CYCLE 1 = an event is recorded and does not change on playback.
CYCLE 2 = an event is not recorded and does change on playback.

Yeah, this is a legitimate request. When you first requested it I didn't understand and now I do--I don't play live.

Excellent feedback.

I finally got some time to explore this & yeah - if it could be taken just one step further to work on seq playback. Like you said - the pad assigned to cycle stuff doesn't play anything back via midi so feeding-back midi out to in won't work either (I understood that after trying it out).

One thing - when you hit shift-pad (i.e. the pad asigned to cycle) during play & the MPC starts to note-repeat - it cycles then & freaking sounds really sweet.

so I guess the cycle mechanism is happening where the pads input to the drum program.

if the pad event (the cycling) is recorded, on playback it does not change anymore the variation is lost.

This makes perfect sense to me.A sequence should play back and sound the same every time. It should be totally and utterly predictable and absolutely identical each time it is played. Imagine the confusion when you record something, and press play and it sounds different. And stop and play and it sounds different again...

the purpose of PAD CYCLE (the reason for the original request) is to create variation. to give a looser, more natural sound like a human drummer.

When I press record I want the machines to record exactly what I do, and reproduce that when I hit play again. Anything else is NOT recording and playback.
When I record drums, I want my looser, more natural sound to be heard when I hit the drums. But when I play it back I want to hear it exactly as I played it.

You are really asking for a new and slightly different feature

yo. sorry i didn't update this thread but i just want to point out that my request here DID make it into os128xl.

i checked it out when i went to visit Nym a couple months ago. (it was the first thing i wanted to check out on the new OS! )

i recorded a simple 1 pad hit on each step of the bar, loaded up 4 different samples and turned cycle on as it played back and the cycling worked on playback. you can turn it on/off on the fly, change the cycle types live, etc...

hopefully this feature will make it into the small screen mpcs as well!

innovine wrote:

if the pad event (the cycling) is recorded, on playback it does not change anymore the variation is lost.

This makes perfect sense to me.A sequence should play back and sound the same every time. It should be totally and utterly predictable and absolutely identical each time it is played.

sounds really boring to me, but that's just personal taste. i don't like really repetitive music. i like things that constantly evolve and change as they play back, even if it is just small variations.

Imagine the confusion when you record something, and press play and it sounds different. And stop and play and it sounds different again...

it's not confusing at all. i'm not talking about radical crazy variation here (tho you could set it up like that), i'm talking about little change-ups that make you prick up your ears and take notice. make the drum machine sound a little less like a machine.

the purpose of PAD CYCLE (the reason for the original request) is to create variation. to give a looser, more natural sound like a human drummer.

When I press record I want the machines to record exactly what I do, and reproduce that when I hit play again. Anything else is NOT recording and playback.
When I record drums, I want my looser, more natural sound to be heard when I hit the drums. But when I play it back I want to hear it exactly as I played it.

cool. THEN DON'T TURN ON PAD CYCLE! problem solved.

Sooty_G wrote:sounds really boring to me, but that's just personal taste. i don't like really repetitive music. i like things that constantly evolve and change as they play back, even if it is just small variations

Yes, it is personal taste. And I am not talking at all about how it sounds. I am talking about how predictable the playback is. That is the point of playback.

For example, you are thinking about your small variations, but that is limited to how YOU use the feature. What if I assign wildly different samples, and bash away on the pads while recording until I hear a combination of sounds that I love. If it's implemented your way, I will not have recorded what I heard, and not only that, but it'll sound completely different every time I hit play.

Regarding the way you want it, it does make sense for those small variations to exist, but I am talking about having the SAME variations applied each time the track is played back, so it is consistant and predictable. Applying randomization to playback also means it would not be possible to record a beat (with randomness while recording it) and then listen back to see which bars sound best, and then use those.

THEN DON'T TURN ON PAD CYCLE! problem solved.

I dont want all my hits to sound the same. I want my SONG to sound the same when I play it.

innovine wrote:I dont want all my hits to sound the same. I want my SONG to sound the same when I play it.

so turn pad cycle ON when you record to get variation, then turn it OFF on playback so your beat always sounds the same. easy.