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.
Loopy Pro Questions
This discussion has been closed.
Comments
Do we know if drag and drop on to the timeline or sequence view is on the road map??
Thanks!!
At least not here:
https://loopypro.com/manual/#roadmap
The known near-term roadmap is in the manual.
I'm having problems with the sequencer. I wanted to record my loops directly to the timeline so I laid out the structure of the song using empty loops before recording, but when I play back my performance, the loops play randomly and don't follow my sequence. Any ideas on what I'm doing wrong?
Please post a video demonstration and maybe a copy of your project. There isn’t enough detail in your message to know what might be going on.
In this clip the loops don’t follow the sequence and everything gets out of sync.
Can you zip up the project band put it somewhere where @michael can download it from?
Does the problem only happen if the timeline is set to loop? Do any of the loops have follow action or midi triggers that might be firing?
Could it be something to do with the orange loops ? Looks like they’re only 2.75 bars...
It is a pretty simple project, no follow actions, no widgets or midi triggers. With the loop switch set to off I get similar results.
At the moment the squares “scene” on the right got to trigger the group raw.
Is the follow action not available for those squares?
Could figure out yet how to do but I’ll try more.
Follow actions apply to clips. Those things that say scene are button widgets. Take a look at them in the layout editor to see the actions they trigger. They are just buttons that tell a number of clips to play.
If I understand what you want correctly then the attached template should serve as an example.
Check the actions on the buttons, and also the play groups to see how they're specifically set up
Humm ... that Stop All button is acting a little weird. You might want to remove that one if it gives you trouble.
Is it possible to see this project in action.. seems it can do snapshots (screen buttons)… This may help make iOS the ultimate Music/Song Creation ‘tool..
Will love to see Sample Key detection and Transpose key (and scale) of the entire project (Blocs/Launchpad app, etc)
Nice..
I thought you were supposed to hit the rec button to record directly to the timeline. It turns out you just have to arm the tracks and press play. The sequencer was recording overlapped loops and that was causing the problem. I'm not sure if it's a bug or not.
Hmmmmm. Maybe I have been doing this wrong as well? Where do you ARM the tracks at? Are you saying just arm them and hit play in sequence view?
The arm button appears when you create empty events in the timeline. If you tap the arm button you can set the duration, count-in, loop detection, etc
Well crap….. I just found out if I double tap the timeline my recorded loops are already there. Hmmmm. Find out more and more every day!!! Thanks.
Repost from other Loopy Pro thread: Hey guys, I wasn’t able to find anything through forums search, but is there any talk of QWERTY keyboard shortcuts?
Also, I’m currently testing the beta sidecar. Wonder if anyones paired it with Loopy Pro yet.
If you have loops on your donuts you can sequence them in the timeline by tapping. You can also create empty events, record directly to the timeline and that way you can forget about punching in and out
This would be awesome as I use my magic keyboard in Cubasis and AUM all the time!!!!!
I noticed two Loopy Pro MIDI targets in AUM:
One is a MIDI processor, the other a MIDI instrument.
The processor may be for controlling Loopy with an external controller?
But for what can the MIDI instruments be used?
Normally, a MIDI instrument is something like an Synth and a MID generator something like Suggester, Xequences Pads, or a onscreen keyboard.
Or?
You can send and receive midi in loopy. You can even create layouts that just have buttons and sliders that send and receive midi .. which is handy for creating control surfaces.
For example, this layout:
Oh, many thanks, @espiegel123
I did not yet explore that... the manual is not finished 😅😅😅
So LP can act as MIDI controller and be controlled by an external controller.
I re-read the AUM manual:
https://kymatica.com/aum/help#toc72
So the processor can both receive and send MIDI within a MIDI strip.
And the instrument can receive MIDI from the host.
Need to wait for an explanation in the LP manual 😅
What do you need explained? You can add buttons and sliders that send midi. This is in the manual. Take a look at the actions and widgets sections.
I just don't understand the practical difference between the instrument and the processor.
Which is used for what?
The project is attached to the original post. If you want to see it in action then all you need to do is load it up.
you can use loopy to just send and receive midi using buttons and sliders and do no audio. in the picture i posted in response to you loopy is being used to send cc's and notes from my phone to remote control an app on my ipad . If that doesn't make sense, it may simply be a use-case that isn't relevant to you.