data thinning and feedback with OSC and MIDI

Aug 30, 2011 at 6:23am

data thinning and feedback with OSC and MIDI

after many years away from MAX I am back! Yay. Unfortunately somethings I am finding very hard and hopefully you can help.

two issues

how do I thin a stream of data so that numbers do not repeat sequentially? For example when using [scale 0. 1. 0 127] to thin OSC controllers I get a lot of the same int over and over such as 22 22 22 23 23 23. I want to thin this so it would only be 22 23. I am mostly controlling MIDI gear and I don’t want to mess up timing by sending the same controller value over and over.

second issue
when using TouchOSC to control a piece of MIDI hardware (Eventide H7600) I am getting feedback as the Eventide sends its on screen values out as CCs when they are changed. Or maybeTouchOSC forwards its input to its output? This I am very confused about. Somewhere I have feedback between TouchOSC, MAX and the H7600. Are there any example patches that show how to deal with MIDI devices that feed back? I notice a bunch of gates in the TouchOSC examples that might be for this but they don’t seem to have any control other than on screen toggle boxes.


Aug 30, 2011 at 7:48am

issue 1: use [change] (or [zl change] for lists
issue 2: I’m not familiar with your system, but when you solve issue 1 this might be solved as well.

Aug 30, 2011 at 1:07pm

I used TouchOSC directly to my Max patch, with visual updating from Max back to TouchOSC, no feedback—apparently it only sent the data when the iPhone screen itself was tapped. Not sure if this has changed though. And yes, I don’t think the gates/toggles in TouchOSC are for this, they’re just general-purpose toggles.

When your Eventide sends out the CC values, is it sending back into your patch? And then these are sent to TouchOSC? If so, you’d just need a “set $1″ or [prepend set] before they go to TouchOSC, this way you can see the current values, but they won’t activate the feedback loop.

Sep 1, 2011 at 8:26pm

thanks for your help, [change] was the missing piece. After a little sleep things made a lot more sense and I adjusted my routing to prevent feedback.

I am very glad to be back into MAX – feels very fulfilling to be able to make custom music tools without spending more money on my modular :)


You must be logged in to reply to this topic.