os2xl

is solid.

chord feature:

it sends midi (ie triggers multiple notes into the sequencer, ie is not like pad pattern which pitches 1 pad via qlink note on data). this means that you can record your chord and then edit the notes individually afterwards. it also means you can use it with vsts and outboard gear.

it's easy as hell to set up and edit

the "arp" function (might be better off being called a "roll" function" is a nice addition to add a little realism to your chords

the duration function is cool, you can hit/hold a pad and have it's chord repeat at certain intervals, though i hope for a feature to turn the duration off and have each chord last as long as you hold that one pad/key as well

any other questions? it's a solid, simple feature. the chord list is saved to the mpc's flash memory. i'd love to be able to save them with the sequence data, like the line patterns, but it's no big deal. can't complain, cuz this is a solid compositional feature.

i see it as also great for live use, too.

sounds dope, is this osxl coming for the 2500 too?

thanks

Nym wrote:any other questions? it's a solid, simple feature. the chord list is saved to the mpc's flash memory. i'd love to be able to save them with the sequence data, like the line patterns, but it's no big deal.

so can you define your own chords & save them to the flash memory? i'm thinking of alternate tunings. how many different chords can you store in memory? it would be cool to build up a library of all sorts of different traditional ethnic tunings (balinese gamelan, classical indian (like sitar music), etc... ) to use & share.

yes, for the 2500 too, eventually.

so can you define your own chords & save them to the flash memory? i'm thinking of alternate tunings. how many different chords can you store in memory? it would be cool to build up a library of all sorts of different traditional ethnic tunings (balinese gamelan, classical indian (like sitar music), etc... ) to use & share.

yes, you can define your own chords and save them to the flash memory. a bunch are already provided but those are mostly confined within one octave - they're there to be embellished/changed/added onto. and you can always revert to the original defaults easy enough.

you can store 32 chords in memory if i'm not mistaken.

regarding alternate tunings, that's gonna be done at the program level on individual notes, so it'd be a combo of the saved chord and the tuned pgm.

Nym, can you comment on this:

21. The ZERO CROSS key was added to the "Joint" window of TRIM.

yeah, while i was sleeping they sent me beta 68 (started with beta 60 the night before)
the addition of crossfade loop to the joint page in trim
i haven't been home since i last posted but i'm very very excited about that

20. The pad of the target of a SIMULT PAD is also recorded.

hmm this is going to take some getting used to, but it's a nice idea...
i usually link A15, B15 etc so that's going to get messy in midi grid edit

21. The ZERO CROSS key was added to the "Joint" window of TRIM.

this is good news!

Nym, can you tell us what's up with the QREAL situation?

qreals are different, and this is an area where i expect folks will have to get used to the changes. i certainly will, but i'm lucky cuz i'm changing the way i do things -- less portable, more stuff w/ ccs and in daw -- but others will have to make their own judgements.

qreal filters now bypass program mode completely - ie, you turn on qreal LOWPASS on a track and the result = lowpass applied over the entire program.

this means that you cannot adjust individual pads filters/filter adsr envelopes.

while this is kind of a bummer, it comes with other good things - filter 2 for instance, and the eq high/low. very helpful. you can get a broader range of sounds now, but less is automatable.

i didn't actually use this in practice, just in observation, so i'll have more comment on that later

This sounds great! I can't wait to try out the Chord function and create my own chord groups, and what Sooty G said about alternate tunings and sharing ethnic chords sounds like an incredable idea!

Nym, could you try to record a basic sequence to see if you can load it into reguar OS2? If this works without any problems, it would be a good way to add automation. That way you could build a sequence in XL, and mix it in OS2...

yeah. chord is going to be straight up valuable, especially when he gets the current chord+aftertouch bug sorted out.

^ i can tell you right off that it's probably not gonna work, without even asking what your definition of "basic" is - i tried loading a drum pgm last night, one whose settings "shouldn't" have been incompatible by features used, but the loop points played back funky (looped items played indefinitely)

recreating the program in XL was successful - it just didn't work from the original

not to mention that qlink realtime data will not be compatible.

TIME CORRECT STRENGTH is fantastic. crossfade loop is pretty dope too, simple but it works the way i needed it to

workflow is very similar to os2 so far, nothing hugely different.

in CHOP, however, REGION is a parameter you can grab. so instead of moving from chop 1 to chop 64 one click at a time, you can wheel over to it. this is real handy, except for the fact that it's right in the middle of the START and END point parameters. this means that when you're flickering back n forth between ST and END, you have to click through the REGION parameter.

in my bug reports i'll be asking that he change the order to START _____ END _____ REGION __

currently it's START _____ REGION ___ END _______ and you can't go immediately from ST to END. a little clumsy.

thanks for the info nym, yeah just when i thought chopping couldnt get nicer, a region param would be great, after the end value though as you've mentioned, other wise it'll slow me down for most things.

for me fast chopping, alt loop and gpe is JJos! ....oh yeah and not losing work.haha

all this new stuff looks cool, looking forward to playing with chord, i was wondering if some of the removals are to prepare for possible future extras (e.g.multi timber and so on) .there are a few things I do where q link to pad is pretty handy .- "mixed" programs of different one shots for live playing for instance but never mind eh.

qreal filters now bypass program mode completely - ie, you turn on qreal LOWPASS on a track and the result = lowpass applied over the entire program.

Im assuming that if no filter is assigned to a pad then the qlink>filter would have no effect on that pad?-as is the case at the moment. (same can't be said for sample start,tune, etc of course)

Im assuming that if no filter is assigned to a pad then the qlink>filter would have no effect on that pad?-as is the case at the moment. (same can't be said for sample start,tune, etc of course)

nah, activating qreal filter actually TURNS ON a filter for the entire program - therefor it does have an effect on the pad

qreal is the one biggest difference in jjos, gonna take the most gettinng used to, but so far the other additions are just so good that i cannot complain one bit.

and as far as more specific "qlink" work goes, as well as mix automation and other stuff, i'm planning to start using my individual outs and vsts/ccs more.


the arpeggiator is so sweet...