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
Audio Evolution Mobile Studio 6.8.7 has been released:
This app just rocks. Such a good touch-based ui once you start to “get it”.
So I got all excited and bought Fabfilter Pro Q4 to go with all my other Fab apps. I loaded them into CB3, and then n-Track Pro with 100% Fabfilter apps on a Guitar, Vocal, Piano, Bass, and Drum track as well as the Master track of each DAW for my mastering efforts. I used 256bits and didn’t freeze any tracks on my humble Air4. I noticed playback stuttering and latency issues on both DAWs. However, I had ZERO issues on Audio Evolution. Smooth as silk. Has anyone else had a similar experience?
Hello @dwrae !
I checked PDC and it turned out to be broken. Firstly, the compensation does not work, and secondly, you may hear a strange sound that appears at the beginning when the application tries to compensate for the delay introduced by the plug-in (in this case, in linear phase mode):
Could you check it out, please?
I'll check it out, although I am pretty sure it has worked so it should be a specific case.
I cannot reproduce it, although I only have the Pro Q 2. Can you reproduce it with only the Pro Q 2 on the track and no effect muted? Can you try with our Default Sound Set instead if you are using an Audio Unit and see if that makes a difference?
Unbelievable
Audio Evolution Mobile Studio 6.9.2 for iOS has been released:
Thanks for the update, I would love to use AEM more but I always find myself hindered with some poor usability, I know you fixed the one for having to pause to use many parts of the UI.
I hope to find time to make some more concrete suggestions, I would really like to see AEM being updated for a more user friendly experience, it is a very complete DAW!
Hi @dwrae!
Thank you so much for updating this awesome DAW with exact features I wished to have
I found a couple of issues:
1. The app crashes if you add automation for an AUv3 parameter and tweak (even another) AUv3 parameter via MIDI CC. I tried with SWAM violin, added automation for "Expression" with AUv3, and tweaked vibrato by "modwheel" MIDI CC from the MIDI editor. And app freezes deadly every time when I start playing.
2. Is it possible to display MIDI CC on top if they store information as you did with the automation? My default case is playing SWAM instrument expressively live and then doing small corrections, but it is always a torture to find the exact MIDI channel in the list
I'll check it out,thanks!
Thank you so much for such fast replies!
If you to reproduce the bug or collect logs - I will be happy to help
I tried all sorts of things, but I cannot get it to crash. I don't have SWAM violin, so if you could check if it happens with another AUv3, I'd appreciate it.
What I tried:
No crash here
Audio Evolution Mobile Studio 6.9.4 for iOS released:
Note offs are now sent to an AU MIDI after stopping playback. Before, starting playback could still have a hanging note that was processed.
Added 'Render to a MIDI file' to the track pop-up of instrument and MIDI tracks so you can save individual tracks to a MIDI file.
Solved a possible crash that could occur when disconnecting or connecting a USB audio device.
Audio tracks are now unarmed when attaching/detaching an audio device.
Bravo! Thank you for making Audio Evolution so awesome!
Hi @dwrae! Thank you for the updates and taking a look at my bug.
I couldn’t reproduce this bug in another synth from end to end. But I have an idea why it may happen.
I will split the bug into two parts.
Part 1. Parameter fluttering
Video #1
This is reproducible on any synth so I used a free J6 for demo. As you can see I
I guess you override the automation line with new values only when the fader moves, without catching finger up / down events.
But movements of my finger don't have a constant speed and there are tiny "gaps" where AEMS uses the old values from the previous cycles. And these gaps are so small that the result curve becomes very fluttery. Of course I magnified the effect by using a short loop. But even in the regular production it makes this "Touch" function unusable when you want to override a part of your automation - the "overridden" part will always be that flattery. And that's may be the 1st piece of a puzzle
Part 2. SWAM MIDI + AU automation feedback
Video #2
This is SWAM specific.
I guess that's a SWAMs feature that it displays the AU parameter movement when this parameter is tweaked by MIDI. Very convenient during the live playing I must say. But when I enable the "Touch" function in AEMS it reads this movement as an AU automation. So we have two automation lines and they are not the same - it looks like the AU line is a bit smoother. And here I don't know:
God, that remind me the times when I worked as a manual QA
Thanks for the very detailed information. The automation is recorded based on events that the AU sends. So if it would have sent an event when starting to touch the slider, then I guess it would have been OK. Recording automation in a loop will cause undesired effects since the automation events will be put in a list and afterwards, those events are merged with the existing events. So the 'overwrite' part happens afterwards and I don't see this changing soon I'm afraid.
Regarding the CC's, I think you should use either MIDI CC's to control a parameter and not both MIDI and automation if they control the same thing. If SWAM will send parameter automation when a parameter is controlled by MIDI CC, then you will a double effect. Here, SWAM should have an option to send parameter change events to the host when MIDI CC is used since there is no way that the host knows it controls the same thing.
Audio Evolution Mobile Studio 6.9.6 for iOS has been released:
Hi @dwrae, thank you for the reply!
Understood your point about AU automation.
That would be totally enough for me in this case, but there are two things that are making this usecase not very usable for me as well.
1. It looks like MIDI CC values are also merged together when I want to re-input them for some part of the track. Is it possible to add an override mode or something like this for this case?
2. Only AU automation list shows an asterisk mark for edited parameters. MIDI CC list doesn't have this feature, and I have a pretty complex controller with the mapping I never remember. So I can't find the correct parameter without checking each one. Could you please add the asterisk mark for the MIDI CC list as well?
Audio Evolution Mobile Studio 6.9.8 for iOS has been released:
That bpm timestretch is well thought out, just when I thought AEM couldn’t get any better. Thank you as always!
I was fooling around with AEM for the last few hours and found a lot to like. I’ll take some time this weekend to further check it out but so far, so good. Anyone else have any input good or bad? 😎👍🏼
Only good. If I was going to regularly doing any DAW stuff on the iPad I think I'd work to overcome my little bit of disorientation over the interface and workflow and use it over other DAWs just because it has most of what's needed under one umbrella. I can't say anything bad about the UI and workflow. It's fine. It's just not natural to me right off the bat.
I find that by the time something I do is worthy of being fully DAW'ed (which is rare these days) I just don't feel like using the iPad for that. Everything else, but not that.
Thanks @wim
I do find the workflow fine in some aspects and puzzling in others. Familiarization will help I think.
I swear by Caustic, NS2 and FLSM but each has something missing. By the time my ideal app comes out I will be dust!
Couple of questions, if you please…
Is it still limited to a single midi fx per track?
Also, afaik, you can only view the mixer, arrangement, piano roll, and audio editing views individually and can’t for example see the piano roll together with the arrange window. How much of a hindrance is that when composing/arranging?
I don't recall it was ever. There are 3 AU MIDI slots per track.
It depends. There are many users with phones who handle this fine. Rest assured though this is going to be resolved in the next UI update for tablets.
@dwrae When is this new update expected? I spent a good amount of time with AEMS over the weekend and am quite pleased with it. I have some observations but will hold off until after next update if it’s soon.
@watari_banzai For me there is no hindrance in the current implementation.
I'm afraid I cannot give a time frame since it depends on a lot of factors.
@dwrae No problem. Thanks!
A really quick question ( well, actually three )
just trying out this beast. I deleted the audio on a track and when I try and drag another piece of audio onto this empty track it says I can’t because I have exceeded the number of tracks. But, I am still only working within the three tracks - not creating a new track.
Is it not possible to drag audio onto an already created track?
Secondly, how do I delete a channel entirely?
What are the meters calibrated too ( ie are they rms and peak or something else )?
Thanks in advance.