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.

MidiFire (and MTS)

LittlewoodgLittlewoodg
edited September 2017 in General App Discussion

This turns out to be a very handy router (like their MidiBridge) for those synth apps I own that MTS IAA doesn't connect with directly...

It's also a very very deep modular/patchable midi processor (see the "Synth Byter" module that expands on that tool in MidiBridge, and the "Robotic Knob" module) for those midi scientists among us.

Has save-able/shareable scenes

Is on sale for much less than Midubridge but does so much more

MidiFire by Audeonic Apps
https://itunes.apple.com/us/app/midifire/id906600872?mt=8

Comments

  • CarnbotCarnbot

    Yes I like this. The advantage over midiflow and AB3 is you can quickly reroute destinations and sources and can do a lot without having to buy any extras. Wish the Stream byter was a bit easier to use. I wonder if you can use it to make probability stuff and randomisers? Think it will be beyond me.
    I've been triggering CCs with the Robotic knob but haven't grasped all the controls yet.

  • LittlewoodgLittlewoodg
    edited September 2017

    @Carnbot said:
    Yes I like this. The advantage over midiflow and AB3 is you can quickly reroute destinations and sources and can do a lot without having to buy any extras. Wish the Stream byter was a bit easier to use. I wonder if you can use it to make probability stuff and randomisers? Think it will be beyond me.
    I've been triggering CCs with the Robotic knob but haven't grasped all the controls yet.

    The Help documentation on Stream Byter blew my mind. Definitely far beyond me. Hopefully the midi adepts will avail themselves of app and its sharing features...and help me out with some of their amazing scenes :)

  • chris_fosterchris_foster

    Wondering why they went with CoreMidi instead of IAA-Midi

    IAA-MIDI
    An Inter-App Audio node app can receive direct MIDI from the host, without going through CoreMIDI. The host can then schedule MIDI events to the node with sample-accurate precision, using MusicDeviceMIDIEvent(). Also routing becomes easier, there’s no need to find the correct virtual endpoints to connect - especially if the host is the producer of the events (a sequencer).

  • LittlewoodgLittlewoodg
    edited September 2017

    @chris_foster said:
    Wondering why they went with CoreMidi instead of IAA-Midi

    IAA-MIDI
    An Inter-App Audio node app can receive direct MIDI from the host, without going through CoreMIDI. The host can then schedule MIDI events to the node with sample-accurate precision, using MusicDeviceMIDIEvent(). Also routing becomes easier, there’s no need to find the correct virtual endpoints to connect - especially if the host is the producer of the events (a sequencer).

    Maybe it's an attempt to steer around the ongoing inconsistency of IAA implementation across instrument apps. I know in the case of (name an iOS DAW) hosting (name an iOS synth) that IAA instrument audio will reach the host, but the instrument doesn't respond to host midi, while (name many other iOS synths) do recieve host midi. IAA midi fails and inconsistency across the platform are still cliche.

    my experience with core midi (using Genome, and a few other midi sequencing apps) has been stable and consistent.

  • AlexBAlexB
    edited September 2017

    MidiBridge before and midifire now has been my essential midi center where to control my needs of routing. It's such a superb app! Great great fan of Nic and his work!

  • HandOfEmptyHandOfEmpty

    Long time user of MidiBridge, happy to have picked up MidiFire now - great work. :)

  • ALBALB

    One question - anyone use it with BeatMaker 3? I tried it last night but even though BM3 sees MidiFire, I can't get it to record the midi. Any advice would be helpful.

  • RichtownsRichtowns

    @ALB BM3 has this annoying habit of greying out midi sources in the Midi settings page. That would be my first guess.

  • ALBALB

    @Richtowns said:
    @ALB BM3 has this annoying habit of greying out midi sources in the Midi settings page. That would be my first guess.

    Hmmm - I don't recall that MidiFire was greyed out, but I'll check again. Maybe I should go to the BM3 forum to try to hash this out. I often have problems with non-AU midi (of various kinds) on BM3. Could be user error, or just non-standard implementation of core midi in BM3. Sorry to highjack the thread. Otherwise, I'm liking MidiFire. It seems deep, but simple enough for me - really good so far in linking up apps.

  • NoonienSNoonienS

    Any native support for AB3 MIDI source/target, or would you need to use the Adaptor (not very useful from a workflow perspective)?

  • CarnbotCarnbot

    @NoonienS said:
    Any native support for AB3 MIDI source/target, or would you need to use the Adaptor (not very useful from a workflow perspective)?

    Not yet, but worth asking them, I sent them a request also, so the more requests the better.

  • CalverhallCalverhall

    It looks awesome, I'm considering it for the MIDI CC remapping alone, but if it had AB3 intergration with state saving then oh boy!

    Those kind of capabilities would essentially compltete the puzzle of designing a straight forward and cohesive mapping template for iOS live set ups on a song by song basis, switching between songs and sets through AB3 presets.

  • HandOfEmptyHandOfEmpty

    Is it possible to rename the midi ports in MidiFire? This was a great feature in MidiBridge because the iConnectivity default names were too long. MidiFire cuts the names off too short to see the full device name. Not sure how much I can really use this app if I can’t see what’s what.

  • AlexBAlexB

    Doesnt seem possible to rename. Let the dev know because it would be actually a nice to have.

Sign In or Register to comment.

© Vanilla Keystone Theme 2025