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.

M2DX [TestFlight] — DX7-compatible FM synth with full MIDI 2.0 UMP support

hakaruhakaru
edited June 19 in General App Discussion

Hi all,

Just opened the public TestFlight beta of M2DX, a DX7-compatible FM synthesizer for iOS/iPadOS 18+. Built entirely in Swift6

TestFlight: https://testflight.apple.com/join/BAtGszPw
Support page (full feature list): https://hakaru.net/M2DX-support/
Source: https://github.com/hakaru/M2DX

## What it does

DX7 emulation
- 6 operators × 32 algorithms (full DX7 algorithm set)
- 32 factory presets bundled (BRASS1, E.PIANO1, WOOD BASS, FLUTE 1, etc.)
- 16-voice polyphony, sustain pedal (CC64), ±2 semitone pitch bend

MIDI 2.0
- Core UMP support: 16-bit velocity (65,536 levels), 32-bit CC, 32-bit pitch bend
- Automatic MIDI 1.0 fallback (works with any traditional gear)
- MIDI-CI Property Exchange: 155+ params auto-discoverable, JSON-based preset management (no SysEx required)

FX & Routing
- 6-stage FX chain: EQ → Drive → Chorus → Reverb → Stereo → Maximizer
- Every FX parameter MIDI Learn-mappable to any CC

Audio engine
- AVAudioSourceNode direct rendering inside CoreAudio render callback
- ~5ms IOBufferDuration is the effective latency floor

## Honest disclosure

