Tag Archives: OSC

The Science of Surfaces

Hey kids, there’s a new poll on the left. Please vote and select multiple options if you use multiple touch surface apps. 

UPDATE: the built in Blogger poll is broken and I’ve switched to a widget from pollcode.com. Apologies to anyone whose votes were lost… it kept resetting to different numbers of votes. (if this is actually someone messing with me through a Blogger security hole, well played sir, by which I mean, get a life šŸ˜‰


My experience of touch surfaces as controllers is that they shouldn’t be clones of what they’re controlling. I admit that there’s a certain cool factor in having a Lemur or TouchOSC template that allows full access to every parameter on a Reaktor instrument’s GUI. And in some cases, that can add to the playability and usability of the instrument.

On the other hand, though, what’s the point of replicating an instrument GUI? Generally speaking there will be too many controls, and they will be too functionally and ergonomically diverse to provide a fluid performance experience.

This is why I keep coming back to Konkreet Performer. It doesn’t attempt to provide the ability to mimic a GUI. What it does, and does well, is translate touch into control in ways that are both simple and complex, in the right ways – simple in that setting up a layout is easy and direct – and complex in that parameters can describe not just touches and movements, but the relationships between different touches and movements. Unexpectedly cool things ensue.

This is not to say that I don’t recognize the relative strengths of the other touch surface apps – maybe this is just a personal preference and I simply prefer a simple touch interface that functions as an adjunct to a standard computer setup, rather than a replacement for it.

In the long run I’m pretty sure tablets and laptops will glom together in some form – if the Microsoft Surface doesn’t succeed then something eventually will and every Reaktor ensemble or synth plugin will be its own touch surface – a situation which will bring its own set of problems and solutions.

Anyhow, please vote in the poll on the left because I’m getting ready to launch a new instrument and I’ll take into account the popularity of the apps when designing controller mappings and templates.

OSC support in Reaktor plugin mode, at last!

 Reaktor update news! In the upcoming 5.8, which is now in beta, we will finally have OSC in plugin mode. That means connecting an iPad to our favorite ensembles directly with no MIDI translation layer. Fire up Konkreet Performer and map OSC parameters directly with Reaktor running in Logic, Reaper, Cubase, Ableton Live, whatever. 

I’m excited. Are you excited? If not I’ll be excited for you.

New and improved features:

  • Updated OSC Settings window
  • Improved handling of OSC and MIDI, enables fast and easy mapping of MIDI & OSC controllers to Reaktor ensembles in Play Mode
  • New OSC Array modules, for sending and receiving OSC messages in array format
  • OSC in plug-in mode
  • OSC learn feature now also implemented in Play mode
  • OSC activity indicator
  • Limits on the total number of OSC connections have been removed
  • Maximum numbers of ports for the OSC Send and Receive modules has been increased to 40
  • Improved sample management, including the ability to manage samples when in Play Mode
  • Various workflow improvements in the sample map editor
  • Selection of sampler module per drop down menu
  • Show sampler module in structure functionality
  • Mouse control fine tuning
  • Bookmark behavior for Screensets
  • Fixed sample rate per Ensemble
  • Various other fixes and improvements

Konkreet Performer OSC to MIDI translator

This is an expanded version of the specialized Konkreet Performer OSC to MIDI translator and visualizer I built for the latest version of the Mirage granular sampler. If you’re not familiar with Konkreet Performer and you have an iPad, you need to check it out because it is awesome.

One drawback of using KP with Reaktor is that KP only sends OSC, and Reaktor won’t receive OSC when running as a plugin. Hence, this ensemble, which can be run in Reaktor standalone and will re-route KP’s control signals as MIDI to Reaktor or other synths running in a host.

Instructions are included on a text widget in the readme instrument. This is a 1.0 release so please report any bugs in the comments!


First Lemur Template

All reety then, after buying Lemur for iPad the other day and sifting the PDF manual for the chunky bits, I spent a few hours today crafting my first Lemur template. It’s a hybrid OSC / MIDI creation that borrows the stock drum pads, adds a sustain latch, and also five bouncing balls with individually adjustable speeds, friction and scaling. 

The scaling turned out to be especially important, as setting the balls loose on their full range of travel then mapping them to Reaktor controls is a bit sloppy. So using the X and Y scale controls, you can specify a range of travel for whatever control you map them to. That way, you can specify that your filter cutoff stays within a useful range, or open it up to the full range of travel for crazy wildness.

The MultiBalls output both OSC and MIDI. The OSC signals look like /Multiball/X1 etc, and the MIDI CCs are in the range 17 to 26. There are X and Y lock toggles to make MIDI learn easier.

There are probably better ways to address the creation of variables and math formulas than what I’ve done here, but give me a break, this is my first try! If you’re a longtime Lemur demigod, I welcome your criticisms.

The HolyBallz template can be downloaded here. I’ll be adding templates more specific to my own ensembles soon.