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.

Tessitura Pro doesn't seem to send MIDI out ?

gkillmastergkillmaster
in General App Discussion

Either on my OSX version (in Catalina) or from my iPad Pro 2018.

Has anyone tried this and have it working?

Comments

  • aplourdeaplourde

    @gkillmaster said:
    Either on my OSX version (in Catalina) or from my iPad Pro 2018.

    Has anyone tried this and have it working?

    Yes.

    The “settings” for this are pretty crap. Basically the way it works is to connect to the first MIDI port it finds. This will be the first Core MIDI port that's created.

    So if you load App A then App B, Tessitura will connect to App A.
    If you load App B then App A, Tessitura will connect to App B.

    If you have a bunch of apps loaded and want to connect to a specific one you'll have to quit everything and then load that specific app first. Or, load a MIDI router app (MidiFire, MidiFlow, etc.) or host (AUM, Audiobus, etc.) first and then use that to point to any specific app.

    A few things to note:
    -it only sends on MIDI Channel 1, so your app needs to be on Ch1 or set to OMNI (or use a MIDI router to switch the channel)
    -the connection to to first app won't update. So, if you quit the first app, Tessitura will still be trying to send to that app and nothing will work. Even if you turn MIDI off and on in the settings, it won't update, you have to quit and restart Tessitura.
    -sometimes the reference to an app's Core MIDI port will hang around even after you quit the app. If this happened to be the first app you loaded, Tessitura will keep trying to connect to that. Resetting RAM or restarting you device is the only remedy.

    All of this is tested on iOS 12 devices (iPhone and iPad), so if it's not working at all for you, that could be an iOS 13 bug.

  • gkillmastergkillmaster

    @aplourde said:

    @gkillmaster said:
    Either on my OSX version (in Catalina) or from my iPad Pro 2018.

    Has anyone tried this and have it working?

    Yes.

    The “settings” for this are pretty crap. Basically the way it works is to connect to the first MIDI port it finds. This will be the first Core MIDI port that's created.

    So if you load App A then App B, Tessitura will connect to App A.
    If you load App B then App A, Tessitura will connect to App B.

    If you have a bunch of apps loaded and want to connect to a specific one you'll have to quit everything and then load that specific app first. Or, load a MIDI router app (MidiFire, MidiFlow, etc.) or host (AUM, Audiobus, etc.) first and then use that to point to any specific app.

    A few things to note:
    -it only sends on MIDI Channel 1, so your app needs to be on Ch1 or set to OMNI (or use a MIDI router to switch the channel)
    -the connection to to first app won't update. So, if you quit the first app, Tessitura will still be trying to send to that app and nothing will work. Even if you turn MIDI off and on in the settings, it won't update, you have to quit and restart Tessitura.
    -sometimes the reference to an app's Core MIDI port will hang around even after you quit the app. If this happened to be the first app you loaded, Tessitura will keep trying to connect to that. Resetting RAM or restarting you device is the only remedy.

    All of this is tested on iOS 12 devices (iPhone and iPad), so if it's not working at all for you, that could be an iOS 13 bug.

    Thanks so much! I'll try this stuff out asap. Why does it have to be so obtuse?

  • CracklePotCracklePot

    Why do you need to use the Midi Out for this app?
    I only ever use it to work out ideas, but never as a sequencer or Midi source.

    Just curious, is all.

  • CracklePotCracklePot

    @aplourde
    Great troubleshooting, and clear explanation.
    Well done!
    🤙🏻

  • gkillmastergkillmaster

    @CracklePot said:
    Why do you need to use the Midi Out for this app?
    I only ever use it to work out ideas, but never as a sequencer or Midi source.

    Just curious, is all.

    I have some ideas I want to work through which requires quickly changing modes and playing super fast scales.

Sign In or Register to comment.