Feature Suggestion: Transpose?

i kinda meant, just the midi note number being increased/decreased by the transpose value. this explains why i thought it would only work for midi tracks, as they would more likely be triggering an auto chromed program, or a synth, which could handle the changing note numbers. changing the note numbers around on drum programs would make, for example, the kick transpose to a hi hat for example. could be cool for some crazy sh!t.

yeah its funny that there are a few more choices than it might seem at first for how a transpose could work.

from this thread, i see the following issues:

-global sequence transpose vs. per-track transpose
-transpose of only 'midi' tracks vs. 'drum' tracks also
-transpose of drums/samples by changing pad# vs. changing sample pitch

All the options are interesting. If we are going to ask JJ, we might as well get straight what we want.

However my vote (and probably the easiest to code properly) would be for:
-per-track transpose
-transpose either midi or drum tracks, as desired
-transpose only steps up/down the padnumber, not the sample tuning...

...at least to start.

sleepersriddle wrote:-per-track transpose
-transpose either midi or drum tracks, as desired
-transpose only steps up/down the padnumber, not the sample tuning...

...at least to start.

exactly what i would like. although i think steps up/down the note numbe rather than pad number would be better, as pads can be assigned to any note numbe, and things might get confusing.

true... i was probably just worried about what would happen if the (notenumber+1) wasn't actually assigned to a pad originally. what do you think? do we want it to actually 're-assign' notes<-->pads?

Mr modnaR wrote:... although i think steps up/down the note numbe rather than pad number would be better, as pads can be assigned to any note numbe, and things might get confusing.

yeah totally , but i use a "chromatic layout" even for drum maps a lot,because then if i want to jam beats from my kybd, i can go up thro' the pads 1-2-3 etc. otherwise (and i hate this) if i forget to format/chromatic # the programs before i fill em full of samples, then i cant transpose things accurately - simply cos theyre not in an order i know well (the akaimpc default # layout baffles me....but doods, these above options your on about would be cool for me, i can work most improvements to an advantage! : )

sleepersriddle wrote:true... i was probably just worried about what would happen if the (notenumber+1) wasn't actually assigned to a pad originally. what do you think? do we want it to actually 're-assign' notes<-->pads?

i think it would be best to just be a modifier to the note number being played by that track. for me personally, i would use this for chromatic programs and external synths only, so there would be no problem with there being no assigned pads. i think this would be the simplest to implement option, and would hopefully create less chance of code problems donw the line.

sleepersriddle wrote:true... i was probably just worried about what would happen if the (notenumber+1) wasn't actually assigned to a pad originally. what do you think? do we want it to actually 're-assign' notes<-->pads?

i think it would be best to just be a modifier to the note number being played by that track. for me personally, i would use this for chromatic programs and external synths only, so there would be no problem with there being no assigned pads. i think this would be the simplest to implement option, and would hopefully create less chance of code problems donw the line.

Mr modnaR wrote:

sleepersriddle wrote:true... i was probably just worried about what would happen if the (notenumber+1) wasn't actually assigned to a pad originally. what do you think? do we want it to actually 're-assign' notes<-->pads?

i think it would be best to just be a modifier to the note number being played by that track. for me personally, i would use this for chromatic programs and external synths only, so there would be no problem with there being no assigned pads. i think this would be the simplest to implement option, and would hopefully create less chance of code problems donw the line.

to clarify if im understanding u::
with your preference it would _only_ work on external midi?

or am i missing something; changing the 'note number' would not affect internally-sampled chromatic programs, would it? (I would think u have to change pad or tuning for that to work.)

no. midi note numbers are assigned to pads in the program screen. if you assign them in order, then run your hand up an keyboard controller, the notes will play in sequence chromatically. if you leave them all jumbled up, running your hand up a keyboard wil still play midi notes in order, but because the pads aren't ordered chromatically, they wil play out of order. when i say the transpose feature would merely be a modifier for the note number being sent from that track, i mean: if a C3 is being played on the track, and the transpose value is +3, then a D#3 will be sent out. this can be sent anywhere, internal sampler external synth whatever. all i was saying was that i would use this transpose feature for chromatically assigned programs and external synths, so, modifying the note numbers as they come out of the sequencer's tracks would move the 'percieved' note number up or down the scale, and this would work perfectly for external synths and chromatic programs.

sorry for the long and probably unclear explanation....

sleepersriddle wrote:but if transpose was on a 'per track' basis, it could be cool to have the option of transposing drum tracks (with result being pitch goes up) and you could at least try it... hmm..

i would like that per track scenario.

Mr modnaR wrote:
sorry for the long and probably unclear explanation....

modnar - u nailed it, thanks. its hard typing theory into words esp. when its flying off the top of yer head, (speaking from personal perspexives)

Hmm, i'm just wondering if so much time and effort should be devoted to something that is external from the MPC. I'm thinking focus should be kept on working on what we have with the MPC rather than trying to "give wings to the buick" by making a bunch of external features that may be difficult to implement, redundant, or not used very often.

why do you say it's external to the mpc? this will work perfectly well with programs in the mpc.

Hmm, I guess there was a misunderstanding about the transposition from my perspective. You must be talking about transposition of notes instead of pitch%?

Fully supportive of any idea for the MPC though! Nice to have some thoughts on ideas for the 1000 and JJ's never ending possibility generator for the MPC.

The MPC has always been designed and used to sequence external MIDI gear, as one of its most important functions.

More like giving tires to a Buick.