NEW JJ OS V2!!!

PM me if anyone wants to see my bug report for os 0.65
it's way too long to post here and would probably cause too much worry
but i had a blast today finding bugs and making observations.

Am I the only one who gives a (expletive) about the God Dam Rules?!?!?

You're entering a world of pain smokey.

I know OS2 is in a very early stage and blah blah about not having all the functionality and polish yet, but upon loading up OS2 here are my opinions:

-This is very obvious, but I think JJ is moving away from drum programs and into sampled instruments. Meaning, IMO, people who make traditional drum kits will find themselves with less options then those who use their MPC to build more dynamic, non-percussive instruments. The removal of velocity based manipulation takes most of the expressiveness out of being a drummer, and with the inclusion of aftertouch, gives all the expressiveness to keyboard players, knob tweakers etc. After playing with his example programs w/ aftertouch, I was immediately impressed with what power JJ was able to bring out of the machine. It is very easy to become creative since he has aftertouch modify functions that i would regularly assign to knobs on my midi controller anyway.

-The NDC opens up room to chop/slice without fear of making mistakes and the ability to have chops play the same section which i think is exciting. In its current form however (I know, under construction) It's more work than DC. He will most likely put in some sort of mapping-to-pads button in the future which would make it almost indistinguishable from DC.

I think I'll buy it once it's officially released and all the workflow issues are sorted out and am really happy that JJ has let us play with the aftertouch (the most impressive effort of version 2).

A few more notes:

-grid edit in the main screen is awesome. It feels so right and it seems I cant remember what was there before

-I would suggest people load their old projects with the new os and play them and see if you are missing anything. I was also disappointed when i heard of the removal of features but realized that in my last 10 or so projects i had not used any of them.

what's up man. let me make a quick comment on the one thing i saw in your post that may be a little off:

[quote people who make traditional drum kits will find themselves with less options...The removal of velocity based manipulation takes most of the expressiveness out of being a drummer[/quote]

the only velocity based manipulation that has been removed is the following: velocity to attack and velocity to start. velocity-filter is still there, just in a different place. this is the most important of the velocity->_____ besides velocity->level. Aftertouch also provides a great deal of velocity->filter control. check out velocity>EG and the aftertouch control in the filter section of NewProgramMode.

you'll find that much of what appears to have been removed is actually just moved around a little bit.

i'm a traditional drumkit addict. i wouldn't be able to live without most of the features included in os1 to make my drum programs. since i come from a nonmusical background, rhythm came most naturally to me, and my beats are 100% drum driven. that being said, i'm not concerned in the slightest about using os2 to create my drum programs.

we took 1 step back, and then hopped on a bus and drove forward to the next city. i bet we'll all discover that for ourselves.

Yes I must be blind. Velocity range is right in the pad menu for (drum) programs. Ignore my rant! I hope he switches GPE to pad 7 and puts the PAD edit in pad11.

good idea.

oh, also, did you see this???? this really got me excited. brings layers to a whole new level, no pun intended

After touch -> Sample layer crossfade (Under construction)

!!

Antonym wrote:good idea.

oh, also, did you see this???? this really got me excited. brings layers to a whole new level, no pun intended

After touch -> Sample layer crossfade (Under construction)

!!

ooooh missus (drools)

man i'm sitting here imagining what that means....

conceptually, you could create a inst program with 2 completely different sounding samples, say a static sample and then a sine wave. aftertouch would crossfade in between the two based on pressure.

that's NUTS. the implications of this for actual musical usage (above is just an example) is enormous.

Antonym wrote:man i'm sitting here imagining what that means....

conceptually, you could create a inst program with 2 completely different sounding samples, say a static sample and then a sine wave. aftertouch would crossfade in between the two based on pressure.

that's NUTS. the implications of this for actual musical usage (above is just an example) is enormous.

YEAH BUT SON HOW YOU GET THEM 808'S TO BANG SON?

Thanks a lot Ant! I can't wait to get my hands on this program! What I'm wondering now is how compatable the two systems will be with each other... For example, say you edit a bunch of your samples in ver. 2, will ver. 1 be able to play these samples? Maybe you would just have to resample and store as a new wave? Middle of the month is coming quick...


Oh, by the way, I love your avatar. Great stuff!

the samples i think you'll be able to edit, as long as you don't use NDC.

projects will not be compatible at all.
the best compatibility trick i'm currently aware of is to resample as audio track. this will work a treat.

Yeah that's what I was thinking. Worst comes to worse you can always rsample then bring it up in version 1 and add onto it there... Sounds like that's kind of what the programers had in mind seeing how you can choose whatever version you want it to run... As far as I can see, you can't lose.

That's what I'm doing - resampling.

G4s

gotta a question - if we constantly have to flash to swap between OS1 & OS2
how many times can this be done?
is it like a USB pen drive - and can be used thousands upon thousands of times?
or is there a smaller limit, that could be a future problem?

cheers

f