Tag Archives: MIDI

TB Midi Stuff

One iOS control surface that’s getting too little love in my poll on the left is TB MIDI Stuff.

It sends and receives OSC and MIDI, including NRPN, so you can do 14 bit high resolution MIDI. It even does bi-directional Sysex. The editor is built in so there’s no need to edit your layout on a computer then sync – add, delete and modify controls and pages right on your device. There are some built in control surfaces like a standard keyboard (with arp!) and an MPC type drum pad and many other editable templates.

Get it here for only $4.99 – daaaaamn that’s cheap – and I guarantee you will find uses for it. It’s worth that coffee-and-muffin price just for the default keyboard and MPC and the Wicki-Hayden templates, to say nothing of the custom templates you can put together quickly and easily. Oh, did I mention there are built in scales and customizable scales you can play from ribbons and other objects? Well, there are. It’s a Swiss army knife of MIDI features for a toothpick price.

Finally, here’s a video of one of the 1.x versions of TB MIDI Stuff (2.0 was recently released)

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.

Mirage 1.9.6.1

Here is the new version of Mirage featuring OSC control mappings for the awesomeĀ Konkreet PerformerĀ iPad control surface.

Note: Mirage works just fine on its own without KP too, just map some MIDI controllers or use a mouse. A TouchOSC template will follow

Update: Download link now goes to version 1.9.6.1 which is the same as 1.9.6 except the Mirage instrument header is set to visible, making it easier to get into instrument properties and change the number of voices. It arguably looks “neater” with the header bar hidden but isn’t as noob-friendly.

This version is free for owners of previous versions. Download here – your existing password will open the archive.
The new version includes extensive feature enhancements and numerous bug fixes, and carefully thought out, tested and integrated Konkreet Performer mappings. Mirage snapshot recall will also recall node positions and transmit them to Performer on your iPad.
mirage 196 diagram
This time out the sample material is mostly one-shots to work in conjunction with the added pitch correction. Adding longer phrases and snippets of songs works well too but with the one-shots you can do something more deliberate and compose a part for a pre-existing track. I find with long phrases there are only a couple of note combinations that work well and what you come up with will have a mind of its own and suggest its own composition.There are a couple of trashed piano field recordings in here that rattle beautifully – nothing like hitting the harp directly on a piano that’s sat out in the weather for a few seasons.

To use Konkreet Performer with Mirage, set up a 4 node layout with visible node labels, activate trigger hold, and set inertia to 30. When touching and moving the central node, the other nodes will slowly track and follow, creating a sort of manual LFO that slowly snaps back to the snapshot’s original settings.
The Mirage package includes a separate translator ensemble that can be run in Reaktor standalone, parallel to a host using Mirage as a plugin, to translate Konkreet Performer’s native OSC signals to MIDI. Use MIDI Yoke on Windows or the IAC driver on Mac to reroute MIDI from the translator to your host.
Mirage is $15 and a license can be purchased here:Mirage Add to Cart

Or, save $$ and buy the sampler pack which includes Loupe and ParamDrum.

Any questions? Ask away!

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!

download

Using Konkreet Performer and TouchOSC in a host?

Spending some time with Lemur since its launch, one of the neatest features is the ability to script 14 bit MIDI, to give higher resolution control over various parameters. This is essential in instruments like Loupe and Mirage, where regular 7 bit MIDI just doesn’t give the fineness I want to set loop points. It’s too steppy and jumpy.

I’m working right now on creating Lemur templates for my ensembles, but I’d also like to do version for Konkreet Performer and TouchOSC. This would involve running a Pure Data patch and rerouting PD’s output, which is an extra step, but it would enable fine grained control within a host. As you may have noticed, Reaktor’s OSC capabilities are missing in the plugin versions (for the love of God, why?!)

Anyhow, vote in the poll above if this extended capability for Konkreet, TouchOSC and my instruments interests you.

Update: I’ve hit a few performance issues with Pure Data so I’m going to do the OSC translator as a custom Reaktor patch. Here’s what you do: run Reaktor standalone alongside your host with the translator patch, and redirect its MIDI output to your host. This is easy on Mac because programs can share a core audio interface, but a bit sticky on Windows where ASIO access is exclusive. One solution could be to redirect Reaktor’s output to a different sound interface, or set it to use the DirectX driver. I’m open to suggestions from Windows users.

So, how about it – Reaktor as a translator?

Update 2: things are coming together…