Loopy Pro: Create music, your way.

What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.

Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.

Download on the App Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Puzzling behaviour sending midi out and back in to host apps.

evenStevenevenSteven
in Knowledge Base

Hi all,

Can anyone more knowledgeable than I explain just what-in-the-knotted-virtual-midi-shoelaces is happening here?

(For anybody short on time: this is low-priority. I have sort-of got what I’m aiming for elsewhere (Drambo, AUM session, Ableton), so please feel free to be about your business! 😁 I just want to better understand WTF is happening in this case)

I was trying to cook up a way to chromatically access Battalion’s drums via their individual midi channels, while it’s hosted in SAND or BAM, with empty tracks sending a channel each to the main Battalion track. It seems that, internally, neither host can direct multiple channels to one track, which is fair enough (please do correct me if I’m wrong there).

I routed the midi out of, and back to, the standalone host via AUM. Tried both:
Track midi —> host output port, AUM source into the target track (host output to AUM source in AUM routing matrix)
Track midi —> AUM, host input port into target track (AUM dest —> host input in the routing matrix)

In both host apps, while these configurations triggered the AUv3, it only did so when its track was selected! Selecting another track, eg. one sending the midi out, completely silenced the plugin. This is what is puzzling me!

Clearly, with this happening in two different apps, there’s something screwy about the routing, or a technical reason in AUv3 itself.

It’s no big deal. As I say, I have other set-ups to use, but this has really puzzled me. Why would the audio drop out, or the MIDI stop, when the track sending it is selected?

Cheers.

Comments

  • evenStevenevenSteven

    I should have timed my question better, I most likely won't see any responses till tomorrow as I'm on the way to the rugby final at Twickenham!
    I'll just be drinking, not playing though. 😂
    Have a grand weekend, everybody.

  • evenStevenevenSteven

  • evenStevenevenSteven
    edited June 20

    Just a shot of the AUM matrix, also used AUM dest to SAND/BAM inputs. Both configs trigger the track.

  • uncledaveuncledave

    @evenSteven said:
    Just a shot of the AUM matrix, also used AUM dest to SAND/BAM inputs. Both configs trigger the track.

    And you could also have used SAND OUTPUT to SAND INPUT, or AUM Destination to AUM Source. Each app has two virtual MIDI ports, one for input and one for output. Connecting them does not create a short circuit, it just depends how they are routed in the other app.

    You need to show us the MIDI settings in the SAND app, both input and output.

  • evenStevenevenSteven

    @uncledave said:

    @evenSteven said:
    Just a shot of the AUM matrix, also used AUM dest to SAND/BAM inputs. Both configs trigger the track.

    And you could also have used SAND OUTPUT to SAND INPUT, or AUM Destination to AUM Source. Each app has two virtual MIDI ports, one for input and one for output. Connecting them does not create a short circuit, it just depends how they are routed in the other app.

    You need to show us the MIDI settings in the SAND app, both input and output.

    Thanks @uncledave. Yeah, it’s the same effect with both ways of routing it. Here’s a photo montage of the ins and outs, trying both routes.

  • evenStevenevenSteven
    edited June 21

    Top row is ‘aum in’ feeding track 1, ‘sand out’ on track 2, the routing in AUM.
    Second row: ‘sand input’ on track 1, ‘aum’ as midi destination on track 2, with the routing for that in AUM.
    You can see in the left-most images (showing track 1 selected) that the audio meters show the sound triggering. The middle shots (track 2 selected) have no audio coming through track 1, even though the transport is still running.
    The same occurs in BAM, with equivalent routing on the tracks. Strange!

    Edit: just to clarify, routing ‘sand input’ to ‘sand output’ in AUM, or ‘aum destination’ to ‘aum source’, with the requisite settings in SAND have the same effect.

  • uncledaveuncledave

    Right. Maybe these hosts (SAND and BAM) only play audio on the selected track, when a track is selected. A Background Audio setting might help (just guessing).

  • evenStevenevenSteven

    @uncledave said:
    Right. Maybe these hosts (SAND and BAM) only play audio on the selected track, when a track is selected. A Background Audio setting might help (just guessing).

    Ah, good suggestion, I’ll take a look. Thanks for that.

Sign In or Register to comment.