JJ OS Feature Requests (ARCHIVE)

Redsox00 wrote:They should implement Sample-Cycling Feature like the "5000" has..

Example: (http://www.youtube.com/watch?v=OHvc_6yKE6A)

This shouldn't be anything too difficult to add. I would like it to be a able to cycle thru 8 or more sounds.

anyone here with me?

This can be done by cycling through NDC chops by using the Q-Link slider, but we have been requesting an option to link the LFO to the Q-Link slider, this way it would be done automatically.

there have been a few requests for LFO rotating chops/slices in NDC samples, if this feature gets implemented it would be better if the LFO could be assigned to each pad separately because if different pads have NDC samples with different amount of slices it would represent a problem.

i.e.: LFO is linked to Q-Link slider which is linked to CHP-TRK. The min value is 0, max value is say 12, so the LFO rotates through slices 0-12 of all pads in the track. If all pads have NDC samples with 12 slices assigned then it's ok, but if some have more than 12, then we have a problem, so the solution would be to have each pad have it's own LFO-CHP-rotation, maybe something like this:



when you highlight the NDC field and press window, the MPC will let you set the min-max values.

astronaut wrote:there have been a few requests for LFO rotating chops/slices in NDC samples, if this feature gets implemented it would be better if the LFO could be assigned to each pad separately because if different pads have NDC samples with different amount of slices it would represent a problem.

i.e.: LFO is linked to Q-Link slider which is linked to CHP-TRK. The min value is 0, max value is say 12, so the LFO rotates through slices 0-12 of all pads in the track. If all pads have NDC samples with 12 slices assigned then it's ok, but if some have more than 12, then we have a problem, so the solution would be to have each pad have it's own LFO-CHP-rotation, maybe something like this:

when you highlight the NDC field and press window, the MPC will let you set the min-max values.

I dont get this? ok im on my first coffee today but this post has done my head in. No offence astronaut intended, I am just not sure what you mean. Are you requesting the LFO to trigger different chops? Or are you requesting the LFO to be in time? or both? or what? see, Im not sure. I dont like the idea of using LFO to trigger chops, that is what sequencer is for. You can set different LFO settings for everychop in the NDC made program, and i believe they are in tempo ie set LFO rate to 0.48 and it is half beat sweep.

astronaut wrote:

Redsox00 wrote:They should implement Sample-Cycling Feature like the "5000" has..

Example: (http://www.youtube.com/watch?v=OHvc_6yKE6A)

This shouldn't be anything too difficult to add. I would like it to be a able to cycle thru 8 or more sounds.

anyone here with me?

This can be done by cycling through NDC chops by using the Q-Link slider, but we have been requesting an option to link the LFO to the Q-Link slider, this way it would be done automatically.

^^wondering same thing as bliprock. I agree that it would be cool to implement sample cycling feature similar to how the 5000 has it, but I'm not sure about the lfo stuff.

the LFO is just one way to cycle through chops, it does not necessarily have to be done using LFO.

bliprock wrote:I dont get this? ok im on my first coffee today but this post has done my head in. No offence astronaut intended, I am just not sure what you mean. Are you requesting the LFO to trigger different chops? Or are you requesting the LFO to be in time? or both? or what? see, Im not sure. I dont like the idea of using LFO to trigger chops, that is what sequencer is for. You can set different LFO settings for everychop in the NDC made program, and i believe they are in tempo ie set LFO rate to 0.48 and it is half beat sweep.

It's about the LFO choosing a different chop/slice every time you hit a pad. It could of course be implemented in a simpler and more elegant way, without the need to use the Q-Link slider or LFO, just a separate option that pays a different chop every time you hit a pad.

Right now I'm using my Yamaha Rm1x sequencer that plays a midi loop with CC messages that go to the MPC1000 to the Q-Link slider which in turn is linked to CHP-TRK function, so the CC messages from the Rm1x are constantly changing which chop of a NDC sample is played every time I hit a pad on that track.

So for example I use 4 pads on a track, each pad has a NDC sample assigned to it, each of these samples is divided into 8 slices. Now, I have the Rm1x play midi CC messages that rotate the slices, so every time I hit a pad a different slice plays. It's a kinda of a round robin, has been discussed here often. Now, the problem comes in if one of the 4 pads has an NDC sample with less than 8 slices, say 4 slices, because if you hit the corresponding pad at the time when the Rm1x CC message chooses slices 6 you get unexpected results.

In any case, I think you should just try playing around with the Q-Link chop function to see what I mean. I'm probably making it look too complicated, but it ain't.

...

p.s. I use NDC to split a sample into 32 chops (since it can only do 32), and then the SLICE function to adjust the chops.

cyrus wrote: I agree that it would be cool to implement sample cycling feature similar to how the 5000 has it,

I think the cycle function seem to be less interesting when you have 3 layers instead of 4.

le rat wrote:

cyrus wrote: I agree that it would be cool to implement sample cycling feature similar to how the 5000 has it,

I think the cycle function seem to be less interesting when you have 3 layers instead of 4.

I think if we had both layer play back mode "cycle, random, velocity" like the mpc5000 plus "chop play back mode", 1 layer would be ok sacrifice. in essence if you did this (see below) you'd get 3 layers to cylcle through, and each layer could have potentially 32 chops to cycle through. thats alot of friggin randomness to really really get some expressive layering going.............not to mention combining it with simult.




like this:

Pad layer "play mode" like the mpc5000 - we'd get new button F5, and a new dialog box when pressed:

http://imageshack.us/photo/my-images/707/playmode.jpg/


dialog box when "play mode" is pressed F5:

http://imageshack.us/photo/my-images/41/playmodedialog.jpg/


#################################################
#################################################

#################################################
#################################################


Then also add "chop play back mode". in the chop column you could select chop number, random, cycle. if you opened window when value was highlighted you get new dialog box where you could choose play back type and the chops to cycle through.


Chop play back:

http://imageshack.us/photo/my-images/641/randomchop.jpg/



Dialog box for chop play back:

http://imageshack.us/photo/my-images/8/chopmode.jpg/

@cyrus

+1

Hopefully JJ sees your post soon and starts working on the implementation asap.

Free running LFOs that are not initialized each time a sample is triggered. Could for instance be used for less static hihats (modulate pitch, filter or something slightly).

le rat wrote:

bliprock wrote:Please please please can i request that the end point stays highlighted in the trim window when retriggerring sample.

Hit pad 4 or pad 8 (note on or one shot behavior) if you want to stay on the END parameter.

It's disconcerting in comparison with old OS but I got slowly accustomed to.

Peace

yeeeha le rat, its always really dumb things like this that throw me... i updated a few times and was a bit confused, and swear it did it, then i forgot how i did it, then i was lazy and didnt really try hard enough hence dumb question...works a treat.

astronaut wrote:
It's about the LFO choosing a different chop/slice every time you hit a pad. It could of course be implemented in a simpler and more elegant way, without the need to use the Q-Link slider or LFO, just a separate option that pays a different chop every time you hit a pad.

Right now I'm using my Yamaha Rm1x sequencer that plays a midi loop with CC messages that go to the MPC1000 to the Q-Link slider which in turn is linked to CHP-TRK function, so the CC messages from the Rm1x are constantly changing which chop of a NDC sample is played every time I hit a pad on that track.

So for example I use 4 pads on a track, each pad has a NDC sample assigned to it, each of these samples is divided into 8 slices. Now, I have the Rm1x play midi CC messages that rotate the slices, so every time I hit a pad a different slice plays. It's a kinda of a round robin, has been discussed here often. Now, the problem comes in if one of the 4 pads has an NDC sample with less than 8 slices, say 4 slices, because if you hit the corresponding pad at the time when the Rm1x CC message chooses slices 6 you get unexpected results.

In any case, I think you should just try playing around with the Q-Link chop function to see what I mean. I'm probably making it look too complicated, but it ain't.

...

p.s. I use NDC to split a sample into 32 chops (since it can only do 32), and then the SLICE function to adjust the chops.

I use mpc as master sequencer so is the opposite workflow but jjos has opened up the mpc as a slaved device like the way you have used it in your example. but first, I would be surprised if you need more than 32 chops so why slice more?? SO i remade your idea, and use midi note not cc to trigger pad....this then enables realtime cycle of sample via qlink slider as it is retriggered via yor Rm1x sending midi note message for the pads being used, but it seems that you can send the right cc to control qlink slider, and then cycle chops . I dont know which one your using and i would need to look up manual. So if you have uneven chop counts from triggering different lengths then you simply send the right cc data on that midi cc number to trigger sample chop number to make it even. So find cc chanel number then send the data on that cc chanel to the corresponding chop number on that pad. So just to recap. midi note=pad trigger, then cc chanel number gives you the mpc qlink slider control, but not the actual midi data that controls that control (the qlink in this instance). get it?..then data on that midi cc number (0-127) will then control the chosen parrameter of the midi cc chanel. so send data 0-1 on midi cc#? (qlink slider cc) and it should go to first chop. send data of round (125-127) should give last chop. Actually i have not bothered to really suss out midi cc's for mpc as i use cc's for synths and mpc is master so all ccs are for synths ect and not controlling mpc.

bliprock wrote:

le rat wrote:

bliprock wrote:Please please please can i request that the end point stays highlighted in the trim window when retriggerring sample.

Hit pad 4 or pad 8 (note on or one shot behavior) if you want to stay on the END parameter.

It's disconcerting in comparison with old OS but I got slowly accustomed to.

Peace

yeeeha le rat, its always really dumb things like this that throw me... i updated a few times and was a bit confused, and swear it did it, then i forgot how i did it, then i was lazy and didnt really try hard enough hence dumb question...works a treat.

Haha I rather say that there are no dumb questions, only dumb answers

By the way here is the "detailed" explanation of pads behiavor in TRIM mode.

Notes
PAD9-PAD12 work, as shown in the following figure.


If PAD1-PAD4 is pressed, a sample will be playback by NOTE ON.
If PAD5-PAD8 is pressed, a sample will be playback by ONE SHOT.
A sample will be reverse-played back if PAD3 and PAD7 are pressed.
Moreover, a start or an end point can be adjusted, carrying out audition, if a DATA wheel is turned pressing a pad (PAD1-PAD4 and PAD9-PAD12).
If PAD1, PAD2, PAD5, PAD6, PAD9, and PAD10 are pressed, cursor will move to St field.
If PAD3, PAD4, PAD7, PAD8, PAD11, and PAD12 are pressed, cursor will move to End field.
If PAD9-PAD12 and PAD14-PAD16 are pressed, the waveform of a play portion will blink.
It works similarly on the screen of F5 (CHOP).
However, there is no reverse playback of PAD3 and PAD7.

http://www7a.biglobe.ne.jp/~mpc1000/os2xl/trim.htm

What I really miss is an intelligent function which would "reset" a loop when you change its end point.

That cycle feature on the MPC5k looks useful! Cycling through your NDCs would be the feature to implement first, I think. Yeah, cycling through layers and NDC would be nuts, but auto cycling through NDCs would get you 90% of the way there.

Using LFOs instead of note repeat and tempo to cycle seems weird. I'd have a hard time imagining how a triangle would work different than a sine.

I'd like to see LFOs send out MIDI CCs. This'd be pretty amazing. Playback samples on the MPC and LFO control external hardware or software with the same pad.

AUTO-LOAD METRONOME samples.

right now you need to have the metronome samples included in an auto-load program or you gotta do it every time you restart the mpc.