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 StoreAudiobus is the app that makes the rest of your setup better.
Loopy Pro: MIDI Questions
Seems to me this category could use a dedicated thread just for midi questions. We’ll see if it sticks. Anyway, starting simple…
Is there a way to set the virtual in midi channel in Loopy Pro. I have it set up with Launchpad on channel one (note triggers recording), but when sending TC-DATA to another app (apematrix), it also triggers recording in LP. The ideal would be to just block note input going from TC to LP on channel 2, which is going to apematrix. Suppose I could edit the TC patches, but was hoping there’s a simpler solution from within LP.
Thanks.
Comments
Can you post a screenshot shot of your Loopy mixer setup and the midi bindings in Control Settings? If TC-DATA is triggering something in Loopy Pro, it means that a binding was setup for that event coming from TC-Data.
Midi triggers in loopy are always particular to a specific channel and device.
How did the binding get created? Did you midi learn it or enter it manually?
Thanks @espiegel123 . The loops are controlled by the standard Loopy Pro Launchpad default, as seen below. No midi learn to launch the loops. I tried disabling the input but still getting loops launching. I think I’m going to try using an IAA midi filter, like Midiflow, to block all midi input from TC to LP. Will update on that soon.
@zilld2017 : it is unusual that those are set to virtual midi in instead of to the Launchpad. Normally Launchpad bindings are directly to the Launchpad.
Please post a screenshot of the top level of Control Settings and your mixer and also do Add Midi on the mixer page and take a screenshot of the popup so that we can see what your iPad sees as available midi devices.
Describe how your hardware is connected. It may help understand why your Launchpad is being mapped to virtual in rather than the Launchpad.
@espiegel123
Off to work, but will try to post later tonight.
@zilld2017 . Just guessing, but is the Launchpad connected (plugged in) before loading Loopy Pro?
Good question. The answer is no, not for this configuration. I’m using korg nanostudio on the go and the launchpad at home.
Those Launchpad bindings do not look like what I would expect if you did not create those by hand. Here is what Control Settings Looks like for me when set up with Automated Launchpad bindings.
With automated binding, one won't see individual bindings in a profile.
So, it would be helpful to understand exactly how this was created. Please post screenshots at each level of Control Settings to have a better picture.
This helps. I turned off all the bindings. Works pretty much as expected—recording not triggered in LP.
However, one confounding issue remains—the mixer disappears. Is there a Hide Mixer action that I’m missing and may have midi-learned?
Thanks again for taking the time to help with this @espiegal123 and @uncledave.
In what circumstance is the mixer disappearing? There is a new action to hide/shoe the mixer. All bindings are visible in Control Settings by looking at the contents of the profiles.
>
That’s interesting…and potentially helpful. To troubleshoot, I’ve turned off all the settings/bindings. Still seeing the mixer disappear when getting data from TC…Note on/off and cc1, 7.
You could try putting a MIDI monitor on the input stream from TC. It could be sending something you don't realize, like maybe a PC.
If there isn't a binding visible in any profile, the MIDI shouldn't have any impact. There was a bug that could result in a binding being stored internally and invisibly, but if you are using the latest version of Loopy Pro that shouldn't happen.
Are you using the latest version?
Are you absolutely sure that none of your profiles have a binding to the Show/Hide Mixer action?
Can you create a new project with Loopy Pro's default project and turn off your global profiles in Control Settings and see if it happens?
If it still happens after that, please do the following:
If it doesn't show a MIDI mapping, use the popup at the upper left of the screen and choose each profile in turn and see if anything shows up.
I’ll do that. Thank you.
V
Yes. 1.1.18
Zero bindings in either “global profile: default”, or “current project: default”.
I did (created a default project, turned off global profile default and current project default—ie, no bindings at all appear to be on).
And it does (mixer hides)
Did this….
No mapping shows up. Mixer still toggles. Plus, three of the loops toggle on record. This is with the following settings:
Anyway, thanks for the effort. That’s it for me today, and hopefully you two. Going to troubleshoot TC this weekend to narrow down the offending message.
@zilld2017 : let us know if you can identify the offending message,
@michael is it possible that there is a ghost binding at work here?
Hi,
I'm having any issue with inputs to my midi-pedal turning off my guitar effects.
For example: I have a loop running that I want to toggle/mute, I set up a mute-color button for it in LP and I also can activate same from a midi-pedal button. (I also set up a mute-clip option, that had the same issue) The mute functions as desired (either through touching the button on the iPad or the button on my pedal) however when I use the pedal, it cancels any guitar effect.
Brand new iPad, Softstep2, latest versions of iOS, and multiple resets, rebuilt project one step at a time, looked through the documents.
I even built a simple 1-clip, 1 effect, 1 mute (color) project to confirm my issue. Same problem, clip plays and mutes correctly w/o canceling guitar-effect when touching the button on the iPad. But tapping the pedal cancels the effect.
I'm new to LoopyPro so I know that the issue likely lies w/ me and how I'm setting up the project. Can someone suggest where I can begin researching how to resolve it?
Thanks in advance,
Best,
JD
Please post a screenshot or screenshots that show your bindings and also the setup for the binding that isn’t working.
Also, check with a midi monitor to see what your pedal is sending. Instructions for that and other midi troubleshooting tips at: https://wiki.audiob.us/doku.php?id=loopy_pro:midi_troubleshooting
Hi, thanks for the reply.
I'm still digging in here and I just noticed something... What appears to be happening is that when I tap buttons 1 through 4 on my pedal to mute clips, it is also changing the presets w/I ToneStack PRO (A, B, C & D)
I'm getting somewhere... At least I see what the problem is now !
I have to figure out how to disable the change w/i TSpro so that the it doesn't cancel out what I want to do w/I LoopyPro. Not sure why it's doing that but I'll figure it out.
I'll take a good look at the link you posted and report back.
Best,
JD
Resolved !
Thanks for the reply/suggestion - that and writing out my issue helped me see and isolate it clearly.
(I disabled midi-pedal inputs w/in ToneStack since all my changes are coming from w/in LoopyPro itself)
Best,
JD
@espiegel123 , @Michael
I think there’s a ghost binding, that’s the issue. Here’s a short screen capture of my setting up a fresh default LP session and using. TC-DATA patch that only sends cc1. Mixer still hides (doesn’t toggle).
[im about ready to throw in the towel on this one, which is disappointing. There’s nothing like TC for generating managed midi chaos in the AUV3 realm that I can find (maaaaybe Surface Builder, but I don’t want to purchase it just for the one use-case).
[in fact, if only I could find a way to just block any virtual midi data from reaching LP I’d be happy. Midiflow would seem to serve that purpose, but to no avail—everything reaches LP via that port, even an Audiobus patch sending TC midi straight to Apematrix (my intended target). Anyway, the “ghost binding demo]
Thanks as always.
@zilld2017 : a few things. It looks like TC-DATA sends MIDI to all virtual midi ports it sees. So there is no way to put something like MIDI Flow between it and other apps. It is very unfortunate that it doesn't let you choose the destination.
It isn't having an impact on the mixer state when I try it. A few things to look at while waiting for Michael to look into it.
Have you rebooted your device since this started happening? If not, try that.
As a test, if you turn of virtual midi output in TC-DATA does it stop happening?
If you change your TC-Data patch to not send CC1 on channel 1 does it stop happening?
Yes, rebooted, but still hiding the mixer.
No. Tried testing with virtual midi out off and on, still hiding mixer.
Tried sending cc1 on channel 2: it stops hiding! Also notable: cc2-7 (only one’s I’ve isolated and tested so far) on channel 1 works—mixer stays visible. Well, well…. So this seems to indicate cc1 on channel 1 has been causing the mixer to hide, even without bindings. On my device. At least that’s my conclusion.
I still have one more issue (mentioned earlier) but let’s leave that for another time and enjoy our troubleshooting success. Thanks @espiegel123 !
@zilld2017 : the ghost binding seems to be something specific to your install as if doesn’t happen for me. We probably need Michael to investigate.
What’s the other issue?
A strange anomaly that I shall have to accept. Glad to have narrowed down the source though.
Probably not a LP issue, but:
when TC-Data passes note data through Virtual MIDI, it goes to ApeMatrix (functioning as my instrument source) as desired, but also goes to LP, triggering the clips, which is **not**** desired.
Again, a simple IAA app that will filter out all Virtual MIDI output from reaching LP would be solve all my problems. Any suggestions?
I tried to explain this earlier.
TC-DATA sends directly to all virtual midi ports [which means any app that has a midi in port visible to the OS]. So there is no way to filter it. TC-DATA sends the data directly to each app that can receive midi.
All you can do is not use the data. If for some reason you need to use the Loopy's virtual in, you will have to not create bindings to messages TC-DATA sends.
Imo, TC-DATA should offer the user a choice of where it sends its data or publish its own midi out port so that every app doesn't receive everything it sends.
Got that.
Putting the onus on TC, agreed.
100%
I imagine that when TC-Data was programmed it probably wasn't likely for someone to be running multiple receivers on the same device at once.
Can you use the MIDI channel as a basic way of handling this? Set the TC-Data output channel to 2. Configure the ApeMatrix app to receive notes on channel 2. Configure LP to respond to notes only on channel 1. If LP needs some messages from TC-Data, a little StreamByter script inside LP could listen to the stream on channel 2, and convert only desired messages to channel 1. This would be the traditional MIDI way of solving this, before we could route individual virtual ports.
I believe I tried changing the midi out channel in TC earlier in this soujurn—it has to be done in the patches, there is no global midi out channel option. No matter the setting, any note data goes into LP. I don’t want any data at all going from TC to LP. Thanks, @uncledave