About the filters in OS 2XL

i just got a large email from jj regarding some of this os2xl stuff.
a lot of good news. i understand it all and know that things gotta be a certain way sometimes.

first: a sigh of relief.

[SIMULT PAD.]: CHORD can be substituted.

ahhh.

second: regarding filter cutoff: jj maintains that filter1,2 and ADSR should be all on the same screen. this leaves little space for VELOCITY->CUTOFF. in effect, it sounds like he is actually bumping velocity->cutoff in favor of filter2 because of SPACE, not because of hardware limitation...!

The PAD velocity of MPC1000 does not become useful.
"Filter2" will be more useful than "Velocity->Cutoff."
If required, it adds to other screens.

ie, "if we require velocity->cutoff, it'll have to just go in some other GPE space, or maybe a WINDOW screen in the filter GPE page.
EITHER WAY, NO F'IN BIG DEAL, RIGHT? easy street.

compatibility is going to be different. i don't think it'll be program compatibilities so much as sequence data, but i don't know how far that'll go either.

first:

XL gives priority to the ease of using.

and here i was thinking it was easy already!

A sacrifice is required in order to reform. An effort is made so that a problem may not occur, but a priority is low. 50% of the development time of OS1 and OS2 was spent in order to maintain compatibility. If priority is given to compatibility with old OS, no new things can be performed. I want to use time for OS newer than old OS.

well sir, this gives me reason to finish all my os2 projects i guess as opposed to startin new ones.

don't be worried. if you're happy where you are, it's coo, stick where you're at...i'm definitely gonna see what's happening in xl

excellent news nym, or should that be xl-ent news haha..
thanks for posting the info. glad to hear that chord will be the replacement for simult after all. and yeah... opening windows to access less used features is not a problem at all. roll on December!

also if simult is replaced by chord... that might just mean that mute groups and simult will now be independent, there were many times when I would have liked to have used both in the past, but had to sacrifice one for the other.

ahhh!!! i didn't think of that, but me too!!

i'm down with what JJ is saying, but i just don't want him to pull USEFUL stuff out - removing capabilities that the machine and OS currently have.

he says FILTER 2 is more important / useful than VELOCITY DEPTH. i disagree. i say: leave those decisions in the hands of the user.

i love JJ but as i understand it he is a programmer, not a musician. he was already going to pull FILTER DEPTH out due to an apparent logical conflict with another parameter because he didn't see the musical possibilities in it. when i pointed out one unique use of DEPTH to him (FREQUENCY=100, DEPTH=-100) he put it back in.

if it's really down to lack of space in GPE, that's an easy fix and should never be a reason for pulling something out. every tab in GPE can have a second screen. just look at the LFO/MUTE tab. i would leave all of FILTER 1 on one screen and put all of FILTER 2 on the second screen. it's very quick and easy to switch between the 2 especially when the cursor remembers it's position from screen to screen.

oh yeah, and get rid of that damn GENERAL MIDI column in the AMP screen! that would free up almost half a screen!

anyway, i'm just gonna chill till the new OS comes out and then see what we got & then hit him with the requests later if necessary.

also, i was always the one saying "forget compatibility with the older OS, lets add new features!". while i'm still down with that approach to a degree i nevertheless think it's too early to be breaking compatibility with OS 2 projects. OS 2 is too new to be rendering work done on that obsolete already. remember OS 2Xl get's installed over OS 2 so you can't switch back and forth easily like you can with OS 1 & 2 currently.

trybtek wrote:I dont really understand why JJ would develop such an amazing os (OS2) and then decide to make a newer OS and REMOVE important additions!?!?!?!
I cant see why he cant just keep the os the same and add to it.
I just hope he ends up keeping SIMULT PAD, this is very important to my programming!
Peace!

With the limitations of the actual coding area, it now becomes a situation of choosing the OS that will suit each project. Even though all of the OS versions can not be loaded into the Mp at one time, they can easily be stored on the CF card and reloaded for whatever project needs whatever OS version. Just another step when loading or developing a project.