NEW JJ OS V2!!!

rabulisten wrote:nice tip arebee...

seems daft to compromise bread and butter fx to get king tubbyish wobble fx. or any other "novelty" fx. seems that everytime jj announces something new is going down folks start asking for whack sh*t.
"throw out all fx and give me radical tape echos" pffft.

pfffffffffffffffffffffft indeed

dont get me wrong earwolf,you seem to be a knowledgeable person regarding the mpc and music,but the idea about ditching the regular fx in order to get dub echoes is kinda daft. I guess if i would have proposed to loose the regular fx in order to achive a slayer-esque guitar distorsion i would have gotten critism too, deservedly so imo. these are very niche fx. and the the mpc has some delay options already. sorry if i came across harsh.

i got a test os2 via email yesterday from jj. it's at this point unusable but i got to browse it and see how it was.

aftertouch is really really great.
velocity->EG in the filter screen provides velocity->filter modulation, so we didn't lose that feature.

the main screen is terrific, the grid preview is solid and you can record and edit notes in it. not as good as midi grid edit but it's great for quick rearranging.

16 pad grid edit appears to have been removed, but maybe i just missed it. 6 pad grid edit is still there. midi grid edit is still there, and that was always better than regular grid edit anyway. i hope in the future that you won't have to turn the track to MIDI to view MIDI grid edit.

another cool thing is that the the os boots with a bunch of samples in it, all very small single cycle square/saw waves for synthesis. load one on pad1, another on pad2, simult them together, set different aftertouches and LFOs, and warble away...

the new pad sensitivity screen offers a more specific pad by pad assignment.
mode+pad7 takes you straight to GPE
2 autoload folders is wonderful, so much better than all that internal memory crap.

perhaps the coolest function is being able to boot either os at any given time. this is SUCH a great feature, because it means we can work on our old projects without the irritation of downdating the os.

the new nondestructive slice function is really really good.
i have yet to experiment with a few things, like what happens if you specify your slices and then stretch the original sample. do the slices move to compensate, or will you have to specify slices again? there are many thigns to test and unfortunately i wasn't able to get too far. the current build is still very buggy and at this point unusable due to its incomplete nature.

jj said the specification may change and that this is just to help communicate. he asked that i try to explain some specification to the forums.

does anyone have things they want me to look at for them in the meantime?

correct me if I'm wrong Earwolf, but, you WERE being sarcastic, right? Super groove funk box os v3...

you said its not usable, so you may not be able to answer, but are you able to load projects from os1 without problems? or do they not translate well between os1 and os2?

Antonym wrote:another cool thing is that the the os boots with a bunch of samples in it, all very small single cycle square/saw waves for synthesis.

that's kinda like the Yamaha A-Series samplers. With this, you could basically turn the thing on and use it as a VA synth without having to load waves. So am I right in guessing that no default keymapped programs have been made to use these samples? I wonder what the source is for those samples? It would be nice if JJ included some Moog or Arp single cycle waves.

Antonym wrote:the new nondestructive slice function is really really good.
i have yet to experiment with a few things, like what happens if you specify your slices and then stretch the original sample. do the slices move to compensate, or will you have to specify slices again?

I would guess that you'd have to re-specify your chops (JJ does call them chops right?) If JJ gets it to work the way you're thinking, then he IS a Jenius.

I also used to be an ASR-X user, and one of the biggest benefits for me workflow-wise, was non-destructive chopping. I'm very interested to see how its implemented. If you could give some more detail I'd greatly appreciate it.

no default programs with these samples, but remember 2 autoload folders. you could make your own default and load it right there.

also, once this os is dropped, the jj os community will be able to offer a LOT to each other in terms of keygrouped programs. building these things will take no time at all, and i'll gladly host them on my web page. we could get a lot of cool keygroups up, just need to maintain quality control.

ndc is implemented like this - it replaces the old slice function. AUTO is still there. you hit SLICE, define how many slices you want there to be, and then you edit the start/end of each individual one. these start/ends can overlap. when you're viewing your current slice, it appears in dark while the rest of the sample is light. you don't see the rest of the slice lines, only the color difference of your current slice.

i didnt think to check whether you could specify alternate loop points on the individual slices. i hope you can.

once you're done slicing you enter GPE and assign the sample to X amount of pads. then in the CHOP column you assign the slice number to the pad.

i didn't try loading old projects on it yet.

Jfalconcrest wrote:correct me if I'm wrong Earwolf, but, you WERE being sarcastic, right? Super groove funk box os v3...

yeah he was just being funny, y'all pounced on it, keep it up wolfmaaaandubz. ubz, ubzsh, ubzzzssshhh, ka ka ka .

Antonym wrote:i got a test os2 via email yesterday from jj. it's at this point unusable but i got to browse it and see how it was.

How come he sent the preview OS to you? I KNEW you were JJ, Nym. I knew it all along. You had the pad fix you were working on, then suddenly "AKKIA" drops the pad fix. Coincidence? I don't think so. Also, can you stop the preloaded samples from autoloading and using up our ram space?

antonym :

1-have you tried midi cc in to q link?

2-please try to load old projects (that used 2nd filters etc...) and tell us what happen

3-filter 1 is 12db slope?

4-can you explain what are the differences between the differents kind of program(instruments drums...)?

5-do you have to reboot the mpc to change your os?

6-real time pitch is still there?

haha i am not jj. i cannot code. i think the preview was sent to me because of all the agony on the forums of people being concerned of the new specification. the webmaster has probably received more than he can handle.

since i'm a more public dude than the programmer i think it was so i could ease the pain a bit by explaining the specification. and that's what i intend to do, because we're gaining far more than we're losing. i am not getting work done on this os yet, that's for OS1.

the preloaded samples take 1 kb apiece, and there are maybe 5 of them, so they use about as much as 1 very short mono snare. no worries there.

midi cc in to qlink is not implemented yet.

i don't know if filter1 is 12db slope, but if this helps, when you turn res up all the way to 100 on any filter

old projects load, but without os1 features, obviously. projects play, but since filter is completely different (different curve, different res) it sounds different.

there is a "new" OPM accessible from the main screen. this is where all the ADSR stuff is visually displayed. in .58, it appears that this has not been placed in GPE (yet, it looks like space is cleared for it)

when you create a drum pgm, you have your typical layered approach, minus 4th layer, + adsr. when you create an inst program, the SAMPLE screen is different. you set the samples up via range. if you want sample SINE to appear from notes 35-37, you designate that range. then you move to the next sample and designate THAT range. i believe you can overlap samples, thus creating layers.

you do have to reboot the mpc to change the os. you can flip back and forth by holding the tap tempo while booting. this is a really good move.

realtime pitch shift is still there.

ah so, real keygroups, i see .

yall shouldn't sweat it. from what i've seen in this os so far we have a lot to look forward to.

Antonym wrote:i don't know if filter1 is 12db slope, but if this helps, when you turn res up all the way to 100 on any filter

old projects load, but without os1 features, obviously. projects play, but since filter is completely different (different curve, different res) it sounds different.

Uiiii! Does that mean jj improved the filter?