![]() You will need to repeat operating all the controls and then switching to Audulus and back if you reload the patch or switch patches. Since TouchOSC is sending MIDI to Audulus, multitouch is fully supported. You can then switch back to TouchOSC and you should be able to control your patch. Audulus will not initially process the MIDI commands while it’s in the background (hopefully Taylor will fix this). Switch back to Audulus to allow Audulus to recognize the MIDI inputs. This will send MIDI to Audulus for each control. ![]() You now need to operate all of the MIDI controls (select the pads, turn up the knobs etc. Select the Audulus 1 layout and make sure that CoreMIDI is enabled and the Audulus slider is on. To control Audulus on the iPad make sure that Background Audio is on in Audulus (wrench icon). Use the controls in the attached Audulus patch as required to create your patch. To use, install the attached Audulus 1.touchosc layout in touchOSC following the documentation. I chose to make the toggles knobs rather than triggers in Audulus, although they are fully on or off. I then created an Audulus patch with corresponding controls. I created a simple controller with 8 triggers (pads), 4 toggles, 6 rotary knobs, five vertical faders, a pitch bend and a modulation slider. It occurred to me that it might be possible to use it as an alternative control surface for Audulus. Although it is primarily used as a DAW remote, it is a quite capable MIDI controller. For those of you that aren’t familiar with the app, TouchOSC is an iPad based MIDI and OSC control application. I ported this over from the old Forum because recently acquired TouchOSC. If you have a Chroma, you owe it to yourself to check out the Rhodes Chroma website and join the email list.This is not, strictly speaking, hardware, but it seemed the best fit. The screens show all editable parameters of the Rhodes Chroma. Note you do need the CC+ upgrade on your Chroma with MIDI set for Expanded Mode MCM. For OSCulator, you just need to open the template, click on the Settings icon and set it to use whatever MIDI out you plan to hook into your Chroma. For TouchOSC you just need to drop the mapping in the templates folder and sync to your iPad. The two templates in the share above are for TouchOSC and OSCulator. To translate these messages to MIDI CC you need something like OSCulator. TouchOSC only transmits Open Sound Control messages. One is for TouchOSC and one is for OSCulator.įor those new to TouchOSC and OSCulator, TouchOSC provides a JazzMutant Lemur-like control interface that is completely configurable. Update: see this post for an editor that does not require The Missing Link.įor The Missing Link you can find templates here. Below is a shot of the iPad on top of the Chroma. This video is not a performance and is only meant to show a little of what the Rhodes Chroma TouchOSC editor is capable of." See the screens above for reference. ![]() I then enable Wave B followed by applying various modulations to filter and pitch for both. I then show Wave B is inactive by attempting to adjust its pitch which does nothing. In the beginning I adjust the pitch for Wave A which is active. Īs for this video, the Chroma starts with an initialized patch which only has one "Wave/Patch" active. There is too much to go into here, so check out the excellent Rhodes Chroma site for more. ![]() The routing is not fixed and is very flexible, meaning you can use modulation sources on B with A and vice versa. On the Chroma, each of two oscillators, Wave A and Wave B have corresponding filters, Filter A and Filter B, LFOs called Sweep A and B, and so on. On most you have two oscillators that are routed through a filter with shared modulation sources such as envelopes and LFOs. "The Chroma has a slightly, conceptually different architecture than most analog poly synths. ![]()
0 Comments
Leave a Reply. |