#Update touchosc from osculator update#
#Update touchosc from osculator Patch#

By pressing a fader '/2/fader1', in which case there is a variable argument (note number).Ģ.

#Update touchosc from osculator update#

update the text labels with a new text value.ġ. The general idea is to put in only one place everything that is related to a single function. Sorry if it was not very clear, here is a more detailed explanation. There might be a possibility to help with the scaling of the Note Params but first I have to check that it will not create a problem with the way Kyma notes are represented. I know that in the case of MIDI this is not convenient, this is why a multiplifier is implicitely applied for the scalings of the MIDI CC messages (some other MIDI messages do apply as well). Most of OSCulator events are ranging from 0.0 to 1.0, which is convenient when you are working with several OSC devices. Some early implementations of mrmr were using an integer from 0 to 1000. The 'standard' range for numerical OSC message is a float going from 0.0 to 1.0. You can attach your files on this thread, or you can carry on this discussion by email if you prefer (camille at osculator dot net).Ībout the scaling of vs :Īt the time OSCulator was designed, it was supposed to work with a Lemur, or a Wiimote. I have experimented with a solution, and found it was working in some sense, but of course your could be totally different. I would like to help, but it is a bit difficult to anwser your question without having access to your oscd and touchosc files. I send it 64 and the fader shoots to the very top. In addition, rather than send a value of n(1/128) to the faders (where n = the MIDI note number I want) it would be much easier to send it the direct number 0-127 but even if I set the input scaling of the faders to 0-127, they still seem to respond on the basis 0-1. However, the value doesn't seem to get passed on to the buttons as they still output their 'old' pitch. That works in so faar as the faders move. However, I want to create a set of preset 'pitch sets' such that when I hit a button called 'Pitch Set 1', it sends each fader an OSC Routing fixed to the correct value for a set of pitches I want to use (say C Major). I have a set of buttons sending a 'MIDI Note /w params', each taken from a corresponding fader sending 'Note Param: Pitch', such that I select the notes I want on the faders, and then trigger them using the buttons. This approach also has the added bonus of teaching you a bit about the live.remote/object/observer/etc objects (if you don't already know about them) which is awesome, cause they're pretty darn cool.My set up is iPad -> TouchOSC -> OSCulator -> Logic I wish I could remember what the names are so I wouldn't sound like such a space cadet but it's a lot easier than it may seem. But the answer is that it's easy you just have to read about the max objects who's names start with live.(name) and are related to live.remote. One of those max4live objects lets you scroll through controls by id or something like that so you just make a counter and metro that bangs every millisecond (you might have to go a tiny bit slower just so all your stuff doesn't crash at once) and just get it to find the current value of that slider/know/whatever and resend it to itself.Įrm, so you want to use liveobserver (I can't remember what it's called but it's something like that).

#Update touchosc from osculator Patch#

You can make a quick max for live patch that uses liveremote or liveobject to quickly scan through every possible parameter and send a 'bang' to it (this would have the same effect as quickly touching all the knobs and sliders and buttons etc).