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.

RTP-MIDI (Network MIDI) Utility by Ryouta Kira (Free)

wimwim
edited February 25 in General App Discussion

https://apps.apple.com/app/rtp-midi-network-midi/id6759605773

RTP-MIDI (Network MIDI)

Utilities

Simplify your Network MIDI workflow.
A practical RTP-MIDI management tool designed specifically for iOS / iPadOS.

RTP-MIDI is a dedicated utility that allows you to configure and manage RTP-MIDI (Network MIDI) connections entirely on iOS / iPadOS. No Mac or PC required — build and control your network MIDI environment using only your iPhone or iPad.

Key Features:

  • RTP-MIDI Session Management
    Create and manage RTP-MIDI sessions directly on your iOS / iPadOS device. Quickly establish Network MIDI connections without complex setup procedures.

  • System-Wide Availability
    Once configured in this app, the RTP-MIDI connection becomes available to other CoreMIDI-compatible apps on the same device. Use it seamlessly with synthesizers, DAWs, and other music production apps.

  • Manual Host Connection via Contacts
    Add host IP address and port information in Contacts to manually connect to specific RTP-MIDI peers.

Use Cases:

  • Use your iPad as a network-connected sound module
  • Control iOS / iPadOS synths from an external DAW over Wi-Fi
  • Build flexible wireless MIDI routing setups

