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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Comments
That is both documented in the manual and in my tutorial video.
Thank you!
It exports multi-track MIDI files from the global menu, or single-track file from the track menu. These can be imported into any app that can import midi files.
I've looked, but wasn't able to find whether or not StaffPad can do anything with midi files containing MPE.
. nvm . misread the above post.
I haven’t tried it but I am curious if Atom plays back MTR created files. It is possible that the issues were on the recording side
Good question. I should have tested that before writing. Can't do it right now though.
This is great. Thanks for releasing it.
This is really great for jamming with
. I usually like to record audio of my performances as I do like to limit the amount of options I have, but the fact you can’t edit the notes is my preferred way of capturing this type of performance. Just do another take and use the bits you like.
This is what I liked about Photon AU as well, but here the gui is a much better experience. Like Photon, being able to slow down and speed up the performance could be nice (not essential but still stays with the tape recording concept) and could be fun to experiment with, although I expect this would be tricky with MPE.
This looks like a Loopy Pro issue, from your description and videos it's very likely it's stopping to call the MIDI Tape Recorder audio callback block.
MTR will follow the host tempo, even when you're not using the host transport, so you can use that to slow down or speed up 🙂
Oh great, yeah will use that method
In Loopy Pro, if one hasn’t recorded any loops, you need to manually set a tempo before using any plugins that need a tempo (this includes some synths with host tempo based arpeggiators and delays).
Sorry if this is a dumb question, what do you mean by "MPE" text on the tracks?
I think this is one for @GeertBevin
It's explained in the MPE support section in the manual and also in my tutorial video.
Thanks for that.
@tja: I've reported this to @Michael . According to the MTR manual that means that the messages identifying Animoog Z's output stream as MPE aren't reaching MTR -- if I read the manual correctly.
I haven't tried in detail with Loopy Pro, but apeMatrix has a problem here, consecutive RPN messages are not sent correctly between plug-ins, a lot of the messages are simply discarded.
It should be pretty easy to test. Just record playing two notes with different pitch bend or other modulation movement on each. Play it back and listen whether the polyphonic expression plays back properly.
The MPE indicator is turned on if a specific MPE configuration handshake is completed. It could be that a host or synthesizer works OK with MPE but doesn't react to or pass that configuration message properly.
MTR will record all the MIDI messages it receives, MPE or non MPE it doesn't really matter. The MPE indicator is when it captures and remembers the MPE Configuration Message, so that it can configure the synth the same way each time the recording is played. Without the MCM, you'll just have to make sure that the synth is set up the same way each time yourself.
Had to work out my Audiobus login just so I could come and say thanks for this. Really inspiring!
Have spent hours on it and not even using MPE
The moment when I realised the tempo could be changed
Thanks again!
After looking through the feature details, the unique use I understand this platform offers over other midi workstations is that you can perform MPE midi parts and change the patch/instrument after the fact without having to re-record the performance. Am I interpreting this correctly? The essential benefit of midi in a DAW environment is that it allows you to edit a performance for timing and to add expression elements. If there is no midi note editing, CCs etc, on this platform then aside from changing MPE patches/instruments after the fact why wouldn’t you just record the audio in the first place?
…just trying to understand.
I've tried to address that in the FAQ: http://uwyn.com/mtr/support/