NEW JJ OS V2!!!

from the OS 2 page:

1. There is no screen of MODE+PAD7(PROGRAM).
2. The program and sample to an internal memory, save/load is cannot.
3. The filter 2 was deleted.
4. There is no velocity range of a layer.
Therefore, change of the layer by a velocity cannot be performed.
5. There is not 4 of a layer.

so we've lost filter 2, we've lost a layer, and we've lost the ability to change layers based on velocity.

what the hell??!

those are some serious limitations! why is he pulling stuff out now? i thought he just got a bunch of new room for the os and that feature deletion was a thing of the past.

i'm starting to have some serious doubts about this os now. i can't believe he took out that second filter & the velocity switching.

3. The filter 2 was deleted.

i won't upgrade...

Sooty_G wrote:
so we've lost filter 2, we've lost a layer, and we've lost the ability to change layers based on velocity.

strange...

ya...ditto for the 2nd filter...i find it really useful.

same here, i was using the second filter for eq. what a shame to remove it.

maybe an idea to request JJ would be to still have filter 2, but to have it static (ie: no qlink, no envelopes, just filter2: type / cutoff / resonance).
interface wise i guess pressing [window] key in the filter page could pop in a small "filter2" window.

someone who can explain clearly our opinion about deleting filters n layers etc. please send mail to jj and make him wake up

obviously JJ is removing the second filter to make way for the EIGHT NEW FILTERS per pad/layer you slowpokes

4. There is no velocity range of a layer.
Therefore, change of the layer by a velocity cannot be performed.
5. There is not 4 of a layer.

i take back what i said about reverse compatibility...this really concerns me.

hmm i never really understood the use of velocity layers anyway :S .. maybe someone can bring it in a different daylight for me in their workflow?

are you serious? i've been talking about them for a year now
every one of the example files i've upped use velocity layers
allows you to put softer and harder drum sounds on the layers and have them correspond to how hard you're hitting them

this has been a fairly crucial part of the mpc since day one

also, we were able to use the QLINK to change LAYER to access different sounds on 1 pad

also, we had a 4th layer...?

hmm.. usually i just play my kick and snare at full level and after that i just change up the velocity of the kick in step or grid edit.. maybe because of the pads weren't really velocity friendly at first i never really got into this stuff.. doesn't it slow down your workprocess if you firt gotta assign everything to the velocity layers ?

what i don't get is the difference between these two screens:



they both seem to be program editing screens, but one has 1,2 & 3, the other just has 2nd and 3rd. weird.

i seriously doubt jj would leave us without some method of putting more than one sample on a pad, and switching between them, that is a fairly basic requirement of any sample imho, and to have keygroups and not that is just incomprehensible to me.

simult remains doesn't it? i need simult!

yeah, modnar's right, i was thinking about this too. where 1 possibility leaves another will be introduced to accomplish the same thing, but i admit i am very distraught by the loss of velocitative layering...but i already thought up a better alternative. simult 2 pads and alter their velocity->amp levels. set one at 50, leave the other at 100. when you play a very light hit, the latter won't be heard but the former will. still, it's not the same...

hmm.. usually i just play my kick and snare at full level and after that i just change up the velocity of the kick in step or grid edit.. maybe because of the pads weren't really velocity friendly at first i never really got into this stuff.. doesn't it slow down your workprocess if you firt gotta assign everything to the velocity layers ?

doesn't it slow your workprocess if you have to change up the velocity of the kick in step or grid edit? sometimes (all the time imo) you can't ignore details in favor of working fast

my number 1 march request would be reimplementation of velocitative layers OR some sort of better replacement via simult, which is what i could easily see happening.