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
@Hypervox thanks for the quick response, the video is extremely helpful.
However, to investigate further, I'd definitely need the project file too as the reason for the glitch is probably inside that particular project's data.
I'll PM you the details!
Version 2.2.12 is out:
NEW:
FIXES:
@White thanks for the mention.
Just a minor bugfix update -- I still hope to get the next major update (which is definitely in the works!) out before 2025! 😉
Thanks for adding the Drum Map for Ampify Groovebox 👍
Think I will be adding this now as a pianoroll. Playing synths freely to record. How is version 2.3 progressing with mpe record?
Beta testa?
Use KB-1 not a hardware controller.
Can you midi map record to a controller or does audiobus midi map record in sidebar thing, to a controller?
Thanks.
Dont worry. Should be ok just recording from audiobus bar.
Is it possible to configure the keyboard to automatically display two octaves when making a new instrument? Now the default seems to be one octave.
Not exactly, but if you duplicate an existing instrument (by using the little + button in its box instead of the big +), the new instrument will have the same keyboard setup too.
Maybe this helps?
NS2 is pretty smooth and sweet, but no midi time stretching in NS2 which is pretty much why I use Xequence2 over it now.
yep!
Great tip, thanks
I just understood why midi timestreching is essential last night... And it's absolutely great...
Why is it essential? I'm using NS2 to send MIDI into AUM, but I always wonder if there's something I'm missing by not using Xequence 2.
I've been using Nanostudio 2 because
-No blinking light while adding notes to the piano roll
-Vector-based automation entry
-Note velocities are easier to see
-Color scheme is more mild and neutral
So in addition to wanting to know about MIDI time stretching and what causes you to need it often,
I'd be curious to know if Xequence 2 has a similar list of advantages. Maybe it's lighter on resources? I do own it, and I have used it, and I'd be open to switching. I use Xequence Pads AU often.
I tend to use Xequence when I want to use IAA synths or Korg Gadget. Whilst you could use NS2 to do the same, Xequence & AUM together are lighter so I have more processing power for the synths I want. To be fair, I find the two sequencers almost interchangable, and often create a piece in NS2, only to export the MIDi into Xequence if I want different sounds.
For me if NS2 had time-stretching it would be all I use for sequencing as I do love it. So that being said, I now (as of last night
) start sketching in NS2, get a fair bit down, export the midi to Xequence 2, do a half time and double time version and export it back to NS2 for continued midi-ing.
@Skyblazer said:
You know I think that's a big part of the reason why I don't use Xequence more. Something about the color scheme feels oppressive (to me), and so I just feel less creative.
I'm curious, is it a general contrast and brightness issue, or don't you like the individual instrument colors (too saturated?)
Always open for fine-tuning...
Actually having just reopened it to check I have to confess I'd forgotten that it had a light palette, which helps a lot. I still prefer Nanostudio color wise, but it may not be the stumbling block I thought it was.
I think I need to dive back into this sequencer this weekend - feel like I may not have been giving it a fair shake TBH.
@SevenSystems I would prefer the track lanes to not have a gradient. I would say the background colors for the cells in the piano roll are a bit too dark, too similar to each other, and too close in shade to the black horizontal lines separating them.
Maybe it would be best to offer multiple color schemes, but I do like NS2's color scheme the best of any DAW. I could see X2's dark color scheme appealing to somebody with a specific kind of taste. Like, an electronic music producer who uses a table full of hardware with LEDs in the dark. The individual instrument colors do have a certain "dance music" vibe to them. Edit: I just tried the light color scheme. Yeah, it's very light. Something in between the two would be better.
But again, the blinking light for the "Draw" button was the main thing I didn't like. If that button didn't blink, then I wouldn't mind using X2 to enter notes. I do prefer the automation timeline to be vector-based to allow for smoothness and precision, but that might be a larger undertaking, and I could come up with workarounds for that if I needed to. Plus, there is some appeal to the more organic and imprecise current method. But the blinking "Draw" button seems like it would only be useful for someone who is learning the app for the first time. It's the only thing that I would dread having to deal with if NS2 stopped being updated.
@Skyblazer thanks for the detailed feedback. I'll take it into consideration for the upcoming 2.3 update (it is scheduled for September or October at the latest).
Can you post a screenshot and encircle the gradient you've mentioned (I'm not sure which one you mean)?
It's funny you mention the dance producer sitting in a dark room with blinking LEDs. That's how I actually grew up making music, so it might not be a coincidence!
Offering more themes / skins for Xequence down the line would certainly be something that I'd consider too.
The blinking "Draw" button will be gone in 2.3 -- good news! (it's a frequent complaint and I can see why)
Regarding the automation: Yeah, Xequence tries to stay "true to MIDI" as far as possible, that's why its editing is based on the actual individual data points. However, a "hybrid" concept between the raw editing and vectors is already on the roadmap. (which is huge and I wish I had 3 parallel lives to implement it all!)
Thanks again for your constructive criticism, it's much appreciated.
Sunvox reads from a XML file if i'm not wrong. I did a solarized theme for it such a long time ago, I don't recall the format. But it's an interesting way to easily share themes
Yeah I've seen themes done using JSON, YAML and the like as well.
I would like a Solarized theme
@SevenSystems said:
This is very interesting. I can definitely see your argument. The reason I like vectors is that it makes it super quick to get an automation that I like, and super quick to modify it. So maybe a hybrid approach could work here.
I just spent 30 minutes playing around with Xequence and I agree with @Skyblazer about the color scheme. Color schemes are hard, particularly if you're designing something that doesn't fit your personal tastes.
@cian maybe we should do a Xequence Theme Contest after 2.3, where people submit mockups and the 3 most voted ones will be implemented!
But for now, you'll just have to crank up the brightness!
(I know... not funny!)
@SevenSystems
Awesome idea. I just couldn't participate... For me it works well - the dark theme. Light never clicked with me, but i'm giving it a try now
@SevenSystems Thank you for being so responsive! It sounds like there's a very good chance I'll be making the switch in the near future.
I held my finger down on the screen, above the top of the gradient, where it is closest to transparent. I suppose that could be useful for when sections are overlapping, but I also do like NS2 for the way it stacks the first four overlapping tracks.
Maybe I'll try producing in pitch darkness tonight, so I can give the current UI a fairer evaluation. It's definitely not a vibe I'm avoiding for my music. I kind of do like the uplighting gradient, on the "Interface" button for example, in the picture below. But I'd probably use a 100% flat version of the UI if I could. (Actually, even on NS2, there is a subtle shadow falling from the outer edges of the UI onto the piano roll, but I barely notice it.) If you hold a mockup contest, I may submit a design or two.
Another feature I like from NS2: The scroll bars in the piano roll.
I also would like to have a "Max Vertical Zoom" and "Max Horizontal Zoom" setting if possible, but with a closer zoom than NS2. NS2 only zooms in to show a full octave, which is good for a Pro, which is my main device. But I've thought about using my Mini to control AUM on my 10.5 inch device. And NS2's max horizontal zoom could be much finer, for any device.
If you need to check your tracks at different tempos, it's just perfect...Like a sample timestretched...But in midi.
I really had hard times to get it, but last night was just perfect for me...
X2 editing is just a breeze...
Now I sync it with Ableton Live as there's no audio tracks, my premix synths/drums is done into AUM, and I record voices with Ableton Live, perfectly in sync using Link.
So cool, thanks so much @SevenSystems
@AudioGus and @crony Thank you for answering my question. I guess I had never considered trying that before, as a compositional technique. But now I must try it.
Yes that's clear, thanks... I wonder though, is this actually desirable? Right now, when you change root note or scale, Xequence will try to keep the same pitch in roughly the same position on the screen. Is having the root note always at the very left "musically advantegeous"? From my limited musical experience, I'm usually all over the place with the notes I play and don't scroll the root note to a particular position... but maybe I'm strange?