os2xl

i thought when pad pattern came out it was going to function like that, but it'd awesome if this could do it instead. id like to trigger mini sequences of one shots, e.g.hi hats or drum rolls.... (if it did work like this i think id probably end up asking for 8 notes per chord too, so you could get two beats worth of 16th notes out of it!!)

im looking forward to exploring the possibilities of this os for sure.

yeah man, that should work. these "mini seqs" won't be too terribly complex but they'll be nice little 5 or so note arpeggios...

i figured out that i will be better than ok with simulted pads being recorded into the sequence too - this is going to be fantastic. as a result i will just have to make better use of the new delete features in jjos2xl.

simult was fantastic, but limited in that the values were always identical. i used to compensate by adding some silence before my simulted values to kind of stutter/delay the layer, creating more of a caacrak type of snare. however, it was the same amount of delay every time. now, that's not the case anymore, which is sweet, cuz i can edit each layer's timing differently.

some changes in workflow but the overall sequencing yield will be greater.

mikolo - i biked home from work for lunch just so i could test this. here's what i found:

you CAN insert empty spots, but they still play as if they're right next to one another.

ie, a chord like this:

step 1: root note
step 2: +4
step 3: +7
step 4: --- (blank)
step 5: --- (blank

will play the same as this:

step 1: root note
step 2: --- (blank)
step 3: +4
step 4: --- (blank)
step 5: +7

basically it ignores the blank spots and treats em like next door neighbors.
i will report this a "bug" and i will imply that the creative potential of leaving those "rests" in there would be a great unexpected bonus to the CHORD function.

cool, thanks for that nym.

i biked home from work for lunch just so i could test this. here's what i found:

I hope that wasnt too far and/or you did it for your own sake rather than mine!
your info is appreciated nevertheless!

Just checked JJ's new youtube vids (uploaded on the 17th) and theres some nice surprises. e.g. changing loop lengths while playing a seq and copying the entire pad with undo key... I could go on....

also is that crossfade loop in trim or is it just a zero crossing detector?

edit:
ive thought of a possible workaround for the chord pattern thing: assign "rests" to a blank pad.less user friendly but i could see it working.

it'd nice to know if jj would consider tweaking it though.

also perhaps "playing the spaces" would make it difficult to "chain" smoothly around patterns of less than six steps.

it's about 1.5 miles, 8 minutes or so with traffic. worth it cuz i don't have to heat my food up in tupperwares. i often bike home anyway just to get some time away from the children.

your workaround would work, but only with DRUM pgms, not with INST pgms.

GOOD NEWS SOOTY G

i found out a little more about the qlinks today, and you have less to fear, especially with the inclusion of a version of the track explode feature:

turning on a qreal filter doesn't physically turn on the filter for the PROGRAM, it just does for the TRACK - ie if you use 1 program on 2 tracks, you can set HPF on one track and LPF on the other without them contradicting each other.

phew. sorry to scare you. i hope you didn't email them about this confusion.

i still haven't figured out how to achieve the "Relativity" as easily as you described it before, but here's what i just tested in both inst and drum pgms:

1-chop a sample
2-apply LPF on pad1, BPF on pad2, and HPF on pad3.
3-record a performance with pad 1 2 and 3 on track one.
4-move to track 2. put on the same pgm. assign qlink 1 to lpf realtime.
5-record a performance of both pads and qlink motion.

result: the program responds to each track's incoming info differently.

in today's report i will include the "relativity" scenario.

Yes, this is the way it should work. My Motif XS works this way. The qlink makes relative changes or offsets for all the pads on the track.

I wonder how the track explode work? Do you get to chose what pads get split to new tracks or does it split the whole track by any pads in the sequence?

you window over the pad number in MAIN SCREEN and hit window. the window says:

"PAD EVENT MOVE TO OTHER TRACK"
and then you select the track.

it's a lot like SEQ EDIT: MOVE, except it's only 1 pad at a time instead of any number of pads. it's just accessible on the main screen and a little bit faster to get at.

CHORD will really help those of us with more limited music theory over the hurdle of building chords - and for the rest of us it will help us bang stuff out quicker becuase there's less editing involved to get a nice roll

i just banged out something i've been hummin all day in so little time. CHORD is very smooth to work with

you'll notice in OS2xl that you'll be changing TRACK TYPES more in order to get at different functions. it might be wise to request some sort of hotkey to change track type, since it's becoming more like it's own MODE function.

This really sounds like the answer to all of my hopes, aside from the lack of automation. I imagine I'll find a way around this, but it just seems like such an odd thing to cut out. Doesn't it seem like there could be something else that to lose that wouldn't be such a standard feature? I do not use my computer for anything but downloading and storing samples, and the internet. I do not use a DAW and have no plans to start. Hardware rules.

Either way, can't wait to get my hands on this thing... and Nym, you are the man. Thanks for reviewing this for us.

wudsiba, save your thanks. i cannot tell you how happy i am to have the opportunity to be testing this os. i'm in a very lucky place and i will never forget it.

Doesn't it seem like there could be something else that to lose that wouldn't be such a standard feature?

it's not an issue of "with new features, other things go" it's more of an issue of the complexity of programming - with a change of specification in one place, any number of things must change in another. that's why i'm hopeful to see a return of mix automation and other things - actually, "return" isn't the best word, rather "reinterpretation."

this has been keeping me busy all night, since 3 o clock.
5 hours later and i'm still in my kitchen with my cookery and my music equipment
all i need is 4 more midi cables hahah...can't believe that's what i'm short of right now...

Right on Nym, I see what your saying. Programming MIDI is like a puzzle in that sence at times as well. That's one of the great things about MIDI, often there are several ways to acomplish any one function... I'm sure I will be able to get what I want done.

as i continue to get betas in my email i would appreciate any other comments or questions. i'm excited about what currently appears to be shaping up in os2xl, but i also feel that i'm unbiased, as i am still nothing but an end user with delusions of musical fame... i've got nothing to gain here besides a potentially badass OS that depends on our reports, observations and commentary.

how about USE EVENTS: OFF by default in track mute window...

just one thing that would be cool, perhaps tricky to make to work, would be that when in OS2 AUDIO track you can make location points and jump around the time, that midi sync that is sent out wouldn't be lost... propably impossible i'm afraid.

Nym wrote:i've got nothing to gain here besides a potentially badass OS

And that's all we really want. We here know and trust that you wouldn't sell us wolf tickets.
Your reports about the os2xl's potential has got me very exited. I had been on the fence about snatching up a 2500, with this news and developments it's a no-brainer.
Once again JJ will be the reason for me getting a "new school" MPC. Keep it comin...