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

1111214161748

Comments

  • @Matt_Fletcher_2000 said:

    @dwrae said:

    @Matt_Fletcher_2000 said:
    I have a Korg NanoStudio Keys Bluetooth controller at work. I can try that when I get time.

    I ordered one, should be here tomorrow.

    Wow. Thanks!

    It’s a great piece of kit I think.

    Love it too!!

  • @gregsmith said:

    @dwrae said:

    @gregsmith said:
    Ah yes seems to work with au effects but not au instruments. That’s very cool though and is probably all I’ll ever need tbh.

    Next version will have parameter automation for au instruments as well

    Wow! You’re clearly working super hard on this. Thanks for being so responsive.

    Yes. Ditto.

  • The user and all related content has been deleted.
  • Can’t find info on tempo changes in a song?

  • edited September 2018

    @Multicellular said:
    Can’t find info on tempo changes in a song?

    With this developer, that’s a “yet”. Give him a couple days

  • edited September 2018

    Anyone else here that can’t make heads or tails of this thing? I dunno.. Perhaps it’s just me ...
    Auria Pro- No problem, same with Garageband or drum perfect Pro also, Drum Oerfect Pro...BM3.... But this thing.. I like it but I don’t really understand it. I can’t follow either the manual or the video on YouTube
    Ahhh , it’s just me

  • It was surprisingly difficult for me to figure out how to do things that normally I can pretty chuckle figure out how to do. It’s just different however. Once you find the unusually place bits, there’s not really all that much to it.

    I did drop it twice over that, but came back a couple times figuring it’s worth it since it’s universal. Now that I “get it” I’m fine with it.

    Didn’t help that the only way to discover some of this stuff is trudging through videos that may or may not have that one little bit you need, and are already out of date.

    Good app though. Just different enough to throw one off at first.

  • edited September 2018

    @wim: It needs a few good videos and a clearer manual I don’t have any hair left to pull out

  • wimwim
    edited September 2018

    Feel free to ask away here for any specific questions. Someone is bound to be able to point you in the right direction. Once you find stuff it’s just yer basic DAW.

  • @Littlewoodg said:

    @Multicellular said:
    Can’t find info on tempo changes in a song?

    With this developer, that’s a “yet”. Give him a couple days

    Unfortunately, no. Tempo change is extremely difficult. It will introduce many hazards and will not be implemented in the near future, sorry.

  • @tja said:
    Yes, very impressive.

    @dwrae Did you watch my video from https://forum.audiob.us/discussion/comment/538197/#Comment_538197 ?

    I did, but it's not super obvious to me. Either you play lots faster than me or have a specific iDevice that has the problem, but here I cannot notice any lag. Do you have the same with an external keyboard? Then at least I know if it's the MIDI handling or the UI handling.

  • edited September 2018

    @Matt_Fletcher_2000 said:
    It’s a great piece of kit I think.

    Received and fixed. Channel pressure is two bytes instead of 3, ugh! The note on after that wasn't detected anymore. Cubasis couldn't handle it either it seems.

  • @dwrae said:

    @Matt_Fletcher_2000 said:
    It’s a great piece of kit I think.

    Received and fixed. Channel pressure is two bytes instead of 3, ugh! The note on after that wasn't detected anymore. Cubasis couldn't handle it either it seems.

    Cool. Thanks very much!

    So can I confirm, are you capturing ‘channel pressure’ or ‘Poly Aftertouch aka Poly key pressure’ or both?

  • Also, do you have the midi-flow app? (It’s very useful and probably the leading iOS app for routing midi around.

    You’ll find that sending the lightblock through midi flow (rather than direct to AEM) basically works but this time instead of notes being filtered out, channel pressure gets filtered out in AEM. You might want to check that scenario is also fixed?

  • edited September 2018

    Pic below of Midiflow setup that results in no channel pressure being captured. In midiflow I created a ‘custom midi flow port’ called ‘virtual out 1’. Then in AEM I connect to ‘virtual out 1’. I’m sure you’ll find no pressure data makes it into AEM in this senario for some reason. Might be connected to the above fix.

  • @dwrae said:

    @Matt_Fletcher_2000 said:
    It’s a great piece of kit I think.

    Received and fixed. Channel pressure is two bytes instead of 3, ugh! The note on after that wasn't detected anymore. Cubasis couldn't handle it either it seems.

    Never assume MIDI messages to be of fixed length! I've seen that problem in many many iOS MIDI apps leading to hard to trace obscure bugs. You really have to implement full message parsing in your input / thru code for all possible message types. MIDI messages can be anywhere from 1 to infinity (SysEx) bytes, unfortunately ;)

  • @Matt_Fletcher_2000 said:
    So can I confirm, are you capturing ‘channel pressure’ or ‘Poly Aftertouch aka Poly key pressure’ or both?

    Both AFAICT

  • @Matt_Fletcher_2000 said:
    Also, do you have the midi-flow app? (It’s very useful and probably the leading iOS app for routing midi around.

    You’ll find that sending the lightblock through midi flow (rather than direct to AEM) basically works but this time instead of notes being filtered out, channel pressure gets filtered out in AEM. You might want to check that scenario is also fixed?

    I can only assume it's fixed because if that apps sends 2 bytes for channel pressure, then the event would have indeed disappeared in AEM

  • It is really interesting to eavesdrop on the conversation between a knowledgable sophisticated users (who have done a lot of development) and a developer eager to drive bugs and missing features from a mature (if new to IOS) App.

    I hope this continues and the community around the product grows to reward the commitment to excellence.

    Have I mentioned lately that the ToneBooster FX IAP's in this DAW are awesome and most sell for $2 each?

  • @McDtracy said:
    It is really interesting to eavesdrop on the conversation between a knowledgable sophisticated users (who have done a lot of development) and a developer eager to drive bugs and missing features from a mature (if new to IOS) App.

    I hope this continues and the community around the product grows to reward the commitment to excellence.

    Have I mentioned lately that the ToneBooster FX IAP's in this DAW are awesome and most sell for $2 each?

    Yes, thanks so much to @dwrae - the idea that a user has a problem with a particular bit of hardware (Roli Lightblock) and the developer buys it a few days later, tests on it, and fixes it is really quite incredible (particularly given the low price of the app)...

    Incredible stuff.

  • @Matt_Fletcher_2000 said:
    Incredible [developer support] stuff.

    It's worth noting for his small-staff competitors: AEMS has 100,000+ installations on Android with a $7 price tag. He also has USB Audio Record/Playback apps and dozens of IAP's in his product.

    For the big staff development shops the revenue issues are problematic. Does anyone wonder why Propellerheads would use Reason Compact and add a free copy of Reason Lite to the package to upsell to their Desktop products?

    So, Davy Wentzler has a revenue stream to keep him whole while he adds the required IOS details like: AUv3 support, IAA interoperation support, MPE (which arguably applies to Android as a reverse donation) and testing every hot IOS workflow bolt on like Midiflow, AB3, AUM, etc. Making a product stable on IOS is really hard and the requirements keep changing: AUv3 MIDI.

    Android has 8 times the installed base of IOS and less competition in this category. I'm sure Android development has it's own set of frustrations with all the hardware variants. Selling software is a tough business. It's like selling art.

  • Audio Evolution Mobile Studio 2.0.3 released for iOS:

    • AUv3 instrument parameters can now be automated
    • When stopping playback, audio is now faded out to prevent glitches.
    • Moving the time line is now also possible while zooming
    • Increased the contrast of the bar display when the grid is enabled
    • The time code area on top now shows tick marks for beats
    • The MIDI input dialog now has a new section ‘Channel information’ with an option to keep the MIDI channel information or not for MPE purposes
    • The AU user interface can now be displayed by pressing the AU button in the drum pattern editor and drum pad display
    • When a Seaboard or Lightpad Block is detected, channel pressure is always recorded, even with the channel pressure preference set to off
    • No note events were recorded from the Roli Lightblock. Solved.
    • Solved a crash after pressing Next on an effect while the virtual keyboard was displayed
    • Solved a problem with failed rendering of some AU’s that cannot handle changes in frame count
    • Pressing the little keyboard button in the mixer channel when the virtual keyboard is already displayed now closes it
    • Rendering stems or rendering a single track to an audio file used a 4096 frames buffer size instead of the selected one which could also cause problems with rendering AU’s like Zeeon. Solved.
    • The DYN note length in the piano roll was using the grid size setting instead of the dynamic grid size. Solved.
    • Solved a crash when an insert effect was added to a bus whose input was not connected to any track.
    • Very long tracks could be created after ‘Split MIDI channels’ if the track did not contain MIDI notes. Solved.
    • AU MIDI selection was not saved in the project. Solved.
    • The button in the virtual keyboard display on iPhones that opens the AU editor is now renamed to AU from Edit
  • @dwrae said:
    Audio Evolution Mobile Studio 2.0.3 released for iOS:

    • AUv3 instrument parameters can now be automated
    • When stopping playback, audio is now faded out to prevent glitches.
    • Moving the time line is now also possible while zooming
    • Increased the contrast of the bar display when the grid is enabled
    • The time code area on top now shows tick marks for beats
    • The MIDI input dialog now has a new section ‘Channel information’ with an option to keep the MIDI channel information or not for MPE purposes
    • The AU user interface can now be displayed by pressing the AU button in the drum pattern editor and drum pad display
    • When a Seaboard or Lightpad Block is detected, channel pressure is always recorded, even with the channel pressure preference set to off
    • No note events were recorded from the Roli Lightblock. Solved.
    • Solved a crash after pressing Next on an effect while the virtual keyboard was displayed
    • Solved a problem with failed rendering of some AU’s that cannot handle changes in frame count
    • Pressing the little keyboard button in the mixer channel when the virtual keyboard is already displayed now closes it
    • Rendering stems or rendering a single track to an audio file used a 4096 frames buffer size instead of the selected one which could also cause problems with rendering AU’s like Zeeon. Solved.
    • The DYN note length in the piano roll was using the grid size setting instead of the dynamic grid size. Solved.
    • Solved a crash when an insert effect was added to a bus whose input was not connected to any track.
    • Very long tracks could be created after ‘Split MIDI channels’ if the track did not contain MIDI notes. Solved.
    • AU MIDI selection was not saved in the project. Solved.
    • The button in the virtual keyboard display on iPhones that opens the AU editor is now renamed to AU from Edit

    Wow. Thank you very much!

  • @McDtracy said:

    @Matt_Fletcher_2000 said:
    Incredible [developer support] stuff.

    It's worth noting for his small-staff competitors: AEMS has 100,000+ installations on Android with a $7 price tag. He also has USB Audio Record/Playback apps and dozens of IAP's in his product.

    For the big staff development shops the revenue issues are problematic. Does anyone wonder why Propellerheads would use Reason Compact and add a free copy of Reason Lite to the package to upsell to their Desktop products?

    So, Davy Wentzler has a revenue stream to keep him whole while he adds the required IOS details like: AUv3 support, IAA interoperation support, MPE (which arguably applies to Android as a reverse donation) and testing every hot IOS workflow bolt on like Midiflow, AB3, AUM, etc. Making a product stable on IOS is really hard and the requirements keep changing: AUv3 MIDI.

    Android has 8 times the installed base of IOS and less competition in this category. I'm sure Android development has it's own set of frustrations with all the hardware variants. Selling software is a tough business. It's like selling art.

    Anyone know how the audio lag problems are on Android. This was one of the reasons I went into iOS.

  • @greengrocer said:
    Anyone know how the audio lag problems are on Android. This was one of the reasons I went into iOS.

    There are a handful of Android devices which natively have low latency. They are mainly the Nexus and Pixel devices made/configured by Google. Then there are a lot of newer devices that have 'low enough' latency for most people, but not as low as you can go on iOS.

    For all Android devices with OTG suppor however, Audio Evolution Mobile for Android offers its own custom USB audio driver for use with class compliant USB audio interfaces. This driver provides low latency, even if your Android device itself doesn't have it.

  • @dwrae said:
    Audio Evolution Mobile Studio 2.0.3 released for iOS:

    You sir, are awesome.

    Thanks. AEMS has completely changed my "commute workflow" over the last weeks, and it's just getting better and better.

  • @dwrae said:

    @greengrocer said:
    Anyone know how the audio lag problems are on Android. This was one of the reasons I went into iOS.

    There are a handful of Android devices which natively have low latency. They are mainly the Nexus and Pixel devices made/configured by Google. Then there are a lot of newer devices that have 'low enough' latency for most people, but not as low as you can go on iOS.

    For all Android devices with OTG suppor however, Audio Evolution Mobile for Android offers its own custom USB audio driver for use with class compliant USB audio interfaces. This driver provides low latency, even if your Android device itself doesn't have it.

    Thanks

  • Thanks so much @dwrae

    Amazing stuff!

  • edited September 2018

    Thanks again for all of your work, Davey!

Sign In or Register to comment.