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.

THU in Loopy Pro, control rig player and pedals

edited December 2023 in Loopy Pro

Hello forum,

I will edit my earlier post. I wrote about connecting the Korg Nanokey Studio to THU. The beauty of this contoller is it has 8 banks of 8 knobs, so a lot of connections can be made.

But I took it to the next level, I made a panel in Loopy Pro to control the rig player and pedals. Now I don’t need the controller anymore.

Only one small problem left, The global midi mapping are preserved when you change pedals or amps. But the preset midi mappings disappear when you change an element. And the global settings don’t cover all the settings of the pedals. So I added some extra knobs that are not connected yet. When I have a setup I really like, I can connect these knobs to the specific knobs.

And I made a button to pop up the THU interface.

What I like to add next is a button to switch all the pedals off. But this has to be a sequence of all pedals on and off again, because the midi command doesn’t known the on/off state off the pedal at the start. Maybe a widget can do this. Maybe @espiegel123 knows this…..



Comments

  • You have gone deep… I hope someone can help you with the last step.

  • @raabje : a few things, you can add as many actions as you want to a widget. So you can have a widget that turns all the effects on or off.

    Also THU does let you set up midi mapping that isn’t toggling so that sending a cc value of 0 turns off the effect and 127 turns it on.

    In Loopy midi bindings to on-screen controls should be on local profiles rather than global profiles as the mapping will break if the controls move or new ones are added. You can duplicate a local to global and vice versa.

  • @gusgranite said:
    You have gone deep… I hope someone can help you with the last step.

    Ha thanks Gus, I see you worked through 100 pages of the forum. I appreciate that.

    @espiegel123

    My experience with THU is, with global settings, I can swap and move pedals, and the midi binding stays there. But the list of knobs to control is not complete. So if I change a Blues driver pedal for a Taxi driver, the generic binding for OD Pedal is still there.

    In the local setting, there is more knobs to bind, but this dissapears when I swap a pedal. For example the Rig player functionality. If I swap a rig player for a normal amp, the bindings of the rig player get lost if I change it back later.

    So I have made a panel as a starter, and when I want to expand this, there is some space left.

    But that was my experience, I have to check again. Maybe my observation was wrong.

    For one button that sends a command to all the pedals --> on --> off, I have to experiment with the widgets. It was not clear to me yet how to do this.

  • @raabje : you won’t use one action to send off to all pedals, you will use me action per off command. You will be adding many actions to one widget.

  • edited December 2023

    @espiegel123 said:
    @raabje : you won’t use one action to send off to all pedals, you will use me action per off command. You will be adding many actions to one widget.

    Yes, got it finally. What does the trick is creating a new button, choose toggle, choose the distortion on/off button. And then go back to toggle, and press the + button. Then choose OD on/off button, press + button, etc. So this way I create a row of commands with one press of the new button.

    I had overlooked the + button to combine actions.

    Only things is it toggles all buttons to the next state this one central button itself is. That is no problem at all, when all buttons turn on, I toggle a second time. I want to turn all pedals off at the start of the session, because in THU when you use the native interface and turn on and off pedals, you cannot see the state without looking at the THU interface. It is just for convenience, turn all off before I begin, without hassle.

  • @raabje : for what it is worth, if i want to set things to a specific state, I don't use toggles. I will use radio buttons or stepped dials because you can trigger them to send/trigger their current state without toggling. I often set up a stepped dial with two steps: off and on and have a press action that nudges the dial (with wraparound turned on). I tap the dial to toggle and i can trigger the dial from other widgets to retrigger its current step (which is nudge with a step size of 0)

  • @espiegel123 said:
    @raabje : for what it is worth, if i want to set things to a specific state, I don't use toggles. I will use radio buttons or stepped dials because you can trigger them to send/trigger their current state without toggling. I often set up a stepped dial with two steps: off and on and have a press action that nudges the dial (with wraparound turned on). I tap the dial to toggle and i can trigger the dial from other widgets to retrigger its current step (which is nudge with a step size of 0)

    Okay, thanks, I am gonna check that too. I tried it a little bit but I have to get a deeper understanding first. Maybe with some backward engineering from the RC500 project I will get it to work in my own project.

  • Thank you for sharing all your work creating this set up. I happen to own all the apps (including the TH-U IAP’s) that you use so that’s a nice bonus. It loaded perfectly… my only surprise was when I saved it and re-started Loopy Pro and couldn’t find the saved Project… I re-loaded from your downloaded instance and tried again. It took a couple iterations to see the saved project.
    I have no idea what I was doing wrong… maybe I didn’t actually terminate Loopy Pro between attempts. No biggie.

    I really hope more people share their projects… I remember that I really learned AUM over several months uncovering a new feature with each project I created. Loopy Pro is deep and probably needs a similar approach… make something and keep adding complexity to your workflow.

  • edited December 2023

    @McD said:
    Thank you for sharing all your work creating this set up. I happen to own all the apps (including the TH-U IAP’s) that you use so that’s a nice bonus. It loaded perfectly….

    Thanks McD, setting it up in THU was the hard part. I attach the newest version in this post, I added a central on/off button. See below.

    And a lot of pedals have more buttons and switches, so the gray knobs can used for that, you need to assign in THU a local midi cc number to the knobs and switches that are not covered yet.. And then in Loopy Pro program the gray knobs the same way. But don’t switch a pedal with these connections, otherwise the assigned midi cc parameter disappears. It is an extra, you can go to the THU interface too to tweaks those knobs. There are some spare cc numbers available in THU.

    For example in this picture I assign cc89 to the bass knob of a pedal in the distortion group.


    It is too bad the THU interface works with those pull down list, when all the knobs could be used with the touch screen, this Loopy project is not needed.

    Next thing I want to add to this project is knobs to start a row with loops with the same color (group). So I can play and switch intro/part A/part B/part C/etc./outro for drum/bass/guitar

  • edited December 2023

    New version with 5 scenes. The button solo’s a selection of donuts. Copied from the factory project with the 8x8 donuts. I could add more channels later on.

Sign In or Register to comment.