Audiobus: Use your music apps together.
What is Audiobus? — Audiobus is an award-winning music app for iPhone and iPad which lets you use your other music apps together. Chain effects on your favourite synth, run the output of apps or Audio Units into an app like GarageBand or Loopy, or select a different audio interface output for each app. Route MIDI between apps — drive a synth from a MIDI sequencer, or add an arpeggiator to your MIDI keyboard — or sync with your external MIDI gear. And control your entire setup from a MIDI controller.
Download on the App StoreAudiobus is the app that makes the rest of your setup better.
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.
OK, I need the AUM beta or the next stable version for this ;-)
. 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.
I used this fantastic App with out any problems in AUM.
But somehow, I sometimes cannot get it to play or record in Loopy Pro.
I can only assume that this has something to do with any Donuts currently being active or not, but am often confused.
In AUM, the transport does not need to run.
In Loopy Pro sometimes I seem to need a Donut running, sometimes not.
Also, the MPE text near the MTR track does not show up, which it does in AUM.
This may be because of the configuration with two Animoog Z instances?
And yes, I have both MIDI input and output set to MPE in both instances.
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.
Here a video:
https://www.dropbox.com/s/df2l786ztkza7tp/RPReplay_Final1640782588.MP4?dl=0
or
https://www.dropbox.com/s/df2l786ztkza7tp/RPReplay_Final1640782588.MP4?dl=1
It shows that I cannot record and also the missing MPE text... 😳
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).
Yes, that fixed it!
Still don't see the "MPE" text on the tracks.
Sorry if this is a dumb question, what do you mean by "MPE" text on the tracks?
The text "MPE" at track 1, that is visible when running MTR in AUM:
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.
Does that hint to similar problems within Loopy Pro?
Sadly, I do not understand the MPE part of the manual...
I just wanted to be sure, that MPE is used - and right now, that may not be the case, if I understood correctly.
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!
Many thanks!
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/