Using native Logic OSC support with 3rd party plug-ins & new touchOSC maps

Question

Level 1

44 points

Using native Logic OSC support with 3rd party plug-ins & new touchOSC maps

Hi All.

Now that logic from 9.1.2 has native OSC support, I wandered if anyone has used it succesfully with their own customised touchOSC maps?

I'm not so interested in using touchsc as a transport/mixer for logic - which is what the default logic map that comes in touchosc s focused on, but more to control a few 3rd party plug-ins inside logic (FXPansion Geist & Strobe) - which would mean I need to create my own maps. It doesn't seem clear however if or how you can edit or use touchOSC maps which use the native OSC support bult into Logic

Anyone had any joy with this, or able top shed some light on possibilities & limitations?

Mac Pro 2.66 4-Core + 6GB RAM / MBP 2.4 + 4Gig Ram LP8.0.2 / Apogee Duet., Mac OS X (10.5.6)

Posted on Dec 29, 2010 5:34 AM

Reply

Answer 1

Dec 29, 2010 7:27 AM in response to A_Double__

Unfortunately native OSC support is not yet a user-accessible thing - you need the SDK in order to get under the hood. While not exactly rocket science, it's not for the faint of heart either... I'm trying to get a copy of the SDK to take a look. I'll let you know what I find out!

In the meantime, the "LogicPad" controller does a pretty nice job of mapping most 3rd party plugins to the iPad - have you tried it? I was pretty impressed that even parameter names show up...

Cheers,

Jim

Reply

Answer 2

A_Double__ Author

Level 1

44 points

Dec 29, 2010 8:59 AM in response to Jim Daneker

Gotcha, that's a shame. Thanks very much for for explaining.

The Logicpad looks great, but the default controls don't fit with with what I want to do with the 3rd party plugs - for geist for instance I wanted to have 16 pads, some sliders, buttons & also map the patch browser controls.

Cheers

Reply

Answer 3

Dec 29, 2010 9:26 AM in response to A_Double__

I hear you - and I really hope they open up the OSC implementation. I have a feeling it's not an easy thing to do, but it would be nice to have the option!

In the meantime, if your plugins are MIDI-controllable, it's really easy to create your own controllers in TouchOSC editor and then map them via OSCulator. I'm well on my way to a whole collection of controllers for popular sample libraries and a few synths/plugins 😉

Take care,

Reply

Answer 4

A_Double__ Author

Level 1

44 points

Dec 30, 2010 6:22 AM in response to Jim Daneker

Cool, I'll spend some time with Osculator, I already use Bomes midi translator when I use Ableton so it looks pretty similar - just seemed tidier if it wuld all be done in logic.

It seems to me plug-in developers could be missing a trick by creating & supplying OSCtouch maps along with their products... would deffo be a selling point IMO

Reply

Answer 5

Jan 6, 2011 2:24 PM in response to A_Double__

A Double! Ive been trying to do similar tasks, with FXpansion software as well , mainly cypher... Wondering how successful you have been so far, pm me and maybe we can trade layouts!

Reply

Answer 6

Jan 6, 2011 3:10 PM in response to MutualSon

Well guys, my plan to release 1 or 2 simple controllers has evolved into a full-blown product that's actually pretty involved. I needed something that would control all my major sample libraries and I figured a lot of other composers would benefit from something like that. It should be out within a few days; in the meantime, I put up a temporary page that should give you the idea:

http://web.mac.com/ppjmd/home/ipad.html

Cheers,

Reply

Answer 7

A_Double__ Author

Level 1

44 points

Jan 7, 2011 4:49 AM in response to MutualSon

Not yet, looks like Jim may be making our lives easier!

Reply

Answer 8

A_Double__ Author

Level 1

44 points

Jan 7, 2011 4:52 AM in response to Jim Daneker

Nice initiative Jim! (& lovely studio, I took a look at your site)

So your products will be the fruits of the SDK digging & using native logic suport? - or OSCulator reliant?

Reply

Answer 9

Jan 7, 2011 7:10 AM in response to A_Double__

For now they are OSCulator reliant, and that has some advantages: primarily that the user can easily remap anything that doesn't suit their needs. I've been using these for weeks and the combination has been rock solid so I wanted to go with it rather than wait for (and learn) the SDK.

The best part is that these bundles will include everything you need, including custom Kontakt multis, VSL matrix files and of course the OSCulator mappings - and building those may have caused carpal tunnel syndrome! Talk about a mammoth task... Anyway, the goal is for it to be an easy plug & play experience.

Trying to wrap up today or tomorrow - just waiting on some website reorganization...

Stay in touch!

Reply