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.
Auria 2.0.5 is out!!!!
Okay, here's the changeling (http://auriaapp.com/forum/viewtopic.php?f=20&t=9458):
v2.05 (current version at the app store):
- Fixed issue with Lyra and background audio mode
- Fixed issue with keyboard entry when a bluetooth keyboard was attached
- Add “Export to Other App” to Share menu for audio and MIDI regions
- Fixed issue with Bounce In Place not unloading IAAs
- Fixed issue with MIDI not outputting when track 1 is record armed
- Added Bluetooth MIDI keyboard support
- Fixed crashing issue when enabling plugins that used a sidechain.
- Fixed issue with side chain and delay compensation
- Fixed issue with deleting tracks which could cause project corruption
- Fixed GUI issue with on iPad Pro in non-optimized mode when showing 5 - 8 tracks
- Fixed crash when adding, then deleting/undoing a track
- Added 5/8 time signature
- Made import tempo map off by default in the import dialog
- Fixed issue with piano roll selections
- Fixed Mackie MCU and HUI remote issues
Downloading now.
Comments
U mean i gotta find the detals elsewhere!?!?
Alrighty then, here I go
App Store says it's "various bug fixes."
I bought it and have hardly dipped in.
I still haven't figured out how to use a keyboard with an IAA.
Due to this difficulty I'm currently using modstep and cubasis as midi sequencers. Still using auria for some piano-roll intensive tasks.
I just assumed that I was too dumb to find it. That's really kind of goofy.
http://auriaapp.com/forum/viewtopic.php?f=20&t=9458 - info on whats on the 2.05 update
What difficulty are you experiencing exactly? Can you expand?
I wish I didn't have to bring Navichord or some other player into recording midi; I wish that Auria had a dedicated keyboard/drum pad.
Yes, but about the specific difficulty you have: what happens when you use a keyboard with an IAA?
I'm not using an external keyboard. My difficulty: There IS no keyboard built into Auria.
Oh, okay! I usually write my MIDI parts in Lyra, using Lyra's keyboard (Lyra has both velocity sensitive keyboard and pads), then I switch to the instrument of my preference. But yes, the lack of a built-in general purpose keyboard for controlling instruments other than Lyra is something I really hope @WaveMachineLabs change in Auria in the near future.
I think this setup favors the composer rather than the...let's call what I do "curating"? I generally write around the sound rather than compose a progression and find the sound that fits it. My confession for the day.
But I did briefly figure out how to use Navichord to write midi...but it was needlessly complicated and I didn't see the benefit compared to to using modstep or Cubasis.
Never tried Modstep, but it might as well be the solution for you... at least until Auria gets its own general purpose keyboard.
Ah - I see. @ExAsperis99 - I think
Normally I use whatever keyboard the app has. That's why I could not fathom the problem. So, if I'm using iSEM, then I'll use iSEM's keyboard, or if I'm using iVCS3 - likewise, or Addictive or Nave or Animoog, etc. etc. OR I'll use an external hardware keyboard (anything from an Xkey 25 to an 88-key weighted hammer action) OR I'll use Lyra's keyboard and lay down MIDI and play back to an IAA synth.
One of those options seems to work for me most of the time.
However, I agree that if your synth does not present a keyboard and you want to use it from within Auria then it could be useful to have that facility. However, it's not something I miss in a desktop DAW either like Pro Tools or Studio One. Not sure what the particular issue is with it not being there in Auria Pro is.
So when you use iSem, you're using the app's keyboard. But you're recording audio, not midi, correct? I'm wanting to write midi to Auria.
Auria does not implement MIDI. You need Auria Pro for that.
Unfair comparison, @MusicInclusive: most Desktop DAW users are used (no pun intended) to the necessity of having a MIDI controller keyboard as well.
One of the main selling points of Auria, or any iOS DAW for that matter, is mobility. Mobility is defeated when there is so much hassle to write MIDI on an iPad sequencer that you consider treating it like a Desktop DAW and resort to a hardware keyboard.
It's nice to have the ability to fully control Auria with hardware, but the necessity of doing so, specially considering the potential for expressiveness the iPad touch interface has and that is already well explored by other apps, is unaceptable.
I'm all for @WaveMachineLabs to squash all bugs before adding new features. But saying that an obviously desirable feature isn't really necessary reminds me of those old Arch Linux hardcore guys saying that GUIs were preposterous, and command line shells is all that's needed.
Hope Rim adds a keyboard as soon as his schedule for Auria allows it.
I think we're all talking about Auria Pro here.
We're talking about Auria Pro, no?
Incorrect.
@ExAsperis99, you can write MIDI to Auria with any app that can write MIDI. Just set the app as a MIDI input in the MIDI channel strip.
Try it. It's easy. Add a MIDI track, select Arturia iSEM (Instrument) as the instrument. Arm the track, switch over to iSEM, find the play button in the IAA toolbar, press play, and play some notes. Press stop and you'll see your MIDI in Auria Pro.
BTW, you could argue that some apps (Animoog, Model 15's Animoog keyboard, SynthQ ...) have a much more expressive keyboard than you're going to find in any sequencer that I know of.
But ... I'm just playing devil's advocate. I agree that lack of a built-in keyboard / drumpads in a sequencer is a big gap. It's also essential for AU Extensions, which have no internal keyboard.
Ah I see @ExAsperis99 . Well, if the app sends MIDI, then I'll use the app's keyboard and send MIDI to Auria Pro. I've done that with, e.g., Animoog very successfully. In fact, Auria Pro records Animoog's poly aftertouch very nicely and will play it back too. Which is cool. However... the number of apps that actually send MIDI is far fewer than the number of apps that receive it, so, if you wanted to start with the app, then, yes, that's often a non-starter.
Annnnd, in that case, then, yes, sending MIDI from Auria Pro to the app would be a useful thing. I see where you're coming from. However, yes, in most cases where that'd be an issue I'll use an external hardware keyboard, record the MIDI to Auria Pro and also send it to the app in question. Again, the Xkey 25 is very handy for that when one is thinking portability.
Here - just did that very thing. Addictive is loaded as IAA on track 1. Xkey set as input on track 2 (MIDI). Tracks armed. Recorded. Xkey played. Both MIDI and the audio from Addictive recorded at the same time.
And, here's a video I did some time back about recording MIDI and audio where an app supports sending the MIDI - in this case Animoog, which does.
Well, Mr. @MusicInclusive that video makes me very happy to learn this is possible and very grumpy to realize I have owned Auria Pro for many months and not had time to figure this out on my own
thanks for that
I'm not 100% on this, but you can select different sources for in/out in AP, so I would think you can use your fave keyboard as the in, driving what is selected as the IAA in Auria. Apologies if @MusicInclusive video shows that, as I didn't check that out before my post.
Mister Jones: I may have seen this before but if so I didn't appreciate it; I do now. Glad you linked it here.
Quick fool's question: Given the choice why would you bounce the track from to Midi to Audio having captured it in Midi? I'm sure there are many reasons/advantages, but I would appreciate your view.
What about setting Auria's cycling locators? The means for setting them is on the wrong page, imo. Unless I'm missing something?
I may want to capture the MIDI and use it more than once to drive two different synths. Maybe up it by a 3rd or 5th and record with a different voice on the same instrument or a different instrument entirely. I tend to think more in terms of audio than MIDI. I may well capture MIDI in order to adjust and tweak a live-played-in performance, but if I recorded the performance OK the 1st time then I have no need for the MIDI.
I tend to regard MIDI as a kind of "backup" to the auido
I rarely use repeated sequences. I rarely use loops. (Except for drum parts.) I do both sometimes but not as often as live playing. During the live playing I capture the MIDI if I can so that I can do two things. a.) tweak and adjust as I said to re-record a more "perfect" audio result b.) use it to score notation with so that it could potentially be published and played repeatedly. (That's if, of course, the piece lends itself to that and isn't a drone or ambient or other kind of experimental ad-hoc one-off kind of piece).
Make sense? Ish?
One thing I really wish I could do better is capture the MIDI of polyphonic guitar playing to score that.
You mean the |<- on the mixer screen that's no longer on the tracks screen? Yes. I made a case to Rim about restoring that when he first put Auria Pro out there. He was sympathetic when he understood why one would do it on the tracks screen (eventually) but had changed the way it was hooked in and needed the screen real-estate on the tracks screen. He said he'd consider maybe finding a way to put it back at some point.
It's interesting in that his workflow didn't require the use of it on the tracks screen. Mine - and several others who also commented on it - did
If that's not what you meant, I apologize