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
Cool! Thank you!
Yea! I love this app... The beat grid snapping, etc makes editing sooo much easier than other tools. I really need to use it more for other stuff...
Just started using this app and my first impression is that it’s very solid and well laid out for a traditional linear DAW and it seems to check all of the boxes in this regard. Really like how clean the GUI is and the ability to use the buttons to quickly switch around to the different control views is great.
When you click on an track to do automation, it lists all of the AUv3 parameters in the chain which is very useful. Look forward to incorporating this more into my projects. At it’s current price, I think it’s one of the best values for this type of DAW. If you don’t need a bunch of samples, suites of effects, or built-in instruments this DAW is definitely worth looking into . It does support SF2 Files which you can load into its SoundFonts folder via the Files app.
Deleted.
Audio Evolution Mobile Studio 2.0.9 for iOS released:
Very nice! 👍🏼
I appreciate the controls being implemented as relative knobs starting at the center.
One question: How can the range be extended?
In an example patch, I wasn't able to close the filter completely etc.
Also, a sustain control would help (Decay won't have any effect if Sustain is at 100%)
As far as I know, the range of the parameters is the full range that the BASS library supports unless there is a bug somewhere. Anything specific you want me to look at (soundfont/preset/parameter/how do you know the range is not right)?
Try loading the Electric Grand and close the filter cutoff completely.
It's far from zero (unless there's either an issue with BASS or the instrument has additional static filter cutoff modulated by an envelope generator or whatever... Closing cutoff completely should eliminate the audible frequencies completely because the user doesn't always have access to the instrument's internals.
This is great thank you. Can I ask about the filter knobs - I tried with a few patches in the IAP banks and the cutoff and resonance knobs didn’t seem to do anything. Is it specific to certain patches?
Probably, yes. The knobs control the BASS library values, so if it's not doing anything, then the soundfont/preset probably has no range defined. Some only work up to halfway etc. I think that also answers rs2000's question, but I'll check it out anyway.
OK thank you.
Yay!!! Awesome!!!!
Question on this app. Using inserts on a track I.e Bias fx. Will audio evolution record only dry signal or will it record output of insert?
It will always record the clean input. If you want the 'wet' signal, you can always render the track to a file.
@dwrae, is it true that one cannot monitor any audio input? I understand there needing to be protection against feedback when using the iPad mic and speakers. But I’ve got an iRig Pro, which cannot be a source of feedback. It brings audio in through the lightning port, and outputs to the headphone port (I never use the speakers). Can I not monitor the incoming signal? Turning software monitoring on doesn’t help.
I found a workaround by placing AEM in an output slot of Audiobus and the iRig in the audiobus input, with software monitoring. But this seems like an unnecessary workaround. Am I missing something?
Thanks
There might be situations where AEM decides to ignore software monitoring, but I think that's only the case when iOS did not detect any headset/headphones. Did you arm the track?
I’m not sure you understood what I am saying. I have an audio device that I can’t monitor. It’s not one that would cause feedback. It seems as if no audio input other than from apps can be monitored. Is this true?
Yes, the track is armed.
You have this one? https://www.ikmultimedia.com/products/irigproio/
If so, do you use the headphones output on the iRig?
AEM actually crashes when I playback a track and try to open Bias fx to edit the parameters while playing back audio in AEM
No, I have an older one that uses the iPad headphone output. Thanks for drilling into this.
Ok, is it the iRig Pre instead of Pro then? Could you please provide a link? I have several iRig devices here that I could try.
No, it’s an older model of the Pro that doesn’t have a headphone output. You can’t even buy them any more.
Picture: https://goo.gl/images/aVMQXC
However, one way to test in a similar manner with no device is to plug in some earbuds with an inline microphone. Little to no feedback would be expected with the sound outputting to earbuds. Yet you can’t monitor the mic input. Other DAWs allow monitoring, but warn about feedback first, or have some way of detecting feedback and disable monitoring in that case.
I think I have that one somewhere. I'll test it tomorrow, but it has always worked in the past at least.
@dwrae are you able to open up the IAA app that is on the insert slot on the track to adjust settings during track playback in AEM? I tried doing this and AEM craches
@dwrae so I did some more tests. If I have the di track loaded and Bias FX loaded on the insert I can open Bias fx before playback begins to adjust settings. Once playback begins I am able to double click home button to use multitasking to pull up Bias FX, playback continues. If I try to open up Bias FX via the inserts tab on AEM during or post playback the app crashes
Ok, I did some tests with the iRig PRO. Indeed, software monitoring does not work right away, because internally I see the message that no headphones were detected. If one would do software monitoring using the iPad's mic and speakers, then you would get feedback, so that's why the check is there.
When I connect a headset (mic+hp), then software monitoring and even playback does not work. I guess iOS gets confused in this case with two inputs. However, when I connect normal headphones with a 3-pole connector, then software monitoring does work.
@Briandandrig said:
I do that all the time. Yes tried with Bias Fx as well: import one mono audio track, add Bias Fx, come back to AEM, press play, press BIAS FX insert, it switches to the BIAS screen, back, stop playback, press BIAS FX again, no crash.
So, does this always happen and does the app ask to send a crash report on the next start?
Actually, it’s iOS that’s killing the iRig Pro when you plug in the headset. IOS only ever allows one audio source at a time, the last that you plug in. Whenever you attach a new audio source it kills the previous one. The key with any DAW is to always plug the external audio device last. In this case, if you unplug/rep lug the iRig, you should get audio input from it again - but still no monitoring.
Yes, this is a workaround I think I needed to use in one other audio application. The others however seem to be able to sort out when to kill monitoring even with the headset mic present.
It’s not a big thing since there is a workaround. But you may get the odd person asking about it once in awhile.
Yes it crashes every time and asks to send a report. I don’t have mail app so it doesn’t send
@dwrae
Please, i have one question - i wanted to try higher samplerate exports (for example 96 khz) from AEM, am i correct that it is not possible and both project realtime and export sample rate are same as default device sample rate (eg. 44 or 48 khz, based on device) ?
(that's not complain or request:)) - just question, i'm trying multiple DAWs for some tests related to some AU plugins sample rate handling issues, and wanted to include also AEM to my DAW tests set, so asking in case i just overlooked something somewhere
)