OS JJ 2XL : old simult pad behaviour?

hello, i'm thinking about switching to 2XL, but I need to know
what people feel about it.

for example, what is this "old simult pad behaviour" thing ?

alamin

old simult behavior:

pad A01 is simulted to B01.
hit pad A01: both pad A01 and B01 play.
record pad A01 into a sequence: pad A01 is recorded into a sequence.
when the sequencer plays A01, B01 is also played.

new simult behavior:

pad A01 is simulted to B01.
hit pad A01: both pad A01 and B01 play.
record pad A01 into a sequence: pads A01 and B01 are both recorded into a sequence.
when the sequencer plays A01, B01 is not played. B01 is only played by the sequencer when the note is recorded into the sequence.

this is a behavior that i and many others do not like.
i've mentioned that it'd be great to get it switched back, or at least have the option created to have both behaviors as an option.

SIMULT1
SIMULT2

as it is now, new simult behavior is unusable for my style of drum programming.
it has its benefits, but they are few compared to the original simult method.

new simult also sends out midi notes for both pad A01 and B01 now which is nice

that's very nice to know.
old simult did not do that? i don't remember ever trying to output multiple midi notes.

all the more reason for multiple simult behaviors. thank you, forax.

mute
simlt1
simlt2.

i did not know one could do "simult pads!"
how do you "link" A01 to B01 for example ?

it's in GPE under the MUTE page. turn from MUTE to SIMULT.

before i get heated about simult, what could be the strengths behind JJ's decision to redesign the behaviour?

it was fairly understandable how previous OS's employed Simult, but this alteration has set up a few questions as to what simult is best used for....ie: the new midi transmission on simulted notes.

are there more reasons here for its change? anyone know what JJ might be thinking?

plain and simple, he might think that this is a better method. and in some ways of thinking about it, it is a better method. you can record the hits and then edit the timing separate. at first, i was kind of excited about this, but in practice it wasnt nearly as good for what i did with it as i wanted.

that's why i've been mentioning to have both behaviors as an option, especially now that we're on 1.06 already and some people's projects might be dependent on the new simult behavior already.

i think perhaps simult was reworked to enable the new chord feature.

what i can't figure out is why the chord & arp functions do not sync to note repeat/TC? is it really necessary to have an extra 'chord repeat rate' function? if it were linked up to TC you could turn on note repeat and play interesting rhythmic variations and have them shuffled.

i think perhaps simult was reworked to enable the new chord feature.

it may be, but then again it could have been anything else. we can only speculate and accidentally start rumors

if the current simult situation is messing anyone up and you work with a DAW "drumagog" will get you through for the time being. it's got me through the last week.

yeah i'll be using POISE and just output the midi of my drum tracks and SIMULT it that way. i'll just use the mpc for breaks. POISE is sweet - has offset and everything. this would free up some polyphony too, since my drums is what takes up the most polyphony on my tracks for sure.