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
Thanks for reporting. If you use the "Voice Memos" app, does it also always use the iPad mic?
Thanks!
@Samu, did you also try with an audio interface? (you mentioned being able to choose the channel so it looked to me like you were using one...)
@mikejohn / @wim thanks for the 'Open In' report, yes I haven't gotten around to adding this yet (I always try to move the most frustrating and platform-specific stuff to the end), but it will be done
Just on it and so far it's been a success...
...I've tried with Steinberg UR-242, Audient ID4mk2 and EVO4, Audio Technical Turntable with built-in USB, iRig MicHD and USB-C->3.5mm dongle with Røde SmartLav+ all work as expected at various sample-rates.
I would love to see a 'input monitor' button which would be handy for input only source so the iPad speaker could be used to monitor since the record player doesn't have any speakers
For USB-Devices with more than two inputs (like the UR-242) it would be nice to be able to use the other ports as well.
It could be handy to set the auto-normalize level 'somewhere' since applying filters can sometimes make the audio distort (like applying high-pass filter to a normalized recording). The processed audio shows the 'clipping' which can then be normalized back since it's 32-bit floats which is really nice. (Either that or apply some 'limiting' during playback to avoid distortion).
Cheers!
Second or third time this has been mentioned, so I guess it's time to act!
How about a "combination": Center the view on the selection start/end, and zoom in ONLY if you aren't ALREADY zoomed in further manually. (hope this makes sense). That way, a certain minimum "sensible" zoom level is guaranteed, but if you're already "focused manually" on a very tiny area, you won't get "zoomed out" automatically.
Also @Samu
Yes I've imagined a "split view" like this as well and it has been mentioned by others and seems to be a thing with other editors. It's a good idea but for now it's outside the scope of the app! 😢
The only 'voice memo' recorders on my iPad are Voice Record and Dictafoon. They both use my iCA4+ (when connected) 'out of the box'.
Haha, thanks, will be fixed!
Timer was on my agenda, will do! (updating waveform is conceptually non-trivial, mostly because of the different modes (Insert/Mix/Replace) and "Normalize" (whose effect will not be known until after the recording).
OK, I will make it BIGGER!
Has also been mentioned by @espiegel123. I think I'll try to squeeze it in before v1.0.
Fine-tuning the toolbars and what/how much is visible depending on available space should definitely be looked at for v1.1, yes!
^^
For me that could work if the 'logic' works as you describe it
OT. when doing 'trim' keep the trimmed area as the selection, currently the wave is 'de-selected' when doing a trim.
Cheers!
That's neat, thanks a lot for testing! That leaves me to wonder what went wrong with @Harro's interface...
That would be quite trivial... will look into it.
Yes, I shall look into that for v1.1!
Yes the app never internally clips of course so you can always 'Normalize away'... I had originally envisioned an 'AutoNormalize' toggle (just like AutoZoom) that would just automatically Normalize after every edit operation... I think that would fix a lot of issues. Maybe worth it.
OK. I'm not sure why your interface behaves differently to others tested here... is there any configuration options or app for your interface where you can set its behaviour in regards to "Default interface", "Default Input" or something?
I guess in the long run, it will be best to add an explicit input selector to Meow.
Meow is SO smart that both are equivalent!
(if none is selected, it's the same as if all were selected, it's just drawn differently. I never understood why most audio editors allow "nothing" to be selected. It makes no sense at all.)
(eg. if it makes people "feel better" then I can also choose the other "mode" where it actually LOOKS like all is selected...)
@SevenSystems A few 'loud brain-farts' about the transport controls...
When editing 'one-shots' the play-button acts as a play/pause button making rapid re-triggering a bit tricky?
Preferably the play-button could have an option to always start from the start/left-bracket or a manually set playhead location?
The stop-button could turn into a 'pause' button during playback so the "[Played]" function can be used to select the portion that was just played back until pause was tapped, to continue tap the 'pause' button.
Also I've noticed that the UI can't handle two interactions at once?
(ie. latch one finger on the left bracket to move it and use another finger to tap play to audition the from the left bracket position forward, this would make auditioning the start-point a breeze).
Again, these are just ideas to speed up the work-flow
(I'm getting into 'picking hairs' mode since this is already by far one of the most fluid audio-editing experiences on iOS!).
Cheers!
Just following up -- when you say 'After deleting a recorded wave', do you mean 'Select All' and then 'Cut' or 'Delete'? Because in that case, the wave is not really "deleted", it's still there although zero-length, but to the app, there is still something "there" to be resampled...
It doesn't happen to me if I actually select 'New' from the top toolbar...
@SevenSystems The extra 'step' to pick the share format (Keep Settings or Normalized MP3) feels a bit redundant when I've already selected the format I wish to export in the previous step...
(everything to 'speed up the workflow').
To make export really bonkers 'drag'n'drop' functionality could be added to the share button (ie. long-tap on the 'share button' to 'lift it' and drag it to a destination that supports drag'n'drop.
I know this is 'feature creep' bur one can always dream, right?
Cheers!
I get ya, but I can't change the behaviour of the transport anymore for now, as it's very finely-tuned and "smart" (🥴) although it might not seem that way (and I'm sure it could be improved)
It all depends on where / how you last started playback, if 'Loop' is enabled or not, the current selection, etc... I understand rapid re-triggering is tricky because you might accidentally invoke 'pause' instead of 'play', but this would have to wait to be optimized for v1.1. I appreciate the feedback though!
Yes you're right, it's a limitation in XUI (Xequence UI toolkit) back from 2017 when touch screens were still new 😂😉, but it's certainly something to look into improving.
Thank you, that's motivating! (if there's no significant financial incentive, at least there's spiritual...)
I agree it can get annoying, and I could stop showing this dialog after the first time... the problem is, when to start showing it again? 🤔
That would be great yeah, I'll add it to the roadmap for v1.1!
Nah this is totally workflow-related optimizations and I'm all for this kind of feedback. Thanks!
"Open In" will be available in the next update!
BTW, here's the list of stuff that I want in v1.0 and that's still going to be in this beta at some point. As always, thanks to everyone for your support. It's been a pleasure (so far) 😃
@SevenSystems Regarding the fade in/out 'visuals'.
Instead of rendering translucent red 'bars' left and right what about rendering the actual 'curve' that is being used for fade in/out to visualize the fade? (the waveform is already adjusted so it would make perfect sense).
Because rendering the curve would take roughly 25 minutes more implementation time than the red bars 😁 but I agree it would be better. v1.1!
Oh, now for something completely different:
I've always wondered if 'Edit -> Copy' and 'Edit -> Cut' should take the fades into account. Currently, the 'original' audio data is copied into the clipboard even if fade handles are used.
I think it would make more sense and be more convenient because you'd probably want this in the majority of cases. Currently, you always first have to 'Apply Fades' if you want to do Cut/Copy/Paste stuff with a faded selection.
I think you're right. Having to apply a destructive fade in order to copy and paste what you currently "have" in the selection isn't ideal. Since undo is step by step there's no way of going back if you wanted to change the fade on the original portion.
Hmmm, 'thinking loudly', feel free to ignore...
My brain says, if the fade handles are used and a user does a copy then the fade in/out could be 'baked-in' into the copied content (ie. apply fades and copy selection). If the fade handles are not moved there's no need to apply fades and the audio stays intact in the copy buffer.
There might be a need to 'mix' the pasted content (ie. a crossfade between what's present and the clip-board, preferably with 'preview' so the result can be auditioned). Default could be 50/50 when using paste mix.
The mix-balance could come in handy when moving content between two open files when the tabs arrive
But to be honest I very seldom need to do cut, copy & paste within the same file but if I need to pick a portion of an existing file and create a new file I'd prefer a 'new tab/file with selection' and leave the original file in place.
Cheers!
You can 'Apply Fades' -> 'Copy' -> 'Undo' (Undo doesn't affect the clipboard), but yeah, I think even logically, it makes more sense to have the fades in the clipboard automatically.
Undo is very powerful in Meow in general because it also includes steps for selection operations and fade adjustments, not just edits to the audio buffer itself.
Yes, that's what I thought too.
Note that automatic crossfades can already be applied when using the 'Edit' operations, adjustable with the 'Crossfade' slider in the 'Edit' menu. If that's what you meant.
Not exactly, think ‘mix balance’ between source & destination, so more like a ‘blend’ between source a and destination b.
Oh OK right, now I get ya. Yeah, currently, the mix-paste balance is actually 100/100 (we don't really want to modifiy the original audio by default do we?).
In the future, when tabs are introduced (they will!), I actually want to have the clipboard contents as a tab too. Then, you could just go into the clipboard tab and use Process -> Gain +/- there before pasting it somewhere else. I think that would be a good compromise.
Yepp, that would definitely work
@Samu / @wim alright. I've decided to bake the fades into the clipboard.
Here's today's ChangeLog with a few more bits and pieces. I must admit that for the extreme-flu annoying-road-noise situation, I'm happy with it 😂
NEW:
IMPROVEMENTS:
FIXES:
.