os2xl

also, regarding chords, you can easily change the chord to be in the same key of your song by simply changing the root note...handy handy

sounds like some nice stuff for someone who uses the mpc without any outboard gear. you can get more use out of your inst pgms.

i do find it funny that my mc-909 has all these features. even timing streangth.

but this is good stuff. much farther than i ever thought the 1000 would go.

Nym wrote:

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

DEALBREAKER right there. what the fukc is JJ thinking? that's cheap. if i wanted to just put a big fat sloppy filter sweep over the whole program, i'd just run the MAIN OUTS into an external filter box or something. the whole point of the Q-REAL stuff is that it's well integrated with the program and the MPC itself.

i'm not down with leaning on DAWS & VST's to do simple stuff that the MPC should (& WAS) already capable of doing. if i wanted to use all that stuff what the h3ll do i need an MPC for? i'd just buy an MPD and use it to trigger a bunch of stuff in Live / Reason / Reaktor / whatever. i'm not bringing a laptop out live and that's why i got the MPC.

if JJ's running out of codespace, then he should pull out the SIMULT PAD like he said he was going to. because then at least there are features in the OS to reproduce that fuctionality (LAYERS / CHORD). but when he screws up this Q-REAL stuff there is no way to get those capabilities back.

JJ's done this before: introduced a new OS and given 2 new ok features and then takes out 1 old really good one. he's got some wack priorities sometimes. we have to make some noise until he puts it back. sorry, but i'm not paying a cent for OS 2xl until he fixes this.

but Nym, here is what i was really asking about: how is this QREAL data recordable? he said 'there is no QREAL of a grid' so does that mean that you can no longer record your qlink performance data? no longer record CUTOFF, TUNE, RESONANCE, LEVEL AND PAN changes into the sequence ( not to mention all the NOTE ON stuff )? if that is true then that is INCREDIBLY bad.

now there's an alarmist attitude. it's as regular as rain whenever a new app is in the works...

as usual, calm down, it's never as bad as you think it is, and often a lot better. it's also more complicated than codespace. os2 has a whole lot more than 2 ok new features in exchange for 1 really good one - that's why you're using os2 now, not 1. think about it. as is, you've already got os2 and may just have to be content enough to stick with it to maintain your priorities. just examine the three once you've tried them all and decide which you personally want to use the most.

you can record qreal edits, but there's no graphical qreal grid edit. at least for now. drum mode grid edit has changed a lot, and if you notice in os1 and os2, qreal edit is based on/in drum grid edit - unlike control edit, which is based on/in MIDI track grid edit.

as of now, LEVEL/PAN is not automatable (no mix automation) and RESONANCE is determined in the qlink assignment, and not recordable. this is where i hope to see future work pertaining to MIDI CCs, as the entire "qreal" concept should have just been cc based from the beginning in my opinion.

also, this is a beta - who knows if it's even a completed feature

for instance, there's a window under construction that lets you select and then move individual pads to their own tracks.

Nym wrote:as usual, calm down

i'm calm... as long as he doesn't cripple the OS.
the reason i get upset is that OS 2XL sounded sooo perfect for me. the QLINK setup & SIMULT SEQ level in the MAIN screen, customizable MAIN & NUMERIC key, this is all great for me. excellent for live use. i was ready to pay as soon as it dropped.

then i hear how the filters get messed up and it's oh NOOOOOOO....

you can record qreal edits, but there's no graphical qreal grid edit. at least for now. drum mode grid edit has changed a lot, and if you notice in os1 and os2, qreal edit is based on/in drum grid edit - unlike control edit, which is based on/in MIDI track grid edit.

lack of graphical edit isn't great but i can live with it as long as the data is recordable.

as of now, LEVEL/PAN is not automatable (no mix automation)

still think this should be brought back.

and RESONANCE is determined in the qlink assignment, and not recordable.

ditto

