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.

Is there a free midi monitor AUv3 app?

One that can tell me what CCs / notes are being sent? Ta

Comments

  • wimwim
    edited June 2021

    For iPad only, midiSpy. Midi Tools Suite also has a monitor if you already own that one.

    For both iPad and iPhone, StreamByter (click on the magnifying glass to bring up the monitor.)

  • MidiSpy looks super - ta

  • Not sure if there's free AUv3 midi monitor app. But if you've got Mozaic it's pretty trivial to write a script that prints midi messages to the log window. Essentially, making Mozaic into a midi monitor. Not sure if there might actually be a project on Patchstorage that does this. But if not, here's a start:

    // Mozaic Midi Monitor, just save it and load it in 
    // whenever you want to monitor what's happening in your project
    
    @OnMIDINoteOn
    
      log {NoteOn:  }, MIDIByte1, { }, (NoteName MIDIByte2, 1), { }, MIDIByte3
    
    @END
    
    @OnMIDINoteOff
    
      log {NoteOff: }, MIDIByte1, { }, (NoteName MIDIByte2, 1), { }, MIDIByte3
    
    @END
    
    @OnMIDICC:
    
        log {CC: }, MIDIByte1, { }, MIDIByte2, { }, MIDIByte3
    
    @END
    
    @OnSYSEX:
    ReceiveSysex data
     length = SysexSize
     Log {SYSEX:  The received Sysex data is }, length, { bytes long.}
    // if you want, uncomment next line
    //  log {The Sysex data is }, data
     @END
    
    // WHERE DO MIDI CLOCK COMMANDS GET HANDLED?
    
    // SOME HELPFUL EVENTS YOU COULD LOG:
    
    //@OnHostStart
    //@OnHostStop
    //@OnNewBar
    //@OnNewBeat
    //@OnMetroPulse
    //@OnTimer
    
  • MIDI Wrench and MIDISpy are the ones I know. I’ve never used MIDISpy, but definitely MIDI Wrench shows the notes and CC.

  • @DMan said:
    MIDI Wrench and MIDISpy are the ones I know. I’ve never used MIDISpy, but definitely MIDI Wrench shows the notes and CC.

    Yup. These 2 plus others mentioned above and below.

    MfxMonitor
    https://apps.apple.com/us/app/mfxmonitor/id1451193551

    Midi tools isn’t free but has a bunch of AU’s inside one of which is a midi monitor.

    https://apps.apple.com/us/app/midi-tools/id1446209019

  • Thanks all, love this community

  • MIDI Monitor in the MIDI Tools suite is the only one that I know of that logs the frame-offset of events (as the time column) which is quite useful for diagnosing subtle timing issues. It, unfortunately does not log a timetamp so you can’t see the timing of events.

    The UI of mfxTools is horrible. A little tiny unsizable window inside an AU frame. It’d be ok on an iPhone 4 but not on a 12.9 iPad Pro. Maybe I just missed a setting. It does log time stamps though.

    MIDI Spy allows you to filter by event type and logs time stamps (in milliseconds). But the filtering only works before you start capturing but not when analyzing a full capture. The scrolling seems busted right now.

    I’ve also written Mozaic loggers but there’s no way to get real event timing out of it but it’s generally usable.

    None log bars/beats other than the ones in Mozaic.

  • edited June 2021

    MidiSpy is the best one, use it all the time. Midi Tools is useful for its other tools, but the midi monitor is inaccurate for midi CCs with the devices I've used like Midi Twistor and 16n Faderbank.

  • @auxmux said:
    MidiSpy is the best one, use it all the time. Midi Tools is useful for its other tools, but the midi monitor is inaccurate for midi CCs with the devices I've used like Midi Twistor and 16n Faderbank.

    Inaccurate in what way? I haven’t noticed. I wish it timestamped entries and sometimes I wish it wouldn’t decode cc#s to friendly names but the ordering and values have seemed correct. I’ve probably missed something though. It’s probably the one I use most.

    I couldn’t get midi spy to scroll through a (not really so) long log this morning. And I’m always disappointed that you can’t choose between message types after you’ve captured input.

  • @xor said:

    I’ve also written Mozaic loggers but there’s no way to get real event timing out of it but it’s generally usable.

    True. But with each line also logging Mozaic's SystemTime function value would cover some use cases. It's not a midi timestamp, but can be useful to know what time each midi message is being processed within Mozaic.

  • @hes said:

    @xor said:

    I’ve also written Mozaic loggers but there’s no way to get real event timing out of it but it’s generally usable.

    True. But with each line also logging Mozaic's SystemTime function value would cover some use cases. It's not a midi timestamp, but can be useful to know what time each midi message is being processed within Mozaic.

    Yep, that’s what I do. For the most part it’s ok. I generally log the bar:beat:ms-since-beat. It’s painful to do to get it all to align with Mozaic’s lack of string functions.

  • Not free, but also not expensive is Nurack's chord/note recognition module. It works very accurate and also includes a midi monitor module. I'm very impressed with the possibilities using Nurack.

  • MidiSpy, MidiSniffer.
    But beware that to me MidiSpy seems be blocking the MIDI messages, in order to read them. Doesn't simply log them; it seems to be filtering them away in the following nodes of the chain.
    But mind I might be doing something wrong.

Sign In or Register to comment.