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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Audio Evolution Mobile DAW

1212224262748

Comments

  • @MusicMan4Christ said:
    Guys I loaded Ruismaker as an AU on a midi track but how do I launch the UI for Ruismaker. On iPhone SE latest OS.
    Thanks!

    Please open the virtual keyboard by pressing the little keyboard button in the mixer channel on the left. There should be a button named AU in the top bar.

  • @dwrae said:

    @gregsmith said:
    But freezing tracks would presumably make this never really a problem?

    It would kind of solve it, yes. Does the C indicator at the bottom right turn red when you playback?

    Yes. It was ok for a bit and I thought it was doing well but then things got too much :)

    @Matt_Fletcher_2000 said:

    @gregsmith said:

    @dwrae said:

    @gregsmith said:
    I’ve just been reading back through the thread and found the bit about freezing tracks. Is this likely to happen @dwrae ?
    I can’t work on my current song anymore as it’s going over cpu.

    It is likely to happen, but can you please tell me how many tracks you have and how many effects and virtual instruments and what type (AU, the app's own effects/instruments, IAA, etc.)? Is this something you would expect to run into in other DAWs at this point?

    I’ve got to be honest, I’ve not used Auria or Cubasis at all so this is my first time properly using AU, so I don’t know what kind of limits to expect. I’ve got 7 tracks, 5 of which are au, 1 of which had an au effect on it. Im using Zeeon on 2 tracks which I think is cpu heavy.

    So I’m not surprised at all that this overloads the cpu, especially as I’m on iPhone X and not my iPad :)

    But freezing tracks would presumably make this never really a problem?

    Yep, depending on your device, that’s gonna kill things.

    For now, why not just render the AU tracks to audio in new tracks. Then unload the AUs (making a note of their presets in case you need to go back and tweak them)?

    But yes, freezing would be very good. Much less hassle than the above.

    Yeah I was thinking this. Bit annoying in the composition stage though.

  • Audio Evolution Mobile Studio 2.0.4 for iOS released:

    • When pressing Auto, the automation lanes for busses are now displayed as well and can be edited
    • The automation lanes now show a horizontal dotted line for the default value of the selected parameter
    • Parameters for AUv3 instruments can now be recorded (touch automation)
    • Added ‘Paste’ to relevant pop-up menus in Scroll mode for faster pasting without having to go into Range mode
    • Control Change value lines are now drawn thicker
    • Added an option to the Settings to activate drum pad velocity where the vertical tap position in a drum pad determines the velocity/volume
    • Channel pressure and pitch bend events are now only added if there is no other such event around that time
    • The piano roll editor now draws a center line for pitch bend and pitch bend events are now snapped to the center
    • Channel pressure and pitch bend events can now be both created and edited in Draw mode
    • Added ‘Convert to instrument track’ option for MIDI tracks
    • When selecting Seaboard or Lightpad Block as MIDI input, ‘Keep channel information’ is turned on automatically
    • The AudioUnit interface entry was not displayed in the More menu of a drum pattern track for small phones. Solved.
    • The MIDI channel on output of instrument tracks was forced to one channel which would cause problems with MPE. Solved.
    • Fixed an issue with the virtual keyboard where a key release would stop other keys from moving
    • Solved an issue with range display on MIDI clips
    • Solved a problem with note off events not being sent on the correct channel after pressing stop, causing stuck notes.
    • Solved a problem with MIDI playback in loop mode
    • Solved an issue with importing files with UTF8 encoding
    • Solved a crash with AudioBus
  • Awesome! I broke my iPad so all I have is my iPhone SE now :(
    Thank goodness for this Awesome app!

  • So, on a MIDI instrument track what’s the difference between the automation I draw in the piano roll (as a series of vertical bars) and the automation I draw in the tracks view (after hitting Auto, as diagonal lines between buttons)? I’m messing around with varying the Release on a brass instrument soundfont across several bars of music. If I draw variations in the piano roll by changing ‘NOTE’ view to ‘CONTROL CHANGE’ view and choosing ‘CC 72’ and then I draw variations in the tracks view by highlighting the track, hitting ‘Auto’ and choosing ‘Instrument Release’, am I doing exactly the same thing? How does AEM reconcile those two inputs on the same cc? Or are these two ways of varying cc different?

  • Hey @Cib, have you heard the Toneboosters reverb in this DAW? It sounds pretty good to me. Capable of some subtle sounds.

  • @gusgranite said:
    Hey @Cib, have you heard the Toneboosters reverb in this DAW? It sounds pretty good to me. Capable of some subtle sounds.

    The EQ is first class too :smiley:

  • edited September 2018

    @dwrae can You create automation by manually manipulating the parameters in real time? E.g. bringing up a volume fader?

    [Edit: found it, the Touch button]

  • edited September 2018

    @JonLewis said:
    So, on a MIDI instrument track what’s the difference between the automation I draw in the piano roll (as a series of vertical bars) and the automation I draw in the tracks view (after hitting Auto, as diagonal lines between buttons)? I’m messing around with varying the Release on a brass instrument soundfont across several bars of music. If I draw variations in the piano roll by changing ‘NOTE’ view to ‘CONTROL CHANGE’ view and choosing ‘CC 72’ and then I draw variations in the tracks view by highlighting the track, hitting ‘Auto’ and choosing ‘Instrument Release’, am I doing exactly the same thing? How does AEM reconcile those two inputs on the same cc? Or are these two ways of varying cc different?

    It's basically just what you prefer to use. The background of this is that our latest Android release contains ADSR controls above the virtual keyboard when used with SoundFonts. The iOS version doesn't have these yet, but the parameters are available (since that part is shared code). The BASS midi library that is used to play virtual instruments has specific commands for these controls (besides the MIDI CC events) and those are the ones that the app uses and can be automated in the Auto section. They have overlap with CC's and control the same thing in the end. You can use either, but you shouldn't use both.

  • Thanks! I love having access to the ADSR for soundfonts for expression, and I think the tracks view ‘auto’ button is the more natural way for me.

    So... if I DID make the mistake of having data on the same cc in the piano roll automation view as well, how do I fully clear that again?

    One more question! Does AEM’s soundfont engine have the ability under the hood to put an SF2 instrument into mono mode or can they only operate in normal poly mode? If yes, can I currently toggle that in the CCs somewhere? Would love to make this brass line into a mono/lead.

  • @dwrae does having the same code base as Android result in loss in performance since you can not write optimized plattform specific code?

  • @JonLewis said:
    Thanks! I love having access to the ADSR for soundfonts for expression, and I think the tracks view ‘auto’ button is the more natural way for me.

    So... if I DID make the mistake of having data on the same cc in the piano roll automation view as well, how do I fully clear that again?

    Please go into the piano roll editor, select Control Change and the control change number it concerns. Then press Remove and swipe over the CC dots. This is CC-number dependent. You can also go into Edit mode, long-tap to trigger the blue selection rectangle, then 'grab' the CC dots and press Cut at the left panel. This is CC-number independent.

    One more question! Does AEM’s soundfont engine have the ability under the hood to put an SF2 instrument into mono mode or can they only operate in normal poly mode? If yes, can I currently toggle that in the CCs somewhere? Would love to make this brass line into a mono/lead.

    Yes, it's MIDI CC 126:

    http://www.un4seen.com/doc/#bassmidi/BASS_MIDI_StreamEvent.html

    Please go into the piano roll editor, select Control Change at the top left, then scroll all the way down/up to Control Change 126 (Mono Mode On), then (in Draw mode), tap-and-hold for half a second on the location where you want mono mode to start and make sure you do that in the upper half of the screen (just in case it triggers only on CC values larger than or equal to 64).

  • edited September 2018

    @fattigman said:
    @dwrae does having the same code base as Android result in loss in performance since you can not write optimized plattform specific code?

    No, the C++ code is platform-agnostic anyway (of course except for really platform-specific things like OpenSLES, AU, IAA). However, the Toneboosters effects are optimized for SIMD operations using specific Apple parallellization calls.

  • @dwrae ok thank you. I was just curious because I’m a developer myself.

  • That was an android specific post if I’m not mistaken

  • @dwrae am I right in thinking that only one fader can be moved at a time when recording automation? What if I hook up a midi controller, will that work?

  • edited September 2018

    @LibliengEsse said:
    When you're bored and you want to relax after a hard day's work.
    You need to call a beautiful girl and she will brighten up your evening.
    I usually order here [censored link].
    Everything is real and without deception

    1 hour of Candy versus 1 year of iPad 2018 with Audio Evolution Mobile?
    I guess I'll have a lot more fun with the latter plus the girl of my choice :smiley:

    @JonLewis said:
    That was an android specific post if I’m not mistaken

    You seem to know androids better than I do :D

  • @gusgranite said:
    @dwrae am I right in thinking that only one fader can be moved at a time when recording automation? What if I hook up a midi controller, will that work?

    No multi-touch for the mixer or MIDI control yet.

  • I’m really super grateful to have this app on my iPhone!
    I only wish it had Link but so far it’s pretty tight with Drum Session on iPhone. Haven’t tried with Lumbeats apps.

  • ++1000000 for Link. Please???

  • @dwrae said:

    @gusgranite said:
    @dwrae am I right in thinking that only one fader can be moved at a time when recording automation? What if I hook up a midi controller, will that work?

    No multi-touch for the mixer or MIDI control yet.

    OK, thx.

  • Just had a thought @dwrae ...

    Would it be easy to add a way of unloading an AU but storing the patch? This way we could bounce a track to audio and unload the AU, but easily bring it back again if changes were made? This seems easier than adding freeze track functionality.

  • @dwrae said:

    @gusgranite said:
    @dwrae am I right in thinking that only one fader can be moved at a time when recording automation? What if I hook up a midi controller, will that work?

    No multi-touch for the mixer or MIDI control yet.

    Well I still managed to mix this track live in AEMS. https://choon.co/tracks/0zxqa0gjw5u/downhill/

    Would LOVE multitouch though as there’s a couple of bumps bring one drum track up before being able to fade the other.

    Somehow this DAW inspired me to get a track finished though so THANK YOU @dwrae 👍

  • So @dwrae I checked what apps I had open and realised I had loads of synths and stuff running whilst trying to use AEM. I’ve closed them all and now my cpu is bobbing along just over 50%, with 1 x synth drum, 3 x zeeon (!!!), 1 x model d, and some au effects. Very happy! I’m on iPhone X.

  • @gregsmith said:
    So @dwrae I checked what apps I had open and realised I had loads of synths and stuff running whilst trying to use AEM. I’ve closed them all and now my cpu is bobbing along just over 50%, with 1 x synth drum, 3 x zeeon (!!!), 1 x model d, and some au effects. Very happy! I’m on iPhone X.

    Good to hear that. I'll still think about the freeze option though. Should be very useful in any case.

  • @dwrae said:

    @gregsmith said:
    So @dwrae I checked what apps I had open and realised I had loads of synths and stuff running whilst trying to use AEM. I’ve closed them all and now my cpu is bobbing along just over 50%, with 1 x synth drum, 3 x zeeon (!!!), 1 x model d, and some au effects. Very happy! I’m on iPhone X.

    Good to hear that. I'll still think about the freeze option though. Should be very useful in any case.

    Yep I’m likely to max it out again at soon :)

  • @dwrae said:

    @gregsmith said:
    So @dwrae I checked what apps I had open and realised I had loads of synths and stuff running whilst trying to use AEM. I’ve closed them all and now my cpu is bobbing along just over 50%, with 1 x synth drum, 3 x zeeon (!!!), 1 x model d, and some au effects. Very happy! I’m on iPhone X.

    Good to hear that. I'll still think about the freeze option though. Should be very useful in any case.

    Freeze is a must to be honest :)

  • edited September 2018

    @gregsmith said:
    Yep I’m likely to max it out again at soon :)

    Ok, do you guys have any preference on the way it should work? I see that in Cubasis, you get a new audio track with the rendered audio clip. In Auria Pro, you just see a frozen track that plays the rendered audio but you don't see the rendered audio clip. Can I have your votes please? :)

Sign In or Register to comment.