Not yet at instrument-grade quality — releasing the beta specifically to gather feedback. Current rough edges:

  • MIDI 2.0 hardware coverage: I don't own enough MIDI 2.0-capable hardware
  • DX7 preset parity: 1:1 tonal match vs original DX7 / Dexed not fully verified across all 32 presets
  • SysEx patch import: bank loading compatibility will improve over upcoming builds

  • FX chain musical tuning: parameter ranges and CPU efficiency still need refinement

    What I'd love feedback on

  1. AUv3 priority — currently standalone only. How critical is AUv3 for your Loopy Pro / Cubasis / AUM workflow? (This is
    probably the #1 question for this community)
  2. DX7 preset accuracy comparisons (especially if you have Dexed or hardware DX7)
  3. UI/UX feedback — first impressions, friction points

  4. MIDI 2.0 testing if you have UMP-capable hardware

    Crashes auto-report via Firebase Crashlytics. macOS support planned.

    Thanks for trying it out — happy to answer any technical questions about the FM engine port or MIDI 2.0 plumbing.

Comments

  • audiblevideoaudiblevideo

    Off topic @hakaru your sonic collector creates IR or NAM profiles and your engine plays them?

  • wimwim

    I can answer #1 easily enough. Not of any interest at all if it's not AUv3. Not even if it's free.

    MIDI 2.0? I doubt many people care about it. MPE is far more important to most. I mean it's great, and forward looking, that you're implementing it, but I sure doubt you'll find many people with MIDI 2.0 hardware for quite some time yet.

  • GavinskiGavinski

    @wim said:
    I can answer #1 easily enough. Not of any interest at all if it's not AUv3. Not even if it's free.

    MIDI 2.0? I doubt many people care about it. MPE is far more important to most. I mean it's great, and forward looking, that you're implementing it, but I sure doubt you'll find many people with MIDI 2.0 hardware for quite some time yet.

    +1 to both of these. AUv3 is a must in 2026, there'll be almost zero interest without it. A good mpe implementation might help this stand out in a brutally overcrowded marketplace

  • wimwim

    humm ... it seems MIDI 2.0 UMP encapsulates all MIDI 1.0 protocol messages? So, maybe MPE is doable within that context?

    I exposing my ignorance here.

  • Rob_Jackson_MusicRob_Jackson_Music
    edited April 27

    @hakaru said: Crashes auto-report via Firebase Crashlytics.

    If all you're using Google Firebase for is crash reporting, I'd respectfully ask why?

    App Store Connect will give you perfectly acceptable crash reporting at the code level, fully integrated with Xcode if you upload your dSYM files with your build.

    If you're using Firebase for other "analytics" stuff... I think people tend to not be so keen on that, and you have to disclose what data you're collecting if you plan on distributing through the App Store. Just a heads-up, in case you weren't aware.

    On the topic of AUv3, I guess you're aware that "built entirely in Swift" probably ain't going to get you there? Last time I looked at the audio AVFoundation stuff, which admittedly, was a long time ago, there was no Interoperability between AVFoundation and AUv3, specifically, exposing your AudioUnit to the outside world as an AU App Extension. In fact, it's the main reason I ditched Swift for audio apps years ago, but I digress.

    Last time I looked (again, a while ago) if you build an AU extension from the Xcode template, it spits out Swift for the UI, C++ for the DSP, and Objective C to glue it together. I'm assuming that's still the case.

    Apologies if you're aware of all this as part of a risk assessment kinda thing.

    Cheers, -Rob

  • wagdogwagdog

    I’m a sucker for a DX7 and love dexed.

    Not having auv3 is a non-starter. Sorry, appreciate the effort but must be auv3.

  • x23x23

    If you switch from landscape mode to portrait mode on the iPhone, this sometimes happens. I recorded a video trying to reproduce the bug, I think it has to do with attempting to bring up the keyboard in the edit view.

  • dendydendy
    edited April 27

    good meant advice: i would suggest to add MUCH MUCH more effort into UI ... it maybe doesn't look that but nice appealing UI is thing of MAJOR importance for AU plugins .. ideally scalable so it looks nice at all kinds of various viewport sizes .. it doesn't matter how good is your engine if it is packed into not nice UI full of generic SwiftUI apple/glass components...it doesn't need to be skeumorphic complicated madness - you can make simple flat layot with minumum colors .. claude code wil for sure help you with that (you just need to push im to make reusable configurable compotnetns to avoid him doing all hard-coded shit so then 1 small change means editong 1000 places :))

  • JumpercollinsJumpercollins

    Be nice if it comes with a built in keyboard!

  • purpan2purpan2

    A quick check on my two favourite DX7 presets - EPiano 1 and Brass 3 - shows they sound very much like how my old DX7 used to sound. Very playable indeed. The mod wheel setting is a bit mysterious, though.

  • x23x23

    @Jumpercollins said:
    Be nice if it comes with a built in keyboard!

    It comes with keyboard.

  • AnalogMatthewAnalogMatthew
    edited April 28

    Congrats on getting your app to Testflight @hakaru.

    Just a couple quick heads-ups to keep in mind:

    1) You probably do not want to ship it to the App Store with the original DX7 ROM presets included. As far as I know, Arturia has the only legal rights to distribute those in an app. There are plenty of great DX7-style presets out there you can include instead.
    2) If you are porting Dexed, make sure you are not using the Mark I version. That can create GPL compliance issues and potentially get the app pulled from the App Store.

    Good luck with it!

  • PoppadocrockPoppadocrock

    Congrats @hakaru looks interesting, cheers.

  • PoppadocrockPoppadocrock
    edited April 30

    @AnalogMatthew said:
    Congrats on getting your app to Testflight @hakaru.

    Just a couple quick heads-ups to keep in mind:

    1) You probably do not want to ship it to the App Store with the original DX7 ROM presets included. As far as I know, Arturia has the only legal rights to distribute those in an app. There are plenty of great DX7-style presets out there you can include instead.
    2) If you are porting Dexed, make sure you are not using the Mark I version. That can create GPL compliance issues and potentially get the app pulled from the App Store.

    Good luck with it!

    That’s interesting.

    Users can download tons of free dx7 patches, there are thousands and thousands for free, even a free dx7 cart generator web app that randomly generates 32 or whatever presets in each generated cartridge. Maybe just point customers towards some big free banks “All the Web Zip” dx7 bank comes to mind, and/or generate a bunch of carts save the best and add those too.

  • PoppadocrockPoppadocrock

    For your #1 question, id say yes AUv3 is essential if you want to generate a decent amount of sales. Way more people will be interested, buy, and use the app if it has auv3.

  • hakaruhakaru

    @AnalogMatthew said:

    1) You probably do not want to ship it to the App Store with the original DX7 ROM presets included. As far as I know, Arturia has the only legal rights to distribute those in an app. There are plenty of great DX7-style presets out there you can include instead.
    2) If you are porting Dexed, make sure you are not using the Mark I version. That can create GPL compliance issues and potentially get the app pulled from the App Store.

    Really appreciate the heads-up on both points — these are exactly the kind of issues I need to sort out before App Store
    release.

    1) DX7 ROM presets: I wasn't aware Arturia holds distribution rights to the original patches. I'll remove the factory ROM
    presets from the shipping build and either generate original presets or curate from freely available community patches. Thanks
    to @Poppadocrock for the "All the Web" suggestion too.

    2) Dexed GPL: M2DX is based on the msfa engine (the original Google code, Apache 2.0 licensed), not the Dexed Mark I codebase.
    I've been careful about this, but I'll do another thorough audit of the source lineage before submission. The full source is on
    GitHub for anyone who wants to verify.

    This is exactly why I wanted to do a public beta first. Thank you.

Sign In or Register to comment.