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
I have been trying to record Digistix into NS2. I thought it would work the same way as in Cubasis (simply press record whilst host sync is on and it plays and records simultaneously) but this is not the case in NS2 and I can’t find anywhere in the manual which explains how to do this.
Can anyone help?
Agreed. With the right sounds u can be AUv3 Instrument-less and get a lot done.
Recording audio? What are you trying to record to? Slate or Obsidian? Or?
NS2 doesn't have audio tracks that you can record to like Cubasis does yet.
Or, are we talking about recording MIDI?
If so, then NS2 can't record the output of MIDI AU apps running inside it yet. But there are fairly easy workarounds for that. If you are trying to record MIDI then someone or I can describe them.
It was either you or @dendy who told me how to do this. If I a recalling it right, you can host Digistix as midi output in either AUM or AB, and then have that midi played into digistix in NS2. No? I think this is right. I've not used digistix for a little while, but I'll have a look when I get a moment, to see how to do it step-by-step.
That's one way. The other, if you host DigiStix in NS2 is to route the midi out of NS2 and back in on another track. There are a couple of ways to do that.
But I can't tell if @TimRussell is asking about recording audio or midi, and whether he's hosting DigiStix inside or outside NS2. So it's too soon to try to answer.
Ideally I’d like for Digistix to create a MIDI track which can be used to play Digistix within NS2.
I've been playing around with NS2 for about 3 weeks and now and loving it. Lack of audio tracks is obviously the major downside. For me it's like AUM with more features and a better interface. I have too many software synths that I have acquired over the years but the more I use NS2 the more I just rely on Obsidian for all of my instruments except drums (I did get all of the expansion packs on sale cyber monday). I am using Step Poly and Rozeta suite sequencers to drive Obsidian and Ruismaker/Ruis FM/Ruis Noir for drums, and Ruismaker/Audio Damage/ProQ/Korvpressor for effects. So basically I'm using NS2 for Obsidian, hosting AU and automation and mixing and loving it. Even though I'm not using it at it's fullest capabilities, I feel like Obisidian and Mixing/Automation are easily worth $20 I paid. Obisidian is a beast and better then some synths I paid $10-20 for and the mixing/automation is on another level compared to BM3 which I was previously using. AUM has it's strengths to with flexibility but I come from learning on Pro Tools and hardware mixers and NS2 mixer makes sense to me with the way it's laid out and having automation is a must for me. I hope I'll be able to automate AU parameters at some point but overall I'm very happy with NS2 and for $20 it comes close to rivaling FL Studio which I used for a couple of years on dekstop and costs much more then $20.
Solo the tracks you want to record, go to Project > Mixdown and choose type "soloed tracks".
You can then load your recordings (saved under the Mixdowns folder) to Slate pads or use them in the Obsidian sampler. If you record from an audio interface, you can record directly inside Slate or Obsidian.
@dendy knows more for sure but that's how I do it now.
I agree. I don’t use AUM anymore except maybe for recording IAAs.
Ahh, OK, now it's clear.
NS2 can't record midi from plugins when they're loaded inside it. But there are fairly easy workarounds.
There are a couple of ways to go about this. It's probably explained best here: https://www.blipinteractive.co.uk/community/index.php?p=/discussion/comment/8985/#Comment_8985. If you have questions after looking that over, don't hesitate to ask!
Hey @wim thanks for that. Unfortunately I can’t quite make out what do to from that post and video.
I’ve loaded MIDI Tools Route as MIDI fx in the DigiStix channel, then created another channel of DigiStix, but not sure what to do next. Am I right so far??
Yep, right so far. I'm not available for a couple of hours, but if you're still stumped by then and no one else has stepped in, I'll write up some step by step instructions.
@Dendy has probably done that a few times already, but I don't have time to trace it down right now.
Is there a way to apply swing/groove template to an individual channel in NS2 so that you can add swing to hi hats but not to kick drum for example? I have read through the manual and I assume it's just global swing but just thought I'd ask
You can apply swing to the grid in the part editor and quantize to it. If you want different grooves on different channels, you can quantize them to different swing amounts easily. Record quantize has a separate setting, which also has swing.
Eh...
I forgot DigiStix is an AU Instrument plugin, not a AU FX plugin. Those directions won’t work.
I think the only way to do this is to host DigiStix outside NS2, in Audiobus, then record the Audiobus midi output to a track in NS2.
If you’re not getting the MIDI in NS2, check the track input settings. The default settings are to receive midi from all sources, and to only receive midi when the track is selected. If you’re not getting the midi, try setting the track to Always Receive MIDI. If you’re still not, be sure that either All Sources or NanoStudio 2 is selected as the input, and that all channels, are enabled.
I hope it helps. If you need more help, or screenshots, let me know.
Thanks
If you don’t have the app and are just reading up, you may not realize that swing is destructive. You actually reposition the notes on the piano roll grid. It isn’t an adjustable setting that you can change on the file.
I really hope they change that some day.
The advantage of this mechanism is that you can "swing" a selected set of notes and re-quantize them as often as you like.
If you set swing to zero and quantize again, the notes will be back to the straight grid.
For finer manual note position adjustments I'd suggest to leave the grid enabled but disable grid snap.
The NS2 piano roll has a toggle mode that allows you to tap individual notes to add to the selection (e.g. every other 16th note in case of swing) so you could alternatively fine-adjust any group of notes and listen to the results while playing.
There are no real advantages to destructive parameters where no non-destructive method also exists. You should be able to make things permanent if you wish but non-destructive parameter controls such as transpose, velocity etc are incredibly useful.
When I first used Logic back in its MIdI only days, i was put off by the ugly interface but then won over by its object orientated design which allowed all parameters to be non-destructively set to regions right down to individual notes. I didn’t look back and switched to it permanently.
Being able to get back to original timing is something You get used to and it’s a bit frustrating when you use an app that doesn’t allow it.
Having to destructively set transpose, quantise, velocity etc settings feels like a backwards step.
GarageBand has non-destructive parameters. They’re hidden behind a settings menu which is a little bit inconvenient but it allows you to change velocity, transpose, reverse, loop, quantise etc all non-destructively. Which is nice. :-) unfortunately they don’t extend down to note level though unlike Logic.
TLDR
I wish NS2 would copy logics parameter controls.
Totaly disagree
For me current method is far away superior compared to so called "non destructive way" .. in most cases i apply it and then i manually edit some notes .. So i need to "see" how notes were shifted by applyied swing/quantisation, and i want to change this on particular note...
Often i also select just some notes and apply swingh to those notes where rest i want to leave untouched - which would be totally impossible if swing would be applied just "non descructive way" on whole clip (cannot imagine UI interface which would allow this in non-confusing way in case it would be non destructive)
I use this very often in drum clips, i apply it for example to closed hihat but not to snare/kick, and then i apply different swing to percussions...
What would be great - to hear actually sound during tweaking settings, before they are applied. That would be extremely handy (and it is on todolist)
Here it funny how many people wants non-descructive swing, but they want use MIDIFx "descructive way" (eg. record output of MIDIfx physically back into sequencer) two very similiar things, totally different aproaches. Interesting. Not saying i'm not same, just in inverse situation - i like "non descructive" using of MIDIfx but "destructive" using of swing / quantisation ...
What you just described is non-destructive swing!
Until you apply it, it is non-destructive.
Yeah i know. But it is different - here it serves just for preview. Audible preview would be great, no doubt.
Well, this makes me think you envision that when you leave the piano roll editor the swing setting disappears. I hope not, but either way, will be an improvement. I’m glad to hear it’s on the todo list.
@dendy I think you should be able to destructively quantise if you want but for 100% of my use cases, Logics non-destructive parameter control system is far, far superior.
You can do exactly what you describe above with Logic, only it always remembers the original timing so you can return to non-quantised whenever you want. This also means that when you quantise you can do it based on the original timing, so if you apply a swing you don't like, you can apply another one quickly. When you apply a different quantise parameter, this is based on the original timing, so you don't 'break' your original groove. You can obviously also apply parameters destructively if you want. If a note needs to be moved destructively this is really easy too. You can just quantise a single note or move it and snap it to the grid.
Also when you apply non-destructive quantise in Logic you can see where the note is. It has all the advantages of destructive quantising with none of the drawbacks. You can use it as if it were destructive in any case.
So for example, if you select a region and change the tuning to +1, the notes move in the piano roll to reflect this. But at any time you can set transpose to 0 to return to the original. It's so much quicker to be able to select a whole load of regions and set them all to the same groove quantise template. I do this regularly; I create a groove template based on, say, a drum loop and apply it to other regions and tune it with the various Q-Parameters (range, strength, etc.). You can also do things like transpose multiple region selections across any number of tracks up an octave. And if you mess it up it's a doddle to get back to where you started.
When you change a parameter it is applied relative to the existing one too (which you can override and make it absolute) so you transpose every region up by a semitone and the regions you've already transposed will just add a semitone to the existing setting. And again, getting back to zero is instant and very easy (select all, set parameter to absolute zero).
Once you are used to having full control over all those parameters non-destructively (and in Logics case really quickly and easily via the parameter inspector) anything else feels slow and backwards.
@dendy, @wim, @klownshed, @rms13
When I need the full power, I'm using Logic X myself. The list of superior features in the piano roll alone is hard to compare with any iOS app, and if you ask 100 users then you might get a wish list of 50 features people want added to their iOS app.
Many developers deliberately avoid this, for one, to keep it simpler than on desktop counterparts and not the least because developing a higher-specced app on iOS takes more time for development, maintenance and support.
It could be an option if one dev or a small group of people living in a country with low living expenses is dedicated to development as a full-time job but there are not too many of them.
I’m not expecting Ns2 to get non destructive features. Logic was built like that from the ground up. It was originally sold with as an ‘object orientated’ sequencer which was pretty new at the time.
One other game changing feature of Emagic Notator Logic v1 was that it had smooth playback that didn’t stop, pause or stutter when you edited things.
Thankfully this is one feature NS2 did implement and it makes it feel so slick and professional as a result.
But my main DAW is logic. It’s my only DAW really.
I’m more than happy with all the tools I have. iOS has rejuvenated my music making at a time in my life when I don’t have the space or time to be able to sit in a studio for hours and make music.
I’m happy for NS2 to play a big part in that process. If ain’t perfect by any means but as an iPhone app in particular it’s frankly stunning work.
I may change my opinions and working methods when I eventually put my old air 2 out to pasture and upgrade to a new iPad but for now I’m pretty happy overall. But I quite like discussing this stuff too; it’s fun watching iOS music production evolve.
@klownshed I'm falling in love with NS2 more and more too.
Yesterday I've started VirtualCZ on the desktp since a long time and started copying a few patches into Obsidian with its PD oscillators. It's not a 100% replacement (and the VirtualCZ really sounds fantastic!) but it's possible to get close.
Obsidian and the routing matrix are so deep, it's incredible, sometimes I find new ways to do what I thought was impossible but then it clicks and there's another weird but functional workaround.
The piano roll might not be perfect but I haven't seen any stumbling block so far, what helps me get over a few restrictions is to embrace them and try to use them as they are in the most effective way I can find.
I do 'non-desctructive' editing in NS the old fashioned way: copy the part, mute the original, do destructive editing on the copy. Messy but it works.
I would love to see non-destructive quantize on the track level and non-destructive transpose at the clip level some day.
@wim thanks for your help with this.
I’m going to be feeding NS2 into Cubasis anyway via AB3 so I might just stick with hosting DigiStix in Cubasis where I know it does what I want it to.