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
Valid point, > @rickwaugh
... it also happens, that when you record in cubasis, and there's no signal coming in from the uca222, even after replugging, restarting, and you insert the headphones in the ipad's own jack, only then it reappears.
Factually the ios update is not related to the issue at hand (and can now be reflected in the thread's title)?
Surprised to learn by the way, that simultaneous monitoring when recording - i.e. internal headphones and the soundcard's is possible. Does this apply to all ios daws?
@crzycrs, I can't say, as I settled on Auria from the beginning. I do occasionally get some latency when simultaneously monitoring/recording, but a reset of the device fixes that. I usually try to shut everything else in the iPad down before starting to work, but it's as though there is a residual process hanging around causing problems. But so far, it works pretty well.
Exactly!
The sound comes back once I reconnect to the iPads headphone out. But if I use Audiobis, then I have no problem.
@crzycrs said:
it also happens, that when you record in cubasis, and there's no signal coming in from the uca222, even after replugging, restarting, and you insert the headphones in the ipad's own jack, only then it reappears.
Factually the ios update is not related to the issue at hand (and can now be reflected in the thread's title)?
@LFS I think it would be a good idea in the future version of Cubasis to have a more 'advanced' audio-preferences panel where the user could select both the input and output devices separately, CureAudio supports this...
I personally prefer to 'monitor' thru the iPad's HeadPhone output and record using the UCA-202 as my headphones only have ~1m/3' cable and the my UCA-202 is located away from my iPad (3meter/10' USB extension cable).
The 'advanced' audio-preferences panel could include preferences for:
Input Device (It's possible to attach ex. UCA-202 and iRig Mic HD at the same time using a USB-Hub).
Output Device (Options would be iPad Speaker/iPad HeadPhones or External USB-Device).
Monitoring Device (Same options as for Output Device).
I feel settings like these would be much appreciated by new and current users.
@samu not that an advanced preferences option in any app would be frowned on, it would be awesome. However, would a headphone extension cable be helpful to you? I don't know that behringer interface, so I don't know if the headphone out makes much difference ( it may, I just don't know personally), but an extension is handy for many reasons. I use one particularly with my in-ears so I don't accidentally pull them out if I move around.
I know that wasn't the point of your post, but just a thought.
I prefer short cables on headphones becase I'm usually very close to the iPad so tucking around a +10' cable makes no sense. My Sennheiser Momentum On-Ears have a 1.2m/~3' cable.
The Headphone-amp on the UCA-202 has more juice to drive the headphones.
Yes, I have a long cable to the UCA-202 that I attach to my IPad (When not using the iRig Mic HD) when sampling/recording and short cable for the headphones. So I only need to worry about one long cable attached to my iPad. I there were 2 long cables to worry about it would soon transform in to a trippable cable-spaghetti...
Hi all,
Please note that our engineers evaluated the issue with a Behringer UFO202 device (we've also exchanged with Audiobus) with the following outcome:
It’s not a Cubasis bug but an iOS or a hardware bug that only occurs when an app initializes an audio engine the way Cubasis does it. iOS returns an error code, instead of routing audio I/O to the Behringer UFO202. We cannot pin down which part of the Cubasis audio engine initialization would have to be changed in order to work around the iOS or hardware bug, so we must wait and hope that iOS or Behringer will fix the bug on their side.
Behringer has been informed about the testing results.
Best,
Lars
@LFS I hope you also informed Apple as it has been working just fine in previous versions of iOS. From what I've heard Cubasis doesn't even start on iOS9 (I dont't installe iOS betas so I can not confirm). I also do not have the slightest clue on what 'internal' changes have been made to Core Audio between iOS8.2, 8.3 and 8.4...
iOS8.4.1 beta has just been released, who knows, maybe this 'issue' is fixed in that build?!
Thanks for the help Lars!
I thought about reinstalling Cubasis previous version to test but I like the new version so much! The best ever!
Reg the UCA 202 I think it may have to be Apple to fix it cause it doesn't need any drivers to work with IOS. It just works. Weird thing is why does it only work as designed within Audiobus?
Is Audiobis converting from 64bit to 32bit?
Hi Samu,
We're aware of the iOS 9 startup issue that seems to be related to Apple.
Evaluation has started and discussion with Apple will follow.
Regarding the Behringer device, we have informed Behringer about the issue.
Best,
Lars
@LFS I just can't help to think of what kind of 'special way' Cubasis uses to intitalises audio and 'fails' with the Behringer UCA-202 when the device works falwlessly with just about every other app?!? (The device is a class compliant usb-audio device and no drivers exists for it nor are they needed).
That is why I wondered what good is it for beringher to know if they already made it class compliant.
I hope Apple fixes it cause if I forget to laugh Audiobus first and then launch Cubasis from within, then I get the error message and I have to do a reboot of mu iPad. So for now if I'm going to use my UCA, I make sure to load Cubasis in Audiobus first.
Just to clarify, I don't get any error messages with my UCA-202.
The only 'issue' that sometimes happen (not allways) is that I need to connect headphones to the iPad to be able to record the UCA-Input input in Cubasis but for me it's fine as I prefer to monitor thru the iPad headphone jack.
Using Audioshare the output is by default routed to the UCA but can be over-ridden by connecting the headphones directly to the iPad and when removing the headphones from the iPad the output is re-routed to the UCA.
I'm lookng forward to iOS8.4.1 as it according to a 'whistler' at Apple has some CoreAudio fixes...
Thanks Samu.
I get the audio engine error message from Audiobus. It seems like an initialization error type of message.
It only happens when I have my UCA connected and I lauch Cubasis outside of Audiobus. Now, once I close Cubasis and then try to launch Audiobus, this is exactly the point where I get the error message from audio is and it asks me to reboot.