Audiobus: Use your music apps together.

What is Audiobus? — Audiobus is an award-winning music app for iPhone and iPad which lets you use your other music apps together. Chain effects on your favourite synth, run the output of apps or Audio Units into an app like GarageBand or Loopy, or select a different audio interface output for each app. Route MIDI between apps — drive a synth from a MIDI sequencer, or add an arpeggiator to your MIDI keyboard — or sync with your external MIDI gear. And control your entire setup from a MIDI controller.

Download on the App Store

Audiobus is the app that makes the rest of your setup better.

Using OSC to Synchronise Mixer Faders with TouchOSC

digitalferretdigitalferret
in Loopy Pro

New to Loopy Pro, and am kicking my self for not looking at it earlier, it has just about everything I have ever wanted in a music production app and much more.

Was really fantastic to see that the MIDI Learn feature has the ability to send and receive, which means I can synchonise the faders on TouchOSC with the mixer faders in Loopy Pro, and this happens if I slide the fader on TouchOSC or if I slide the fader on Loopy Pro. Nice!

When I use MIDI, it all works perfectly, however when I use OSC, it seems synchronisation only occurs when I use TouchOSC to change the position of the fader on Loopy Pro. So with OSC it does not seem to work the other way around, even though all good with MIDI.

Any suggestions on trouble-shooting this? Has anyone go this to work with OSC?

I realise Loopy Pro has an awesome customisable UI, but TouchOSC provides an additional surface to use, and I can get quite funky with scripting also.

Comments

  • espiegel123espiegel123

    @Michael

  • digitalferretdigitalferret

    A few more technical details:-

    • I can get TouchOSC to work with OSC with another TouchOSC, and can see the receive and send messages, so do not believe this is a TouchOSC issue.
    • When I trace/log on remote iPad from within TouchOSC, I can see the OSC message sent, but nothing is received from the Loop Pro iPad.
    • When I trace on the Loopy Pro iPad using the Protocol App, I can see the OSC message being received from the Touch OSC iPad.
    • I used Wireshark to packet trace on a Window PC with TouchOSC and cannot see any OSC packets from the Loopy Pro iPad in response to OSC packets from the Windows TouchOSC or when using OSC mapped UI elements on Loopy Pro.

    I notice in Loopy Pro it has a Port that can be set for OSC, but I do not see any IP address that I can be set to let Loopy Pro know where TouchOSC is located.

    I wonder if the OSC Client on Loopy Pro has been implemented yet?

  • espiegel123espiegel123

    @digitalferret : are you talking about TouchOSC running in the same device as Loopy or running on your PC?

    Michael can chime in as to whether feedback is implemented for OSC

  • digitalferretdigitalferret

    Touch OSC is on a separate device to Loopy Pro.

    • Loopy Pro on an iPad Pro
    • TouchOSC on a iPad Mini or a Windows PC.
  • wimwim

    I think I can help. It took a long time for me to figure this all out during the beta.

    The short answer: You only need the IP address of Loopy Pro and to enable feedback. The trick with TouchOSC is to set the connection protocol to TCP Client. The default is UDP, which will only work one-way.

    I tried so many different things until @Michael tipped me off to make that one little change. 😉

    If that fixes it for you then that's all you need. Otherwise, I can write up a more detailed process.

  • wimwim
    edited June 2023

    @espiegel123 said:
    Michael can chime in as to whether feedback is implemented for OSC

    It is.

  • digitalferretdigitalferret

    @wim said:
    I think I can help. It took a long time for me to figure this all out during the beta.

    The short answer: You only need the IP address of Loopy Pro and to enable feedback. The trick with TouchOSC is to set the connection protocol to TCP Client. The default is UDP, which will only work one-way.

    I tried so many different things until @Michael tipped me off to make that one little change. 😉

    If that fixes it for you then that's all you need. Otherwise, I can write up a more detailed process.

    Brilliant! That did the trick.

    You also need to set the OSC Framing version to v1.1 in TouchOSC on the TCP CLIENT option

    I had tried the TCP Client option yesterday but had left it at the default v1.0 and it didn't even work one way, so had ruled out that option.

    So great to have this working, it is a game changer, OSC is superior to MIDI for this sort of thing, especially with boolean UI elements like buttons that can easily get out of sync - will be even better if this feature request is implemented - https://roadmap.loopypro.com/feature-requests/p/action-and-follow-action-for-load-project-for-send-current-state-of-all-or-speci

  • ultracelloultracello

    Nice, that worked fine @digitalferret. Thanks!

Sign In or Register to comment.