os2xl

the old way would suit me better, if i want a sound in a sequence un-simulted i will copy it too another pad and record it, rather than delete the note.

the chord feature has changed i believe in 1.04. before the original pad was always considered as the first note of the chord ("c" for the default chords),and a "d" in the chord would be two pads up.

now if c3 is the root note of the chord it will only play the sound of whatever pad is assigned to c3.

e.g.pad a01 is assigned the default Cmajor chord : C3 E3 G3
hit pad a01... it does not play the note on that pad.. the first note of the chord will be whatever pad is playing c3 (which i believe is somewhere in bank B)
this means that chords cant be templates, a "c major chord" will not play any other major chord unless you de tune the pads.

rinseout wrote:Am i the only one who thinks the new simult pad sucks?
This is not layering but something else. I see the advantages but to me it´s a show stopper.
I usually do the drums very quick, to layer on afterwards. Now that´s impossible as i can´t just add layers but have to set the notes too.
Completely useless imo, it was a great feature (one of the best of the jj to me) just like any other sampler uses it.

Yeah, was just playing around with 1.04 and was working on adding some depth to the drums using simult, and was surprised to find that the simult pads are only triggered when you hit the pad, not when the note is played from the sequencer. Kind of a bummer and makes it quite tedious to layer later as is. Not freaking out about it or anything, but certainly a bit of a surprise how it works compared to other ways I'm used to.

sorry to ask but my head wont let me understand what your saying about simult (just got home after a 15hour shift)
So with simult i CANT play pad 01, record it and then later simult it with pad 02?
Do i need to play pad 01 simulted with pad 02 BEFORE i record?

Why does in not work like os2, that was a very fast and effective way to layer drums.
we should contact JJ if this is the case.

Peace!

trybtek wrote:Do i need to play pad 01 simulted with pad 02 BEFORE i record?

At least for the time being your statement is correct, you need to record the simult at record time since it records individual midi events. I can understand the benefits of doing it either way, but for now it means that the only effective way to 'simult' after you've recorded is to create a drum layer, sample that and then use that as your new sample. Not really what I'm looking for, but I'm just one person.

Dam that sux! I truly hope JJ brings back the way simult used to work!
It rocks in OS2 and its the way my 2000xl works too. would it be possible to report it as a bug???
I dont own a 1000 so i cant test it out and report it. anyone up for the job?
Please bring back the way simult used to be!
Peace!

would a heavy simult user (not to point fingers, but i know that mikolo and i have a similar simult addiction) please to create a new thread detailing the pros and cons of both "note is recorded simult" and "note is triggered by original note simult?"

both have their purposes, but i prefer the latter.

an option would be so great.
plus, it'd be good to "Catch this one early" before too many people do a lot of work in this os with the new simult and then have to go back and change it.

i'd create this thread but i'm on vacation and wouldn't have time to do it justice.

please be objective and non-emotional!!

where is loop on off?

sorry to be dumb.

Main Page, F1

NearTao wrote:Main Page, F1

Thanks

Sorry if this has been brought up already, but why do my pads, even after setting them up, do they react as if they are set at full level? I have switched bac to V2 and back again. They were perfect in V@, but when I reloaded XL, they were all at 127 again... Thanks in advance

Hello,
Today, I want your thoughts about the new os2xl drum grid edit.
Firstly, i have to say i'm a bit disappointed.

I'm still on my 9/4 chorus and I have to program my drums visually (as it's too sloppy for me playing manually and the grid doesn't really help in that ternary part of my beat)

Let me remind you in OS1 (i forgot about regular os2 sorry) You have one square in the grid = one note. Between each count you have 8 spaces when TC=32 and 12 spaces when TC= 32/3.

In os2xl whatever TC is set you have when zooming at the maximum level 8 spaces. That is to say you can't program like os1 32/3 visually. ( but for instance if you play with note repeat and 32/3 manually a line will appear in grid edit)

To sum up my main idea, os2xl drum grid edit lacks either spaces either another level of zoom and it's killing my workflow. Plus with the TC strength stuff you have notes that are not in the "grid" i guess it's a big issue for JJ.

Anyone with the same feeling?

best wishes for 2009 to all the JJ OS users.

le rat wrote:Let me remind you in OS1 (i forgot about regular os2 sorry) You have one square in the grid = one note. Between each count you have 8 spaces when TC=32 and 12 spaces when TC= 32/3.

i miss this bigtime. it was such a simple and clear way to represent the data.

Sooty_G wrote:

le rat wrote:Let me remind you in OS1 (i forgot about regular os2 sorry) You have one square in the grid = one note. Between each count you have 8 spaces when TC=32 and 12 spaces when TC= 32/3.

i miss this bigtime. it was such a simple and clear way to represent the data.

When did this go away? OS2 or OS2xl?

This is the 2nd beat I'm making in OS2 XL and I've gotta say that I'm really pi$$y about this workflow-breaking chop controls! Totally unnatural feeling, the way that the controls for setting start and end points and changing slices are arranged. It used to be perfect in OS 2. The way it is now is driving me mad: A select a slice - turn data wheel, ups this changes the slice - where was my slice to edit again - here it is- whoops, wrong column - end point instead of starting point. Hilarious!!!!

PEACE

T7 wrote:

Sooty_G wrote:

le rat wrote:Let me remind you in OS1 (i forgot about regular os2 sorry) You have one square in the grid = one note. Between each count you have 8 spaces when TC=32 and 12 spaces when TC= 32/3.

i miss this bigtime. it was such a simple and clear way to represent the data.

When did this go away? OS2 or OS2xl?

this went away in OS 2.