Re: TouchOSC / Bidule / Plugins HELP...!

[Simeon Harris <simeonharris40@googlemail.com>]

yes, i thought it would be very similar to parameter linking and tried everything you suggested....without any success whatsoever.

anyway - assuming you've got the target parameter sorted, how does bidule know which of the faders in touchosc is supposed to be controlling it?

i've given up. my brain hurts. i'm going to go and watch The Daily Show which i recorded last night. i may even have a beer.

sim

On Sat, Dec 11, 2010 at 8:08 PM, andy butler <akbutler@tiscali.co.uk> wrote:

Gmail wrote:

Thanks andy, I already read this. It's only half the process.

I'm afraid I don't have any incoming Osc to test.

It seems very similar to the param linking tho'.

You're supposed to paste the o/c address into one of the osc bidules ( doesn't say which one)

that would be Osc Extractor,
there's only 2 Bidules which accept the address, and the other is for *sending* OSC

and them connect the bidule ( doesn't say how or where to)

Tools> Osc Server
then click the Address space tree to find the destination Bidule.

I've got a hunch you don't need *both* of those steps, and you can either select the target parameter from Osc Server OR
use Osc Extractor with the address value.

OR, a third way if you wanted midi, just use  an Osc Midi bidule and link it from the Osc server.

Sim

Sent from my iPod

On 11 Dec 2010, at 18:59, andy butler <akbutler@tiscali.co.uk> wrote:

OSC Server Implementation
First to enable the OSC Server part of Bidule, you need to go the OSC Server dialog by selecting OSC Server from the Tools menu. You need to select a port for Bidule to listen for messages (Note: you might need to change your firewall software settings to allow incoming messages to that port), the default one should be fine but you can change it. Every parameter of every bidule that is available for parameter linking is also available for control through OSC. Each parameter has an address to receive values, the address is built automatically from the location and name of the bidule as well as the parameter name. The location of a bidule is the "path" to it (look at the bottom left of the patchbay when you're inside a group to get the idea) so for example a group named Freeverb in the root of the layout would be /Freeverb, now if we wish to control the mode of the effect, the address would be /Freeverb/Mode. Take note that some characters (like spaces) are reserved and this might change the "expected" address so your best bet is to look into the OSC Server dialog and see the name that is there. Each parameter expect to receive values within its range (click the Params button on the bidule's window to see them). Parameters that are a drop down box with a list of choices will also accept a string representing an available choice. These two address also exists: /play : to start/stop the processing (parameter: 1 or "true" to start audio, 0 or "false" to stop it) /open : force the loading of a .bidule file (parameter: the path to the bidule file on the machine)
Simeon Harris wrote:

cool!
  Jeff
  Oh, and the next release of Mobius will have built-in support for
  TouchOSC without
  needing a converter.