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.

[ Meow | Audio Editor ] Public Beta

13567…17

Comments

  • jebnijebni
    edited February 6

    @wim said:
    Here's something for the brainstorming list. I think it would be a nice distinguishing feature that I don't think other editors have.

    I'd love to see a "wrap edit". By that I mean a way to move the audio within a selection but have it wrap around, preserving the length of the audio but wrapping the end to the beginning as you move it right and the beginning to the end as you move it left.

    Think of a loop where your timing was early starting it, so that the initial transient is at the end and the start is late. Move the audio to the right until the starting transient wraps around to the beginning and is in the correct position. That kind of thing.

    +1.

    @SevenSystems I haven’t actually tested this, but I’m thinking for the live loopers out there who don’t start with a click, the tempo might indeed be 110.76 bpm, and that two digits of accuracy, or at the very least increments of 0.1 bpm, might be important to them.

  • jebnijebni

    Of course, you could make the argument that their projects should simply be timestretched to the nearest 0.5 bpm without anybody noticing, but I could imagine cases where that might be off the table.

  • wimwim

    @jebni said:
    @SevenSystems I haven’t actually tested this, but I’m thinking for the live loopers out there who don’t start with a click, the tempo might indeed be 110.76 bpm, and that two digits of accuracy, or at the very least increments of 0.1 bpm, might be important to them.

    I did find that when setting the tempo a 0.1 jump was a little too much to hit the end of the sample perfectly. But at the same time I told myself I was being a bit ridiculous. 😉

    Nonetheless, I think I agree.

    I'll also say that setting tempo is a breeze and works great. So much so that to my surprise I didn't feel the need for setting the BPM by inputting the number of beats. (It would still be a good feature though.)

  • SevenSystemsSevenSystems

    @wim said:
    I've done a fair run-through on the iPad. I'm super impressed so far! It's amazingly responsive and fluid. A real pleasure to use. Enough so that I can pretty much forgive the "no plugin" ethos. 😎

    Next up - testing with keyboard, then on my current iPhone and my retired iPhone 7. I'll fire up the older iPad too.

    Sounds great, thanks for all the detailed feedback. Curious to hear about the phone and keyboard experience.

    And glad to know you're happy with the waveform display -- I spend quite some time on optimizing it so I guess it paid off. I mean one of the upsides of having no money is that my newest iPad is from 2017 and I really turn every bit and byte to make stuff fluid on it 😂

  • wimwim
    edited February 6

    @SevenSystems said:

    @wim said:
    I've done a fair run-through on the iPad. I'm super impressed so far! It's amazingly responsive and fluid. A real pleasure to use. Enough so that I can pretty much forgive the "no plugin" ethos. 😎

    Next up - testing with keyboard, then on my current iPhone and my retired iPhone 7. I'll fire up the older iPad too.

    Sounds great, thanks for all the detailed feedback. Curious to hear about the phone and keyboard experience.

    And glad to know you're happy with the waveform display -- I spend quite some time on optimizing it so I guess it paid off. I mean one of the upsides of having no money is that my newest iPad is from 2017 and I really turn every bit and byte to make stuff fluid on it 😂

    I've always felt that developers should have outdated equipment. In the companies I worked for we always gave them the hottest new stuff and the software they wrote just got slower and slower.

    Needless to say I was never a popular IT director with any software engineering departments where I worked.

  • SevenSystemsSevenSystems
    edited February 6

    @wim @jebni OK. Currently, the situation is as follows:

    • the 'Tempo' slider always moves in whole BPM increments
    • the +/- buttons next to it change the BPM in 0.1 increments
    • you can tap the slider to enter a value directly with any precision. I thought this will be rounded to 0.1 increments by the slider widget, but it doesn't. So currently, arguably due to a bug, it is possible to enter a BPM value with any precision.

    Given these options (moving the slider, entering a value by tapping, and the +/- buttons), what do y'all think would be the best way forward, without any additional buttons / UI elements? 😁 opinions?

  • SevenSystemsSevenSystems
    edited February 6

    @wim said:

    @SevenSystems said:

    @wim said:
    I've done a fair run-through on the iPad. I'm super impressed so far! It's amazingly responsive and fluid. A real pleasure to use. Enough so that I can pretty much forgive the "no plugin" ethos. 😎

    Next up - testing with keyboard, then on my current iPhone and my retired iPhone 7. I'll fire up the older iPad too.

    Sounds great, thanks for all the detailed feedback. Curious to hear about the phone and keyboard experience.

    And glad to know you're happy with the waveform display -- I spend quite some time on optimizing it so I guess it paid off. I mean one of the upsides of having no money is that my newest iPad is from 2017 and I really turn every bit and byte to make stuff fluid on it 😂

    I've always felt that developers should have outdated equipment. In the companies I worked for we always gave them the hottest new stuff and the software they wrote just got slower and slower.

    Agree!

    Needless to say I was never a popular IT director with any software engineering departments where I worked.

    I was never a director (at least not with command over others) nor an employee, but I probably wouldn't be popular as either 😄

  • SevenSystemsSevenSystems
    edited February 6

    Oh and btw @jebni, while I don't know if timestretching will ever arrive, I do plan to add VariSpeed (i.e. simply "resample" the selection in-place) so that minor corrections to timing can be done. This would probably work the same UI-wise as in Xequence when you activate the Timestretch toggle in the horizontal handles.

  • wimwim

    @SevenSystems said:
    @wim @jebni OK. Currently, the situation is as follows:

    • the 'Tempo' slider always moves in whole BPM increments
    • the +/- buttons next to it change the BPM in 0.1 increments
    • you can tap the slider to enter a value directly with any precision. I thought this will be rounded to 0.1 increments by the slider widget, but it doesn't. So currently, arguably due to a bug, it is possible to enter a BPM value with any precision.

    Given these options (moving the slider, entering a value by tapping, and the +/- buttons), what do y'all think would be the best way forward, without any additional buttons / UI elements? 😁 opinions?

    I think it'd be enough if you could just enter the tempo with that precision and not have it rounded off. Another thought is to change the +/- button precision according to zoom level.

  • mikejohnmikejohn

    @wim said:
    Here's something for the brainstorming list. I think it would be a nice distinguishing feature that I don't think other editors have.

    I'd love to see a "wrap edit". By that I mean a way to move the audio within a selection but have it wrap around, preserving the length of the audio but wrapping the end to the beginning as you move it right and the beginning to the end as you move it left.

    Think of a loop where your timing was early starting it, so that the initial transient is at the end and the start is late. Move the audio to the right until the starting transient wraps around to the beginning and is in the correct position. That kind of thing.

    A big ol’ +1 for this .

  • espiegel123espiegel123

    @wim said:
    I'm gonna go on record as saying I prefer the tap on the bracket thing for moving the selection over tapping directly on the waveform. I think you'll get lots of requests for tapping on the waveform directly, but IMO that method sucks compared to your method.

    So ... just confirming ... you can't please everyone.

    Just to be clear, I like the brackets for refining the selection.. I want to be able to tap to set the initial position.

  • SevenSystemsSevenSystems

    @wim said:

    @SevenSystems said:
    @wim @jebni OK. Currently, the situation is as follows:

    • the 'Tempo' slider always moves in whole BPM increments
    • the +/- buttons next to it change the BPM in 0.1 increments
    • you can tap the slider to enter a value directly with any precision. I thought this will be rounded to 0.1 increments by the slider widget, but it doesn't. So currently, arguably due to a bug, it is possible to enter a BPM value with any precision.

    Given these options (moving the slider, entering a value by tapping, and the +/- buttons), what do y'all think would be the best way forward, without any additional buttons / UI elements? 😁 opinions?

    I think it'd be enough if you could just enter the tempo with that precision and not have it rounded off.

    OK, but then I'd like to configure the slider to display two decimal digits anyway (i.e. 130.00) so that people "know" that more than .1 digit precision is possible. Moving it will still round to whole BPM, because that's probably the most common situation and moving it will be the most common way for people to interact with the tempo, so I think that makes the most sense as the default behaviour.

    Another thought is to change the +/- button precision according to zoom level.

    A good idea, but probably a bit too indirect and unexpected?

    So bottom line is, the only change compared to the current situation would be to have the slider display 2 decimal places instead of one.

  • jebnijebni
    edited February 6

    @SevenSystems said:
    @wim @jebni OK. Currently, the situation is as follows:

    • the 'Tempo' slider always moves in whole BPM increments
    • the +/- buttons next to it change the BPM in 0.1 increments
    • you can tap the slider to enter a value directly with any precision. I thought this will be rounded to 0.1 increments by the slider widget, but it doesn't. So currently, arguably due to a bug, it is possible to enter a BPM value with any precision.

    Given these options (moving the slider, entering a value by tapping, and the +/- buttons), what do y'all think would be the best way forward, without any additional buttons / UI elements? 😁 opinions?

    Excellent bug 😂. I’ll join the TestFlight to see. I like that Neon reveals the affordance for finer grained BPM by displaying “120.0” and supplying separate +/- buttons for the smaller increments, but whatever you do, it should make the possibilities obvious. Even if it means displaying “120.00” by default to make it absolutely clear that the slider is rounding and that there’s another level of pedantry just waiting to be enjoyed, haha.

    Edit: beat me to it. Nice.

  • SevenSystemsSevenSystems

    @espiegel123 said:

    @wim said:
    I'm gonna go on record as saying I prefer the tap on the bracket thing for moving the selection over tapping directly on the waveform. I think you'll get lots of requests for tapping on the waveform directly, but IMO that method sucks compared to your method.

    So ... just confirming ... you can't please everyone.

    Just to be clear, I like the brackets for refining the selection.. I want to be able to tap to set the initial position.

    I totally get it, that's why I made the "Select Played" function, which will let you set the selection start by tapping, and the selection end 'by ear'. But I have your way of working on the roadmap! :)

  • SevenSystemsSevenSystems

    @jebni said:

    @SevenSystems said:
    @wim @jebni OK. Currently, the situation is as follows:

    • the 'Tempo' slider always moves in whole BPM increments
    • the +/- buttons next to it change the BPM in 0.1 increments
    • you can tap the slider to enter a value directly with any precision. I thought this will be rounded to 0.1 increments by the slider widget, but it doesn't. So currently, arguably due to a bug, it is possible to enter a BPM value with any precision.

    Given these options (moving the slider, entering a value by tapping, and the +/- buttons), what do y'all think would be the best way forward, without any additional buttons / UI elements? 😁 opinions?

    Excellent bug 😂. I’ll join the TestFlight to see. I like that Neon reveals the affordance for finer grained BPM by displaying “120.0” and supplying separate +/- buttons for the smaller increments, but whatever you do, it should make the possibilities obvious. Even if it means displaying “120.00” by default to make it absolutely clear that the slider is rounding and that there’s another level of pedantry just waiting to be enjoyed, haha.

    Edit: beat me to it. Nice.

    Haha, yes. I'll check back after a break and then make a decision. Brain is a bit fried after 5 hours of sleep and essentially working non-stop for the past few days. And all that at the expected impressive hourly rate of roughly $0.50 😂 (sorry I know, I'm terrible)

  • wimwim

    Is BPM info saved in the wav file? If not, that would be desirable.

  • jebnijebni

    @SevenSystems said:
    Oh and btw @jebni, while I don't know if timestretching will ever arrive, I do plan to add VariSpeed (i.e. simply "resample" the selection in-place) so that minor corrections to timing can be done. This would probably work the same UI-wise as in Xequence when you activate the Timestretch toggle in the horizontal handles.

    Varispeed to fix timing sounds great. But by timestretching whole projects, I actually meant that the user would decide to do it in the app that the sample will finally live in, which is what I do with Loopy Pro.

  • jebnijebni

    @SevenSystems said:

    @jebni said:

    @SevenSystems said:
    @wim @jebni OK. Currently, the situation is as follows:

    • the 'Tempo' slider always moves in whole BPM increments
    • the +/- buttons next to it change the BPM in 0.1 increments
    • you can tap the slider to enter a value directly with any precision. I thought this will be rounded to 0.1 increments by the slider widget, but it doesn't. So currently, arguably due to a bug, it is possible to enter a BPM value with any precision.

    Given these options (moving the slider, entering a value by tapping, and the +/- buttons), what do y'all think would be the best way forward, without any additional buttons / UI elements? 😁 opinions?

    Excellent bug 😂. I’ll join the TestFlight to see. I like that Neon reveals the affordance for finer grained BPM by displaying “120.0” and supplying separate +/- buttons for the smaller increments, but whatever you do, it should make the possibilities obvious. Even if it means displaying “120.00” by default to make it absolutely clear that the slider is rounding and that there’s another level of pedantry just waiting to be enjoyed, haha.

    Edit: beat me to it. Nice.

    Haha, yes. I'll check back after a break and then make a decision. Brain is a bit fried after 5 hours of sleep and essentially working non-stop for the past few days. And all that at the expected impressive hourly rate of roughly $0.50 😂 (sorry I know, I'm terrible)

    OMG, you need a better boss. 🤦🏻

  • SevenSystemsSevenSystems

    @jebni said:

    @SevenSystems said:

    @jebni said:

    @SevenSystems said:
    @wim @jebni OK. Currently, the situation is as follows:

    • the 'Tempo' slider always moves in whole BPM increments
    • the +/- buttons next to it change the BPM in 0.1 increments
    • you can tap the slider to enter a value directly with any precision. I thought this will be rounded to 0.1 increments by the slider widget, but it doesn't. So currently, arguably due to a bug, it is possible to enter a BPM value with any precision.

    Given these options (moving the slider, entering a value by tapping, and the +/- buttons), what do y'all think would be the best way forward, without any additional buttons / UI elements? 😁 opinions?

    Excellent bug 😂. I’ll join the TestFlight to see. I like that Neon reveals the affordance for finer grained BPM by displaying “120.0” and supplying separate +/- buttons for the smaller increments, but whatever you do, it should make the possibilities obvious. Even if it means displaying “120.00” by default to make it absolutely clear that the slider is rounding and that there’s another level of pedantry just waiting to be enjoyed, haha.

    Edit: beat me to it. Nice.

    Haha, yes. I'll check back after a break and then make a decision. Brain is a bit fried after 5 hours of sleep and essentially working non-stop for the past few days. And all that at the expected impressive hourly rate of roughly $0.50 😂 (sorry I know, I'm terrible)

    OMG, you need a better boss. 🤦🏻

    This forum is my boss 😄

    @wim said:
    Is BPM info saved in the wav file? If not, that would be desirable.

    Some quick research seems to suggest that the WAV header doesn't have a field for tempo information...

  • wimwim
    edited February 6

    @SevenSystems said:

    @jebni said:

    @SevenSystems said:

    @jebni said:

    @SevenSystems said:
    @wim @jebni OK. Currently, the situation is as follows:

    • the 'Tempo' slider always moves in whole BPM increments
    • the +/- buttons next to it change the BPM in 0.1 increments
    • you can tap the slider to enter a value directly with any precision. I thought this will be rounded to 0.1 increments by the slider widget, but it doesn't. So currently, arguably due to a bug, it is possible to enter a BPM value with any precision.

    Given these options (moving the slider, entering a value by tapping, and the +/- buttons), what do y'all think would be the best way forward, without any additional buttons / UI elements? 😁 opinions?

    Excellent bug 😂. I’ll join the TestFlight to see. I like that Neon reveals the affordance for finer grained BPM by displaying “120.0” and supplying separate +/- buttons for the smaller increments, but whatever you do, it should make the possibilities obvious. Even if it means displaying “120.00” by default to make it absolutely clear that the slider is rounding and that there’s another level of pedantry just waiting to be enjoyed, haha.

    Edit: beat me to it. Nice.

    Haha, yes. I'll check back after a break and then make a decision. Brain is a bit fried after 5 hours of sleep and essentially working non-stop for the past few days. And all that at the expected impressive hourly rate of roughly $0.50 😂 (sorry I know, I'm terrible)

    OMG, you need a better boss. 🤦🏻

    This forum is my boss 😄

    @wim said:
    Is BPM info saved in the wav file? If not, that would be desirable.

    Some quick research seems to suggest that the WAV header doesn't have a field for tempo information...

    I don't know the details, but I know there is a way to do this. Many apps can read and use tempo and slice information. Loop points as well.

  • Mr_FoxMr_Fox

    @SevenSystems said:

    @jebni said:

    @SevenSystems said:

    @jebni said:

    @SevenSystems said:
    @wim @jebni OK. Currently, the situation is as follows:

    • the 'Tempo' slider always moves in whole BPM increments
    • the +/- buttons next to it change the BPM in 0.1 increments
    • you can tap the slider to enter a value directly with any precision. I thought this will be rounded to 0.1 increments by the slider widget, but it doesn't. So currently, arguably due to a bug, it is possible to enter a BPM value with any precision.

    Given these options (moving the slider, entering a value by tapping, and the +/- buttons), what do y'all think would be the best way forward, without any additional buttons / UI elements? 😁 opinions?

    Excellent bug 😂. I’ll join the TestFlight to see. I like that Neon reveals the affordance for finer grained BPM by displaying “120.0” and supplying separate +/- buttons for the smaller increments, but whatever you do, it should make the possibilities obvious. Even if it means displaying “120.00” by default to make it absolutely clear that the slider is rounding and that there’s another level of pedantry just waiting to be enjoyed, haha.

    Edit: beat me to it. Nice.

    Haha, yes. I'll check back after a break and then make a decision. Brain is a bit fried after 5 hours of sleep and essentially working non-stop for the past few days. And all that at the expected impressive hourly rate of roughly $0.50 😂 (sorry I know, I'm terrible)

    OMG, you need a better boss. 🤦🏻

    This forum is my boss 😄

    @wim said:
    Is BPM info saved in the wav file? If not, that would be desirable.

    Some quick research seems to suggest that the WAV header doesn't have a field for tempo information...

    Don't work yourself that hard for randos on the internet man.🤦🏻 You deserve better for your talent. ♥️

  • jebnijebni

    @wim @SevenSystems I think cue points are supported for slices, but for tempo, it seems people use proprietary ACID metadata, which includes a beat count. It’s been reverse engineered and documented somewhere.

  • SevenSystemsSevenSystems
    edited February 7

    @Mr_Fox said:

    @SevenSystems said:

    @jebni said:

    @SevenSystems said:

    @jebni said:

    @SevenSystems said:
    @wim @jebni OK. Currently, the situation is as follows:

    • the 'Tempo' slider always moves in whole BPM increments
    • the +/- buttons next to it change the BPM in 0.1 increments
    • you can tap the slider to enter a value directly with any precision. I thought this will be rounded to 0.1 increments by the slider widget, but it doesn't. So currently, arguably due to a bug, it is possible to enter a BPM value with any precision.

    Given these options (moving the slider, entering a value by tapping, and the +/- buttons), what do y'all think would be the best way forward, without any additional buttons / UI elements? 😁 opinions?

    Excellent bug 😂. I’ll join the TestFlight to see. I like that Neon reveals the affordance for finer grained BPM by displaying “120.0” and supplying separate +/- buttons for the smaller increments, but whatever you do, it should make the possibilities obvious. Even if it means displaying “120.00” by default to make it absolutely clear that the slider is rounding and that there’s another level of pedantry just waiting to be enjoyed, haha.

    Edit: beat me to it. Nice.

    Haha, yes. I'll check back after a break and then make a decision. Brain is a bit fried after 5 hours of sleep and essentially working non-stop for the past few days. And all that at the expected impressive hourly rate of roughly $0.50 😂 (sorry I know, I'm terrible)

    OMG, you need a better boss. 🤦🏻

    This forum is my boss 😄

    @wim said:
    Is BPM info saved in the wav file? If not, that would be desirable.

    Some quick research seems to suggest that the WAV header doesn't have a field for tempo information...

    Don't work yourself that hard for randos on the internet man.🤦🏻 You deserve better for your talent. ♥️

    Haha. They're mostly good randos though!

  • SevenSystemsSevenSystems

    @jebni said:
    @wim @SevenSystems I think cue points are supported for slices, but for tempo, it seems people use proprietary ACID metadata, which includes a beat count. It’s been reverse engineered and documented somewhere.

    OK, I might look into that!

  • wimwim

    @jebni said:
    @wim @SevenSystems I think cue points are supported for slices, but for tempo, it seems people use proprietary ACID metadata, which includes a beat count. It’s been reverse engineered and documented somewhere.

    I dunno. Whatever it is that Apple loops, BeatHawk, Auditor, Neon, etc recognize. 🤷🏼‍♂️

  • ShabuduaShabudua

    @espiegel123 said:

    @SevenSystems said:

    @espiegel123 said:
    Can one paste audio from the system clipboard to start a file?

    No, the clipboard is currently internal to the app, but I have using the system clipboard on my list! Currently, you can either drag & drop or use "Open".

    Being able to get data into and out of the app via the system clipboard would enormously increase the app’s utility for me…making it a convenient adjunct to Loopy Pro

    +1. For Meow to be really useful to me, I need to be able to get clips to/from other apps with maximum speed and minimum effort.

  • SamuSamu

    @SevenSystems At some point I’m going to be requesting sustain loop-editing for creating instrument samples, loop-metadata is usually stored in the ‘smpl’ chunk within a .wav file.

    This will likely happen when the app gets built-in recording capabilities, input-selection etc.

    When that time comes a ‘keyboard’ to audtion the sample at various pitches (or slices) might also come in handy.

    Later on today I’ll see how well Apple Pencil is handled as that is my go-to pointing device when I use my iPad and fingers get ‘too big’ for precision :sunglasses:

  • nuno_agogonuno_agogo

    no audio from meeow. loaded mp3 and wav file formats. the cursor ist moving but no sound.

    ipad 6th gen, ipadOS 16.7.2

  • KrupaKrupa

    I think on iPhone it won’t play sound when notification sounds are disabled, not sure if that’s deliberate or not, but I rarely have them enabled…

  • SamuSamu

    @SevenSystems I think I've bumped into a nasty one...

    After I've made a selection using the Apple Pencil and try to use my fingers to 'pinch zoom' the waveform the UI kinda gets 'locked up'. I can no longer move the start/end brackets and after a while trying to use the other icons to select all, or zoom selection etc. I get this freaky error message :sunglasses:

    Here's one of the crash-logs that follow after the 'lockup'.

    Cheers!

Sign In or Register to comment.

© Vanilla Keystone Theme 2024