this is where i hope to see future work pertaining to MIDI CCs, as the entire "qreal" concept should have just been cc based from the beginning in my opinion.

agreed and if JJ could pull this off it would be a dream come true. but i thought he already said this wasn't doable without a ground-up rewrite of the entire OS (remember the whole MIDI CC IN thing?)

but what's really killing me here is this new QREAL filter implementation that you've described.

example: i've got samples on 4 pads. pad 1 has no filter. pad 2 has lowpass, pad 3 has bandpass, pad 4 has highpass, - all at different degrees of strength. i tweak the CUTOFF qlink & i can bring the relative levels of each filter up and down. each keeps their own character.

but now according to what you said, i tweak the CUTOFF QLINK & a lowpass filter gets slapped over the whole thing, even the pad that has no filter at all on it!! you see what i'm saying? you lose a ton of control, flexibility, and subtlety in your filter use. that's a showstopper for me.

Nym wrote:there's a window under construction that lets you select and then move individual pads to their own tracks.

this is cool. sounds like the EXPLODE feature i requested.
i really wanna use this OS so he's got to fix this filter issue (i'll call it a BUG).

i'm gonna do a write up on the different handling of filters in os2 and os2xl detailing how multiple filters are used on different pads in NON-INST pgms (i hate calling them DRUM pgms because they're not necessarily drums) and how multiple qlink realtime recordings are no longer possible under the current setup.

i do have a feeling that something's not quite done, seems like a step backwards in attempts/preparation to take a different step forward. the song "divining rod" from my last mixtape couldn't have been made as easily with the current setup.

similarly, the depth of filter1 has changed as well. overall, with filter2 and filter1 and the addition of high and low eq, there's considerably more non-realtime control over the sound, but less realtime control over the sound.

what the fukc is JJ thinking?

maybe he's thinking to put it back in os2xl2.

arpeggiator now also runs at 1/4 note speed, which in doubletime resolution = 1/8th notes

chord + aftertouch bug was corrected (chord tracks only respond to aftertouch after being recorded into the sequence, not in live performance

hi nym, regarding the chord feature: is is possible to leave gaps in the chord so that the gaps are pronounced when the arp delay thing is applied?

im havin trouble imaginingg what you mean. could you explain further?

do you mean the durations of the individual notes?

ohhh or do you mean "empty notes" which in effect do not get played, and as such the space gets skipped?

le rat wrote:

what the fukc is JJ thinking?

maybe he's thinking to put it back in os2xl2.

os2xxxl t-shirts for us Americans... would you like to supersize your JJOS?

I know there are OS size limitations, I just keep thinking I wouldn't mind sacrificing a bit more RAM space to give OS2/OS3 a little more breathing room so that extra features could be loaded from HD/CF or something. Given the space limitations currently and what JJ has been able to do, imagine how many more features could be squeezed into 512kb or 2mb or whatever of RAM. I'm not sure if the MPC 1k could do this or not, but it would be pretty slick if it was possible.

ohhh or do you mean "empty notes" which in effect do not get played, and as such the space gets skipped?

yeah exactly, so you could use it trigger mini patterns.

if 123*56 represents six slices, the numbers would play notes but the asterix would be an audible silence, equal to the length of the played notes.

when building a chord, there is a BLANK space if you haven't selected a note yet - however, once you turn ON a note, i don't think that you can turn it back off - yet. this would be one of the best/most powerful feature requests for CHORD imaginable, and also quite easy to implement.

i'll test this on my lunch break and see.

if you're right and we CAN do this, CHORD can start to function as an omnidirectional arpeggiator, unlike the current arpeggiator which only travels UP the scale (and is played with multiple fingers on multiple pads)

wow, you've gotten me excited about that idea

NearTao> I don't think os size limitation is a problem. I remember an old thread in the forum with JJ explanations regarding this and if I remember well the maximum size is about 5mo ( I guess that's the internal memory capacity).