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
I agree. I'm usually one of the iOS-update hand-wringers, and only because of warnings on this forum. But there was little of any downside discussions here re: 9.3.2 & I took an early plunge & haven't had any reason to call it out (unless it's what has caused some little hiccups in the way my iPhone works lately...).
Thanks for taking the time to help with this. I LOVE the sound of this.
This setup was loading DRC into an audio track into Cubasis.
When I loaded DRC into Cubasis using IAA on a MIDI track, I had no connection with DRC except by creating MIDI connections and the DRC IAA icon inside Cubasis did not open up DRC as it should have. When I bounced the audio from the MIDI track, there was no sound as DRC was never actually successfully hosted via IAA in Cubasis on a MIDI track.
I tried a similar approach in AUM where the only option to load DRC was as an instrument. Using the AUM keyboard routed to DRC IAA, the connection to DRC in AUM was lost. If the AUM keyboard was connected to DRC via virtual MIDI there were no problems.
My conclusion is that there is a problem with the way the DRC IAA instrument is implemented. The work around is to use DRC as a generator and send MIDI to its virtual port.
@InfoCheck
Now I see what you were talking about - the post as it originally appeared didn't mention you were using AUM at all.
Actually I only used Cubasis in the original post and only used DRC as an IAA generator. Later after reading @sinosoidal post, I decided to try DRC as an instrument in Cubasis and ran into significant problems where DRC didn't work as expected. Hopefully he reads the post and can use the info. to fix the IAA instrument implementation for DRC.
To see whether the DRC IAA instrument problem was due to Cubasis or to DRC, I did similar setups with DRC as a generator and an instrument in AUM. As soon as I hit a key on the built in keyboard of AUM with DRC acting as an instrument, the connection to DRC in AUM was lost. Setup as an IAA generator in AUM as in Cubasis, DRC worked as expected. The fact that AUM only came up with an instrument version of DRC as an option in AUM is another concern as IAA apps with working generator and instrument modes show up as such in AUM. Plus @j_liljedahl is really on top of doing a good IAA implementation when he does update his apps (hopefully he can find the time to do so for all of them).
Ok then
You were using DRC as a generator in Cubasis here, then tried it as an instrument and it didn't work.
On version 1.0.6 I will try to homogenise the behaviour of DRC across inter audio app hosts. I cannot buy every of them but I already own Cubasis, Modstep and AUM. The review cycle of App Store has decreased significantly from 7 days to 2 days and that helps a lot to fix problems. Your feedback as testers is crucial.
Exactly, I've gotten into the routine of creating a seperate non-IAA MIDI track with no instrument assigned to it so I can record the MIDI playing the audio for an IAA app in Cubasis. This way I can simultaneously record both MIDI and audio. Plus I can remove the IAA app so it can be used for another track in Cubasis. I don't worry about IAA apps I won't need opening up when I reopen a project to add other tracks using different synths since they're not needed unless I modify their tracks.
It wasn't until later that I tried DRC on a MIDI track and discovered problems in that configuration.
Thank you for your work on making DRC work for us. If you need beta testers so you can get feedback from people using various setups on various devices before releasing updates to the general public, the forum is a good place to ask.
Yes, I have done that a few times already.
Many of the users of this thread are already beta testers. Many of them were actually early testers. 
Everyone who wishes to join TestFlight just have to send me a private message with the email. Thx!
Considering that Cubasis 2.0 is around the cormer I'll be focusing mainly on DRC's finctionality with it.(Nope, Got no Cubasis beta, wish I had though).
I do have AUM and Modstep too but since I like to stay somewhat focused my main apps for creating noises are Cubasis and Gadget
DRC keeps on opening up the online manual when I try to adjust the keyboard size on my 6s. Anyone else having this issue?
That's a really weird issue. Anyone else having this?
Has anyone found a way to load DRC as an IAA in modstep yet?
Good news! I have found the problem today.
I will make a new beta available for you to test and provide me more feedback.
great news!
@sinosoidal ,
Wishlist:
Finger keying or typing for DRC tempo.
A new ramp down sawtooth waveform for LFO
Menu bar for selecting waveforms, or a knob method.
Nuno, Thank you.
What a lovely wish list!
That 'ramp/saw down' was one of my early wished during beta until I found out it's possible to 'reverse' the ramp by changing the modulation amount in either direction for at least amp and filter. Pitch remains 'ramp up' only.
I do wish to have an optional 'triangle' wave that only produces positive (0-10) values in addition to bi-polar values(-5 to +5) together with at 'start-phase'. Meaning start the 'modulation wave' at maximum modulation value or minimum modulation value value or in the middle.
The positive triangle wave would in practice be a 'ramp up' & 'ramp down' with option to set the 'start phase' (start at bottom of the ramp, top of the ramp or middle of the ramp when it's on it's way up or down).
The options for uni-polar and bi-polar modulation sources are quite rare...
Most cases I end up using a 'free envelope' to control Pulse-Width when they is available.
Hence loopable envelopes are quite handy modulation sources which are not yet present in DRC.
That's my short addition to the requests
Added to the list!
What I loved so much in @Kaikoo2 wish list was that it was short and easy to implement. Your request will be harder to implement. I'm avoiding changes to the audio engine during the next releases. I want to concentrate in UI/UX and interaction with other apps.
That is and should always be high priority because it makes implementing DRC into a work-flow a lot easier
just for curiosity, as I noticed midi learn is omnipresent today, but no entry of controllers
is it that much effort to implement ?
eg: on the midi asignment page tip a controller, popup box appears, type 2 numbers + optional range, bingo
could be activated by a 'manual assignment mode' on the settings page
no need to provide this, though
(I might cludge 2 dials together as a universal 'sender' in one of the midi construction kits)
cheers, Tom
So, you would like to have a manual way of entering the CC number, is that right?
DRC 1.0.6 beta version has just take off from TestFlight.
This is a really early test version but I want to have more feedback about this problem. It is already loading on Modstep and it should be loading on other hosts as well.
Basically the problem was: when a app is loaded by an inter app audio host, it starts from zero, it has to load a lot of stuff, however the host might be sending events to it already (eg: midi events). If the code is not yet completely initialised it must ignore this events otherwise the app crashes because it is trying to access invalid resources.
Looking forward to have your feedback regarding other uses cases and usage in other inter app audio hosts.
yes, much appreciated if it's available
controls are sent via software and 'teaching' that on a single device is tricky if possible at all
but it's just the CCs needed - the range can be set in the sending software (I messed that in my previous post)
as mentioned I like DRC's sound engine because it has character
and it would benefit tremendously from sequenced and realtime control
for sequences I use Oscilab, for manual TC-Data
you probably know the latter, but if not: it's a must have seen for any developer
(one can learn a lot from the design... no matter what the software is about)
cheers, Tom
I'm at work, so I can't really test everything, but I'm happy to report that DRC opens up in a modstep now, and the transport arrow icon appears in DRC. And it sounds so much better than the Mersenne patch I was making do with....
Thanks.
Awesome! Let me know if you find any other crash situation. Thx
did you change anything on the sound engine, too ?
it may be chance or personal condition, but it seemed different from earlier versions
I didn't use it extensively, but the mode of operation starts to become kind of familiar
(which I consider a good sign)
btw it's the first synth of which I appreciate the effects implementation, really good job
sound is VERY unique, comes up more 'analogish' than some real analog synths recently
cheers, Tom
IAA launching with Cubasis is working a lot better now too.
Sorry for lack of feedback, but when things work as expected I usually stay silent