well having spent all day messing with touchosc and having no joy and no response from the plogue forum, i gave up and downloaded ITM midiLab. had it working in 10 minutes. midilab is free, so you can do a basic test to see if it works and then they have more specialist apps with more features for the same price as touchosc. might be worth a look, per.
simOn Sat, Dec 11, 2010 at 1:42 PM, Simeon Harris <simeonharris40@googlemail.com> wrote:
ok will do per.
i'll report back my findings
simOn Sat, Dec 11, 2010 at 1:06 PM, Per Boysen <perboysen@gmail.com> wrote:
On Sat, Dec 11, 2010 at 1:44 PM, Simeon HarrisI suppose it is a similar procedure as when converting MIDI to Bidule
<simeonharris40@googlemail.com> wrote:
> the problem i'm having, is that i have no idea ho to attach a plugin
> parameter to an OSC message. i see in the OSC server screen, that each
> parameter has an OSC address, but i have no clue what to do from that point
> on.
control data; you cable in some "converter object" between the OSC
input and your Bidule stuff. You may have to do some scaling as well
to match the range of the target parameter. I guess someone at the
Bidule forum would be happy to answer that! I had a lot of help from
those guys when building my own Bidule environment.
Please post your findings here! I just replaced my crappy old Ericsson
with an iphone and thinking of replacing my Faderfox hand mixer/button
pad with the iphone.
BTW, speaking about wireless, I read up on user reviews of the Keynote
app (since I do some speeches with big screen presentations) and one
guy there sad that Bluetooth is too slow for real-time control. The
Keynote app works over wifi which he thinks is better/faster. I still
may go with Bluetooth if possible since I can plan it to only use it
for stuff like changing preferences rather than direct musical looping
action control.
Greetings from Sweden
Per Boysen
www.boysen.se
www.perboysen.com
www.looproom.com internet music hub