JJ OS V2 - Feature Requests

yeah DVS i think thats a great idea.
It'd be cool to be able to set an active track to mute another too. i.e. when you unmute a track it mutes another track.
Id like to be able to assign pads in program mode to mute tracks too e.g.
pad a15 mute target > track8. That particular pad will mute the designated track but the other pads will play as usual.

thedvs01 wrote:Track Mute Groups / Simult Mute --

so that when you're in the track mute screen you can assign a group of tracks to one single pad for simultaneous muting and unmuting.

that way if you're the type who puts each individual drum on it's own track, you could still assign them to one pad for muting and drop out your whole drum part real-time, etc.

Also

MIDI Layers for pads

Like, instead of assigning layers of samples to one pad, you assign a group of MIDI notes, so that you can assign one pad to play a chord

If you could set it up so that if you have a MIDI keyboard plugged in, you can play a chord, have it recognize it, and then save that chord to a pad, that would be even better

If anyone has seen the drum/chord pads that are on the Korg M3 workstation then you will know exactly what I am talking about

MIDI Layers for pads

Like, instead of assigning layers of samples to one pad, you assign a group of MIDI notes, so that you can assign one pad to play a chord

If you could set it up so that if you have a MIDI keyboard plugged in, you can play a chord, have it recognize it, and then save that chord to a pad, that would be even better

that's a goddamn FINE idea.

Antonym wrote:

MIDI Layers for pads

Like, instead of assigning layers of samples to one pad, you assign a group of MIDI notes, so that you can assign one pad to play a chord

If you could set it up so that if you have a MIDI keyboard plugged in, you can play a chord, have it recognize it, and then save that chord to a pad, that would be even better

that's a goddamn FINE idea.

I had it for OS1 but figured it wasn't likely for that OS

Either way I submitted it to JJ -- I normally wouldn't but I think that one's very do-able for OS2

Here's how it works on the Korg M3 (it's about 5:40 onwards in the video):

http://youtube.com/watch?v=Pwmv9tDhzjY

A quality high pass filter is REALLY important-because it affects the whole mix of the beat- filtering out sub 30 herz and sometimes higher is essential for getting the gain structure right when composing- tracking and best not left till the very end, as it affects how you balance the different elements of the beat volume-wise. The cheap e.q. we have now is'nt good enough. It can make alot of room for other things in your beat and make your beat sound so much better- essential.

sorry to post 2x, i just figured- they do Q-clone, which takes a digital snap shot of an expensive e.q. that you can call up to use- i don't know how much code it would use up, maybe there's a way to do it so it would'nt take up too much-but it would be great if we could have that in our'e beloved mpc1000- a snapshot of a high end 30hz cut to use in the effects buss-the one i use is the UAD Cambridge (butterworth 6 slope)- after i've high passed the low end my beats are twice as loud before hitting 0db!- it's not that far out and well worth it!

Id love to be able to chop my sample then hit a button and it would automaticly throw the chops into a program and also place each chop on a drum track . SO if i chop a perfect loop will play perfectly but with each sound on a pad .

This would be the best thing for me .

Does this make sense ?

Something else I would like to see in OS2:

Automated sample copying (i.e. NOT the 'extract' function) as well as automated re-sampling.

I'll explain.

First, sample copying:

There are two ways to 'copy' a sample currently.

Either use 'Extract' in the trim screen and extract the entirety of the sample to another sample with a different name. The downside of this method being that you will lose any loop points that you've set in the original sample.

OR

Save the sample, re-load it, and it will tell you the file already exists, so you just rename the file. The plus side of this method is that you get to keep your loop point data. The only downside is really the extra step of saving and re-loading. I think there should be a 'copy' function from the trim screen

(If this is already a feature of OS2 then just ignore this, I haven't messed much with OS2 yet)

Now to the more important feature though.

Automated Re-sampling:

This again deals with preserving loop points.

I'll set up a scenario, let's say you have a sample, say its a 'C' note off a piano. You already have this sample set up so that there is a pingpong loop on the decay so that the note extends indefinitely. It is in your program as 'note on' trigger.

The sample is stereo

Now let's say that you want to set up a chromatic program with this 'C' note, but there's a catch -- you want each pad to have 3 layers:

The original C sample, a copy of this sample pitched 12 semitones up (one octave), and a copy of that sample pitched 12 more semitones up (a second octave above the original)

This is pretty easy to accomplish already, just use the PITCH SHIFT function in the trim screen.

But, the samples are stereo - that means each pad is using up 6 voices of your polyphony with each trigger. If you play a three-fingered chord you are using up 18 voices with just one chord. This is horrible given that the limit is 32.

You want to re-sample the 3 layers into one layer to save on polyphony. Herein lies the problem.

If you re-sample, you will have to re-set all your loop points that you worked so hard to preserve the first time, as they will be lost when you resample.

This is a pain in the ass, so I am recommending the 'Automated Resampling' feature (or simply a 'MERGE' function in the trim screen)

This would allow you to take your 3 layers, each one pitched an octave higher than the previous one, and merge them into one sample while still preserving any loop points that you had previously set. Pain in the ass eliminated, and polyphony saved -- everyone is happy.

to above, you are totally right. especially with the addition of the instrument programs. If you want to preserve all that parameter data but move that sound to a different pad to, lets say pitch it. You can't do this with resampling because all of the parameter data is lost. We need this, because the work around is time consuming.

Broken Record, but TRACK MUTES the way it used to be back in OS1 4.8x . . . . PLEASE!

thedvs01 wrote:MIDI Layers for pads

you assign a group of MIDI notes, so that you can assign one pad to play a chord

YES i'm dying to have this feature added. i was so disappointed to see that you can't do this with the simult pad feature. i think it would be trivial to implement this and very useful/inspiring.