Hi All,

I've attached a patch that I constructed that converts a MIDI continuous controller stream of 1~127 into much higher resolution output (currently set to 127^2 steps). It basically ramps between one MIDI number to the next over a time period specified by the amount of time that has elapsed since the previous MIDI number was passed. Of course it still restricts you from stopping on a number in an range between two MIDI numbers, but at least it allows that range to be swept through.

For example, if you want to use a controller to sweep through frequencies from 20Hz-20,000Hz, if you use a MIDI controller normally it would pick out only 128 discrete frequencies over that range and step from one to another like stepping stones. But using this patch, if you move the controller from, say, 34 to 35, the result would be a smooth sweep through frequencies of about 5300Hz to 4470Hz over the time period equal to the time taken to change from 34 to 35.

Unfortunately, the major limitation is that the patch only knows the time period at the moment you reach the new number, so the ramp only starts by the time it should have finished. This makes it impractical to use for slow sweeps, but you could use a separate controller for these slower movements (one that is much lower geared).

Any suggestions for improving or expanding the patch would be welcomed.

I know that pitch bend already performs as a 14-bit controller, but I don't want to be limited to having only one hi-res at a time (I only have one pitch bend wheel!)

Cheers,
Brett

http://www.pdpatchrepo.info/hurleur/High_Resolution_Controller.pd

really good thinking. simple but very effective idea. will definitely incorporate this into my own setup.

my revised edition attached.

(as a rule, don't use gui objects (liek the gui bangs and number boxes) in your patches unless they are necessary for controlling the patch.)

http://www.pdpatchrepo.info/hurleur/High_Resolution_Controller2.pd

thanks. your revised edition definitely seems to run more smoothly. I'll be taking this home with me! but tell me, what is the purpose of the '50' message on the Sel 1 route - is it to ensure a minimum ramp time of 50ms?

As for the GUI, those were just for my own monitoring purpose - I'm pretty new to programming and just getting to know the objects, so helps to see what's coming out of what! next time I'll slim it back down before posting.

i found a little glitch that meant if you moved the midi controller only 1 unit, then waited a few seconds and moved 1 unit again, then the [line] was taking a few seconds to get up to the next value.

so, i added a mechanism to reset the line to 50ms if you don't touch the controller for more than 2000ms.