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.
Audioshare IAA trick with non-AB apps - not working anymore?
I was so happy to be able to select (among many others) iMPC Pro as IAA Recording Source on Audioshare, put Audioshare in the Input Slot and have fun with additional processing and recording through Audiobus but...
Why is it not working anymore?
iOS7.1.2
Comments
Having just played around with it, it seems like AudioShare is sending audio direct to the system out not the AB output port. Tried with a few apps, including iMPC Pro. You can open an app in the output slot that should block the audio and still hear the AudioShare output.
This only happens when using Audio Share as an IAA host. If you play back a file from your samples within AudioShare, it behaves as expected.
You can test this with Cubasis. Connect AudioShare to Cubasis and play a sample. You hear audio. Switch to Cubasis and turn monitoring off for your Audio Share track. No audio, no track activity on the channel strip.
Connect iMPC Pro via IAA in Audio Share. No channel activity, but you can here whatever you are playing in iMPC Pro. Logical deduction is that the Audio Share IAA output is bypassing the output slot in AB.
Adding an app to the fx slot makes no difference. I added Final Touch. Nothing in Final Touch, but the audio can still be heard.
Final test, play back a sample in Audio Share at the same time as the IAA app (still iMPC pro). Both sounds audible. Turn Final Touch output all the way down, sample behaves as expected and drops away, IAA audio still there.
All this done on iOS7.1.2. AudioShare 2.6.1, AudioBus 2.1.5 and Cubasis 1.8.2
I am an update behind on AudioBus so I don't know if the latest version would make any difference.
Anyone had similar problems on iOS8?
Thanks a lot, @xen ! Gonna try those tests.
I'm an uptade behind on Audiobus as well ( a bit afraid of updating apps on 7.1.2)
Strange is that it was working before...
No problem, there's nothing more frustrating than trying a set up that really should work, but for some reason doesn't.
I've been having one of those weekends. I'm going back to the hardware soon and just hook the ipad into that via MIDI and the system out and just use it as a synth alongside the rest of my set up. I'm spending all my time trying to get stuff working at the moment and that isn't what I bought this for.
@xen said:
I'm going back to the hardware soon and just hook the ipad into that via MIDI and the system out and just use it as a synth alongside the rest of my set up. I'm spending all my time trying to get stuff working at the moment and that isn't what I bought this for.
Yes ios recording can be a lot of fun or a real pain depending on way to many factors! I always seem to find myself going back to hardware because of this, but I do like p,aying around with it stil for fun.
I guess the issue in the end is that it's not one of the other. It's just us and our machines or tin whistles or whatever. Just the work. Or the play. Been sitting on hardware all morning and feeling good about it, but just wanted a certain sound that, bang, MUST BE EARHOOF, and that's great too. Having it to hand. The song doesn't care where the noise came from. Welcomes it in all the same...
Very true. That's why it's important to take a step back every now and then and look at what we are trying to acheive. Is it getting good tunes together or stretching some piece of kit as far we can, stubbornly muttering..."well it should damn well work, so I'm going to repeat the same steps for the twentieth time because this it must be right
Too much time this week on tech and not enough on tunes...
@xen said:
I'm getting to the same point -- rather than trying to use the iPad for everything, I'm intending to use it as a synth, sequencer, or as sample fodder for stuff on the laptop. And of course vice versa -- dumping stuff from the laptop into those delicious iPad samplers and processors.
I'm hoping that this approach will relieve the "stress" I've been feeling from things not working together. Boohoo. Lol.
Yeah, I'm definitely there...thing is, that was what I was expecting to do anyway, but you get exposed to so many innovations that are available as apps, you get seduced into thinking that it should all be available in any combination. Clearly some workflow ideas turn out and some don't.
But the ability to do so much away from the studio is major plus. I got stuck on a train for four hours the other morning and didn't even notice... Got lots of work done on a tune that wouldn't have been possible had I not got the pad.
The future is still bright, just a little less self contained.
I know this isn't helping directly but that Audioshare workaround was not really supposed to work in the first place. What you were using the whole time was an unintended loophole that was never really supported by Audiobus.
If an app is not listed as being compatible with Audiobus, it is not compatible with Audiobus. If you find a way to make it work with Audiobus anyway, all bets are off with regards to how long it will continue to work. Please keep that in mind while building your setups. I know how much it sucks to rely on something and then have it disappear but in this particular case you could have been warned in advance.
It's not a feature, it's a bug.... i thought it was the other way always
@Sebastian - that's a fair point and useful cautionary note regarding relying on a workflow that takes exploits a loop hole.
@Sebastian - it was a pretty damn good loophole. I would have classed it as a really good function rather than a bug! Any reason for that loophole being closed?
It was kind of a loophole, but an intended one. However, when switching to the new IAA based Audiobus SDK, I had to change it so that the output is only from the built in fileplayer. However, you can record the audiobus signal processed through IAA-only effects in AudioShare, but perhaps that's a more unusual setup.