Comments

  • Oh wow, I used rtp midi for years on the desktop, is this the same developer?

  • Ryouta Kira is the developer of KQ Dixie, Sampei, etc.. He's not the developer of RTP-MIDI, which is a standard protocol (RFC 6295) introduced in the early 2000's. I think you're thinking of Tobias Erickson, the developer of the rtpMIDI Windows driver.

    Apple "Network Session" is basically Apple's version RTP-MIDI.

  • wimwim
    edited February 25

    It's just a simple utility that makes connecting over Network Session a little easier. AUM, Loopy Pro, and probably other hosts already handle this fairly well, but it's nice as a quick tool that makes the Network Session available to any host that can use Network Session. Many apps can use Network Session, but don't have the facility to make the connections. This should help with those.

    MIDI over Network Session using WiFi isn't ideal, but it's OK for some things. With wired Ethernet it works great.

  • Be great to see a few videos user cases.

  • Ooh this is interesting, will try later, struggled a bit with the original windows one disconnecting in between uses etc.

  • @Bat71 said:
    Ooh this is interesting, will try later, struggled a bit with the original windows one disconnecting in between uses etc.

    Think it’s Mac iPad only ?

  • @Jumpercollins said:

    @Bat71 said:
    Ooh this is interesting, will try later, struggled a bit with the original windows one disconnecting in between uses etc.

    Think it’s Mac iPad only ?

    Ah booh.

    I thought though that this bit meant I might be able to trigger IoS synths from Ableton - Windows (which is what I was doing before with RTP-Midi from Tobias)

    "Control iOS / iPadOS synths from an external DAW over Wi-Fi"

  • wimwim
    edited February 25

    You should be able to connect to anything that supports the RTP Midi protocol. I set up sessions with my Mac, iPad, and iPhone. A windows PC should be no different if it has an RTP MIDI driver.

    Let me clarify: This isn't an RTP MIDI driver or implementation. It's just a connection manager, giving you a central place you can control what's connected. It does nothing other than that. It also does nothing that you couldn't already do from an iPad or iPhone. It just makes the process simpler and extends the ability to use Network Session to apps that didn't have a way of setting up the session in the first place.

    Remember how we had to resort to apps like midimittr to set up Bluetooth MIDI connections because not many hosts had the connection dialog built in? This is like midimittr in that way.

    Oh ... and just to be clear ... RTP Midi over WiFi generally sucks. Timing is terrible. Over wired networks it can be pretty good though.

    I probably shouldn't have posted this. I think I've created more confusion than anything else.

  • edited February 25

    At the mo 3 ipads all can recieve Din wired midi.

    But if they were usbc.

    Is this an app that can allow me to map a surface builder or loopy, to trigger a host record button but also send the command to both other ipads ( and map and trigger the hosts record buttons )

    Just a universal midi button for 3 ipads ( from 1 ipad )

    Im not sure if you can do this already with the midi apps because bluetooth controllers can only be for 1 ipad ?

    Is this app for midi ?

  • @sigma79 said:
    At the mo 3 ipads all can recieve Din wired midi.

    If so, then you really don't need network midi at all.

    But if they were usbc.

    Is this an app that can allow me to map a surface builder or loopy, to trigger a host record button but also send the command to both other ipads ( and map and trigger the hosts record buttons )

    I don't understand. There's nothing stopping you from sending to multiple destinations from something like Surface Builder or Loopy.

    As for mapping and triggering the hosts' record buttons, that depends on the hosts having that capability.

    Just a universal midi button for 3 ipads ( from 1 ipad )

    I don't understand the problem you're having with doing that already.

    Im not sure if you can do this already with the midi apps because bluetooth controllers can only be for 1 ipad ?

    One Peripheral connection per device, but a Central device can connect to as many peripheral devices as you like. If your "button" is on the central device, it can send to all connected peripheral devices. I'm not sure the problem you're seeing here.

    Is this app for midi ?

    Yes, it's for MIDI. I don't think it's anything you need though.

    It's a utility for connecting managing connections to something called RTP-MIDI. (Apple calls this "Network Session"). It's like a network you can send MIDI over, either using WiFi or a wired Ethernet network. The utility doesn't make the RTP-MIDI network, it only helps make connections.

    From what I can understand of your post, there's nothing it will do that you can't already do better over wired MIDI-DIN or over Bluetooth MIDI.

  • edited February 25

    @wim said:

    @sigma79 said:
    At the mo 3 ipads all can recieve Din wired midi.

    If so, then you really don't need network midi at all.

    But if they were usbc.

    Is this an app that can allow me to map a surface builder or loopy, to trigger a host record button but also send the command to both other ipads ( and map and trigger the hosts record buttons )

    I don't understand. There's nothing stopping you from sending to multiple destinations from something like Surface Builder or Loopy.

    As for mapping and triggering the hosts' record buttons, that depends on the hosts having that capability.

    Just a universal midi button for 3 ipads ( from 1 ipad )

    I don't understand the problem you're having with doing that already.

    Im not sure if you can do this already with the midi apps because bluetooth controllers can only be for 1 ipad ?

    One Peripheral connection per device, but a Central device can connect to as many peripheral devices as you like. If your "button" is on the central device, it can send to all connected peripheral devices. I'm not sure the problem you're seeing here.

    Is this app for midi ?

    Yes, it's for MIDI. I don't think it's anything you need though.

    It's a utility for connecting managing connections to something called RTP-MIDI. (Apple calls this "Network Session"). It's like a network you can send MIDI over, either using WiFi or a wired Ethernet network. The utility doesn't make the RTP-MIDI network, it only helps make connections.

    From what I can understand of your post, there's nothing it will do that you can't already do better over wired MIDI-DIN or over Bluetooth MIDI.

    Cool.

    So if I didnt have midi din.

    I can already send a surface builder ( thats in a host ) not standalone.

    And send midi to the other ipads.

    Whats a central device ?

    Is it just a case of advertising an ipad and recieving on the others ?

    Yah.

    I already sold a Faderfox Pc12 for the task and already bought some cheaper hardware as replacement. Although I should still need device. I should have asked lol.

    You are right wim.

    I dont need this app.

    I didnt need to also spend £120 from from the faderfox sale ( but the controller Il be purchasing to go with a powered din merger, would hopefully be good for a dj app anyway at some point )

    I can send and recieve midi from an ipad to multple ipads though.

  • wimwim
    edited February 25

    @sigma79 said:
    Whats central command ?

    Think of it like a USB hub. A hub has a host port that connects to something, and guest ports to plug things into. The peripherals can only talk to the host, not to each other.

    The central node in a Bluetooth connection is like the iPad the hub is connected to. The peripheral nodes are like devices plugged into the hub.

    Using AUM as an example, on the device that is going to be the central node, you go to Settings > Bluetooth Central to see the list of devices that it can connect to.

    The other iOS devices won't show in that list by default. They need to first "advertise" themselves. In AUM, you turn on this advertising by going to Settings > Bluetooth Peripheral. Once turned on then you can see the device on the central node and connect to it.

    So, now you have a bunch of devices connected to the central node. If your control surface is on the central node, you can communicate to any peripheral node easily.

    You can still use AUM's routing matrix to route between peripherals, but it's AUM doing the routing, the peripherals can't communicate with each other directly, just like with a USB hub.

  • edited February 25

    @wim said:

    @sigma79 said:
    Whats central command ?

    Think of it like a hub. A hub has a host port that connects to something, then guest ports to plug things into. The central node in a Bluetooth connection is like the iPad the hub is connected to. The peripheral nodes are like devices plugged into the hub.

    Using AUM as an example, on the device that is going to be the central node, you go to Settings > Bluetooth Central to see the list of devices that can connect.

    The other devices won't show in that list by default. They need to first "advertise" themselves. In AUM, you turn on this advertising by going to Settings > Bluetooth Peripheral. Once turned on then you can see the device on the central node and connect to it.

    So, now you have a bunch of devices connected to the central node. If your control surface is on the central node, you can communicate to any peripheral node easily.

    You can still use AUM's routing matrix to route between peripherals, but it's AUM doing the routing, the peripherals can't communicate with each other directly.

    Thanks.

    I still needed aum and then closed aum and could use this bluetooth across Drambos.

    I think you still need aum to start a signal to be seen ( until Drambo can advertise )

    I couldnt see both ipads in aum matrix ( perhaps I didnt advertise ) It would obviously work across AUMs.

    Working in Drambo.

    The main thing ( although I could have saved money also lol )

    I can still keep multi ipads in future ( if I still like working on multipads )

    I thought my current multi ipad build were on an extinction timer.

  • @sigma79 said:
    I still needed aum and then closed aum and could use this bluetooth across Drambos.

    That's right, as long as some other app is using the connections, you can close AUM. The connections are torn down once nothing is using them though.

    I think you still need aum to start a signal to be seen ( until Drambo can advertise )

    Yes, or another app such as midimittr.

    I couldnt see both ipads in aum matrix ( perhaps I didnt advertise ) It would obviously work across AUMs.

    Working in Drambo.

    That's right, you won't see the other iPads if they aren't advertising.

  • @sigma79 - BLE MIDI has to be set up from scratch every time when connecting multiple iPads. That's a pain. If you have them connected via MIDI DIN, it may be worth it for less setup hassle, lower latency, and better reliability.

  • @wim said:
    @sigma79 - BLE MIDI has to be set up from scratch every time when connecting multiple iPads. That's a pain. If you have them connected via MIDI DIN, it may be worth it for less setup hassle, lower latency, and better reliability.

    Thanks.

    I made comment for support ( In a Drambo thread ) for this now.

  • @sigma79 said:

    @wim said:
    @sigma79 - BLE MIDI has to be set up from scratch every time when connecting multiple iPads. That's a pain. If you have them connected via MIDI DIN, it may be worth it for less setup hassle, lower latency, and better reliability.

    Thanks.

    I made comment for support ( In a Drambo thread ) for this now.

    Tryin' to make sense of that comment now ... 🙃

Sign In or Register to comment.